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.

The vast majority of human existence from million years ago to now is toil. I don't spend anytime feeling bad about being well compensated at an air conditioned office working on CRUD.

Perhaps it’s not ambition or drive but just curiosity. „I wonder if we can …“ -type of thinking.

I’m in a similar career situation and I am trying to beat my ego into submission to adopt a similar mindset

In keeping with the list preceding "climate change", consider changing it to:

"...advance AI, change climate."

> That may be good enough.

I would argue it is.

I have had discussions with peers recently around doing the big flash-y <insert revolutionary product>. An interesting analogy surfaced. The nuts in the studs of the infrastructure of the many structurally sound homes in existence are just as important (meaningful) as the doors, windows, and more flash-y features. They may be _more_ important in some cases. They all make up the home.

It made me realize it might not be all about maximizing ambitious pursuits. Maybe it is more about experiencing the joy of solving the next problem and the fulfillment that comes from simply being needed pretty regularly.

I was surprised that after “closer to god” comes the “build the next kubernetes”. How do you connect these two things?

E.g. I’ve found the “closer to god” in my yoga practice. And how I now realize that through words I can’t connect that much as through practice (e.g. just eating my lunch being fully present). I still think I can help through my software product building skills, but also know that if I can help people find a more joyful life / build a less painful body is closer to my purpose than “only” building software.

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.

The most important jobs in the world - teaching, cleaning, caring - are extremely underrated. They are lowly paid, and people automatically assume that those doing these jobs are less than.

Sometimes the most important thing in the world is to be a good person to those around you. That can be in extremely short supply to some people.

I don't think so personally, because if its truly from a place of curiosity, then you're in the BEST of place. You're enamored with a specific problem, have some idea of doing it and will slowly explore nooks and crannies to manifest it into reality. The problem here (again, i think) lies in the fact that we don't often see the grander value of our everyday works and yearn to do SOMETHING grander, more impactful, but we don't know which, or how, and in time it will torment us each time we do our normal work. (sorry for the text wall)

> The problem here (again, i think) lies in the fact that we don't often see the grander value of our everyday works and yearn to do SOMETHING grander, more impactful, but we don't know which, or how, and in time it will torment us each time we do our normal work.

I think it's a kind of yearning that can't be satisfied in the outside world. It's an inside problem and can only be solved there.

Kubernetes - only god knows how it works. There :)