"remember that historically the most groundbreaking achievements in early computing have happened in the service of the greater good. This is what I really want to do: I want every how - from the programming language and paradigm, architecture, down to every line of code and piece of syntax - to be informed by the why of the system that is being built. And I want that why to be a reflection of a genuine existing need, not some bullshit business metric which pretty much exists for its own sake."
That's a pretty achievable goal, work in the defense industry and the public sector. Programmers are in high demand, the economic incentives align with building things correctly and don't consist of shipping AI powered coffee machines in the next four weeks and the technical work is usually complex and interesting.
That's a pretty achievable goal, work in the defense industry and the public sector. Programmers are in high demand, the economic incentives align with building things correctly and don't consist of shipping AI powered coffee machines in the next four weeks and the technical work is usually complex and interesting.