I think there's a good argument for Elixir and Phoenix. It's shocking how easy it is to do just about anything with it. An excellent database wrapper, incredible async story, beautiful at real time. You can substitute in a JS SPA framework if you need to, but I think you can go really far with LiveView before that's a requirement.
Are these hard to swallow? It feels like the author is pushing a particular tone when stating facts (with maybe a couple debatable points) that any software engineer would agree with.
I play flight sim games and GFS is a major factor in my hobbies now. I’m over a year into converting a real F-16 throttle grip into a video game controller, and there’s no end in sight. I’ve become immersed in 3d printing, CAD and PCB design.
I hear it’s also big in outdoor hobbies—backpackers often make their own tents and packs too.
I think you would be surprised. There are a lot of concepts that cross over—servant leadership, trusting subordinates with expertise, setting expectations of “what” or “why” and letting your subordinates figure out “how.”
Your point is valid that those in the military can’t just quit, but there is a world of difference between motivated and trusting subordinates and those just going through the motions because they have to. (Same story in software engineers!)
Now, to be clear, the military regularly and routinely fails at the leadership principles they proscribe, but the principles are still good.
Philosophy is not a bucket where "soft" or "unskilled" knowledge work goes either. The author is doing themselves a serious disservice in not really explaining what about prompt engineering makes it not "engineering" and what about philosophy matches it better-- and I say this as someone who is on the caboose of the AI hype train.
