Let's play "devil's advocate" and ... advocate writing LESS "useless" software.
I'm not saying don't work on your own stuff, but if you're going to invest a significant amount of your life into something, ideally it should also have the potential to earn you some money. Unless you're already rich and your problem is boredom instead of money like for the 99.9% of us.
I'm doing just that. I have a long running project that I built for myself, which was tangentially useful in experimenting various software architecture designs but the key part in this project is that it's "business driven". So if I understood something it's the employer's focus on the business rather than the tendency of developers to get lost in the useless beauty of technicalities.
I seldom build a feature for the fun of it, mostly I just need the damn thing to work. And when I do build the feature, it's almost never the most bleeding-edge aggressive optimized version, it takes me weeks and months to think about an use-case so running getting results in 10 seconds versus 100 seconds is absolutely irrelevant, actually relevant if getting 10 seconds instead of 100 takes me another couple hours of thinking.
Recently I am dabbling with the idea of starting another personal side project and again, it's gonna be something of potential commercial value. No harm combining the pleasant with the useful, in fact being useful rather than useless is what keeps me going.
I dunno about the greater context of your snippet, but at face value it seems optimistic to me. It's a wonderful thing when many important axes of consideration are in alignment. Many people find happiness in feeling useful, and money is how a civilization abstracts usefulness into something fungible. It's certainly not a perfect abstraction, but it's not inherently good or bad either.
That’s just how living under capitalism is like for the people who aren’t the lucky few who have a great job doing something they like. If you want a world without the need to earn money, advocate for and implement UBI.
Until then, don’t disparage people trying to earn money.
Have fun and learn when you need it, and work to earn when you need it. I see no harm in both.
But it might be better to have some fun in a while (it does not have to be writing code), so you do not feel like you are trapped in an endless rat-race (99.9% are in the rat-race). Having fun would also reduce the probability of burning out / going deep into depression.
I'm not saying don't work on your own stuff, but if you're going to invest a significant amount of your life into something, ideally it should also have the potential to earn you some money. Unless you're already rich and your problem is boredom instead of money like for the 99.9% of us.
I'm doing just that. I have a long running project that I built for myself, which was tangentially useful in experimenting various software architecture designs but the key part in this project is that it's "business driven". So if I understood something it's the employer's focus on the business rather than the tendency of developers to get lost in the useless beauty of technicalities.
I seldom build a feature for the fun of it, mostly I just need the damn thing to work. And when I do build the feature, it's almost never the most bleeding-edge aggressive optimized version, it takes me weeks and months to think about an use-case so running getting results in 10 seconds versus 100 seconds is absolutely irrelevant, actually relevant if getting 10 seconds instead of 100 takes me another couple hours of thinking.
Recently I am dabbling with the idea of starting another personal side project and again, it's gonna be something of potential commercial value. No harm combining the pleasant with the useful, in fact being useful rather than useless is what keeps me going.