What grade sudents is this for? Do you intend for this to be a dedicated class/semester or just a single unit? How good are they at operating a computer? (Typing, clicking, etc)

Although novel, there are also existing deployments of: https://en.wikipedia.org/wiki/Flywheel_storage_power_system

deleted by creator

IMO in the same way everyone learns arithmetic but doesn’t necessarily go into mathematics or finance, I think everyone should learn basic logic and coding, enough to basically use spreadsheet formulas, which is a half step away functional programming. (I’m pretty sure Excel even supports named functions and lambdas)

I’d think autonomous killing machines wouldn’t have a humanoid shape, as it would be optimized for efficient lethality and not things like grasping external tools and all-terrain movement that is calorically efficient and biomechanically sustainable.

This concept short film came out in 2019: https://www.youtube.com/watch?v=O-2tpwW0kmU

What does it take to emigrate there?

Consider the shell itself to be “the IDE”

Everything is interoperable, extensible, scriptable, and more. CLI tools are designed to run fast/instant, have keyboard shortcuts for everything, and be deeply customizable. The openness and variety cannot be overstated, Google “CLI file explorer” and you’ll easily find at least 10. Nobody has the same exact setup because it gets molded to match how your brain works. Go for popular tools, niche setups, or both.

Graphical IDEs could also run fast/instant and have keyboard shortcuts for everything, but their users don’t demand it. If you wished the file explorer/git integration/debugger/etc worked a bit differently, there might be a plugin, if you’re lucky. Many operations can only be invoked manually via sequence of dialog boxes or mouse clicks or both.

Then you’ve used one without knowing, because somewhere between the ORM you used and the database was SQL, and that SQL was put together by the ORM’s query builder

If by “raw dog SQL” you mean dynamically concatenating strings (conditionally, interpolating runtime values), that’s literally a query builder, albeit a janky SQL-injectable one.

What do you mean? SQL query builders exist in pretty much every lang

when you can’t even tell if they just took the day off with pay or not

But if the output of technical work isn’t apparent in any way besides measuring indirect metrics like “hours of butt in seat”, don’t we have a much bigger problem?

I dunno, I remember it more like, “hey computer, make a LARP/natural wonder/cozy space/sing & dance number for my real humanoid (and android) friends and I to enjoy together”. When computer manifestations got regarded as worthy of personhood, it was either some exceptional case, or the story was about the character’s delusion.

Isn’t functional stuff closely related to type theory & type systems in all langs? In that sense, it’s prevented whole classes of bugs from ever getting to prod in the first place.

Responsible for 0% of code in production

Best code is no code at all

Every line of code by Claude Code, eh?

How old were they, when they had those experiences? I been think I need to have them spend and feel they’ve wasted “their own” money to develop a sense of regret, too.

What did you do?

Do you have a version with type annotations, perhaps in a gist?

IMO that is a legitimate practical transition barrier to really having UBI, though

It’s hard for me to imagine a transition to UBI that isn’t fairly tumultuous

Yeah, this should be common software engineering problem for a senior engineer

In the beginning, there is only one data model used both externally and internally, to keep things simple. Now that they’re diverging, it’s time to draw an abstraction boundary that translates between internal and external models.

I’m not super strong with Java, but subclassing to handle v1/v2/vX doesn’t sound like the right thing to do. I’d detach the old model from the API while otherwise keeping it unchanged, implement a new pathway to connect with the new API, then translate in/out of the old model before it passes into the existing system. This way, the surface area of change and of integration is isolated and decoupled from everything else.

Then seems like they may have chosen these platforms because they’re not accessible and thus not threatening, in a malicious compliance way

Although, giving them the benefit of doubt, perhaps they wanted a low blast radius for their first integration rollout, which is considered good engineering practice.

That’s not “a fix”, that’s called “a practical workaround” which is used in the real world all the time.