What Problems to Solve (1966)

This echoes what I have thought about my career. What to work on.

I've been blessed to have a good paying career in software engineering, but I've never really felt passionate about the products I work on. At the end of the day, my job is a paycheck. I do feel joy solving problems for others, improve society, be able to answer colleagues questions when they "come to my office". My family is happy that I can provide and that I am a role model for them.

I sometimes think I should work on things that make me happier. Sometimes I think that my career path is a mistake, I should work on problems "closer to god", make more meaningful contributions, build the next Kubernetes/ChatGPT/Google/<insert revolutionary product>, advance AI, climate change. I end giving up, I'm not that ambitious or driven.

I'm important to my family and colleagues. That may be good enough.

It depends on what "working on those problems" means to you. If you want to work on those problems as a software engineer, that sounds like an achievable goal.

To me, the interesting, fulfilling bits of building the next Google/ChatGPT/AI/climate change lie in the theory. Arguably with the exception of Kubernetes, this theory does not come from software engineering. As much as I enjoy software engineering, it's a trade. It's a tool to get the job done. And recently, I realized I like building things just as much as I like "the theory".

To me, that was a bitter pill to swallow. I'm not an ML engineer, but I suspect this is also the reason why you can find so many posts about ML engineers trying to pivot to ML scientist roles.