> Software engineering just isn't that hard
1) I agree that this is often true! Code can be pretty boring. That doesn’t mean there are no interesting problems that you can tackle with programming. It just means most people work on incredibly boring stuff and think that’s all there is and totally fine. Find something that’s a better use of your time.
2) There is more and less difficult software engineering. If yours is really boring why wouldn’t you try something more challenging? It doesn’t always pay as well but it can be a lot less terrible to experience on a daily basis.
3) Most of the hardest problems in making interesting technology that touches the world isn’t in exactly how the code is written. Learning this is the first step towards starting to be equipped to tackle the actually hard problems in our field. Which you could work on directly, if you wanted.
None of this is to say that anyone has to do this. You don’t have to have fulfillment in your job. Though you and most others should frankly probably look around and make sure the code you’re writing is doing actually good things in the world rather than bad ones, that’s an ethical obligation but one that is pretty orthogonal whether or not you’re working on interesting problems. (If people optimize solely for money though, they bend towards writing code that makes that empowers companies over people and generally makes the world a worst place. People have a responsibility to evaluate this and try and avoid the ones that don’t.)
Mostly: it’s fine to make the choice to not work on something fulfilling. But stating that there’s nothing fulfilling to work on in this world is just nonsense, defeatist and mostly means you’ve resigned yourself and everyone who takes your advice to unfulfilling, boring and miserable work that doesn’t grow you worth a damn.
And that probably sucks. So why take that approach?