2,983 karma · joined October 4, 2013
https://www.linkedin.com/in/tristanhearn
Cool thing about them is that you can write in C-like AVR code (like Arduino), or micro versions of Lua, Python, and other choices.
Institutional memory is something of a weak point in the software industry compared with other fields.
For many of us that have dipped our toes in the ML tooling but don't have a great application for it in our work areas, this would is the kind of thing that we would like. A NN that predicts well, AND has a well understood methodology that gives us actual insight and not just a black box.
Maybe what I have in my head is a deterministic gradient-based analog of an evolutionary algorithm? I'm not sure.
Speaking from the part-time professors perspective: occurring in parallel to this is a steady growth in course section sizes. 30 students used to be the norm for some courses, but 80-90 is the new normal just a few years later. Some of these tools are designed to help manage this. But the actual process of planning and delivering a lecture, providing individual feedback on written assignments (like exams), etc. is suffering.
Teaching effectively to a large section is harder than you might think, especially when teaching is only a fraction of your job & you have no TAs. But half-assing it is actually not too hard I guess. And you are seldom rewarded for the former. Thankfully for me and for my students, it is mostly a side hobby for me and not a living.
But the execution is so half-assed that it not only turns off students from the platform, but it runs the risk of turning them off to the actual subject matter as well. The whole thing had the stench of static requirements doc to a sub-contractor to a sub-contractor development pipeline with little to no end-user (that is, students, not department administrators) feedback in the development cycle.
It's a bit like self-driving cars in a way. The execution is everything, and the half-way hybridized situation is the most dangerous for the end-user. And the missed execution to me smells a bit like an arms race between Pearson, Wiley, etc. to get their platforms out and entrenched with individual departments before each other.
Every single item that contributes to the learning objectives of this course is incredibly Google-able, but as new students to the field, they do need at least some curation and direction to keep from getting overwhelmed. They need a reference resource that they can trust which is academic enough to be true, yet reasonably conversational. Textbooks used to fill this role, but publishers priced and walled-gardened themselves out of relevance.
Side note: if you're an professor who has done something like this in the past, I'd love to compare notes with you.
2.1 Access to energy / energy density of fuels (batteries included). This is the case across a wide range of industries and problem areas of course, not just transportation. But incremental optimizations in efficiency have lead to squeezing more performance out of the margins, but no Moore's-law type growth will ever happen without some kind of energy breakthrough.
2.2 Going forward, tightly coupled systems will be the norm. The traditional tube-and-wing aircraft with bolted on nacelles is a bit of a dead end for civil aviation. Systems to enable a more complex design workflow (e.g. graph based dataflow with accurate gradients) will be more paramount.
3. Research into the next generation of energy storage materials, and improved large-scale gradient-based numerical optimization algorithms.
That's a good point that autonomy could be a big deal for some consumers, and I bet larger plot size is a factor in that.