I personally believe that developers are basically people who resolve problems regardless of whether they're related to code or not. And I, as also a developer, try to find and resolve those kinds of problems lately.
When I first decided to find and resolve problems, I focused on 'certain' things. Too much, to be exact. I tried finding problems in my daily life first. But what I missed was that I am a developer, so the problems and solutions I found were deeply related to developement.
For exmaple, I found a problem throughout process of dealing with site issues. Most of the issues usually happen in private networks and I need to help people(they can be CS team, sales team, installation technicians) on phone call. So I made a very simple tool that automatically checks overall network settings(ip, subnet, dns, ping test, etc.)
I assume there are those who have the similar problems as I do and the tool that I made would help them. But you know what? The people would be probably developers, meaning they're good enough to make their own tools on their own demands(especially in this AI era). So they objectively have little reason to use simple tools like mine. They can just build their own tools, which allows them to customize everything based on their own needs. If I want my tool to be selected, I must add some valuable features.
So I needed to widen my sight. I tried very hard to find other problems in my daily life. But it ended up becoming related to 'development things'.
I am not saying the 'development things' are not problems. I also wrote down some tool ideas about it. What I'd like to say is that as long as development related problems are not big enough, there wouldn't be a point in making tools to resolve the problems since developers can do that on their own. (except for when yourself need the tool)
And one day, I realized something.
I've recently started taking to piano class. I am a complete beginner, so I've been learning from very basic things, including posture. Everytime I practice the piano, I struggle with a simple problem. My wrists keep going down while I'm playing. (Wrists shouldn't get lowered.) But for a beginner, it's really hard to notice, since I was focusing on touching keys and melody itself and I wished there was someone who always lets me know when my wrists got lowered.
And at that moment, I realized. 'Oh, it's a problem!'
Yes. It's also a problem. And it's not just my case. Other piano beginners would have the same problem, meaning I could help them too if I create a tool for this problem. This was the first realization that a very small thing can be a problem that I could resolve. (how I can resolve this? maybe I can make an app that watches my wrists(using camera) and play an alarm when it detects my wrists are lower than starting position.)
Once I realized this, I could make a habit that to see any inconveniences in my life as problems and think about solutions for them. It's really fascinating. I can now focus on 'inconveniences', not just 'problems'.
One more thing I also realized is that not every problem is about removing pain. Sometimes, creating joy is also solving a problem. That's why I see good games are also a solution for a problem. Good games make people happy and resolve 'boredom', and the boredom is also a problem for people. So in my opinion, game development is also 'problem solving', and that's why I started learning Unity engine(of course, as a hobby)
So ultimately, everything around us can be a problem and we can resolve it. And it might help other people as well, especially when they don't have any knowledge about code. At least, I believe the world is still full of problems to resolve. To put it simply, every inconvenience in our lives can be a problem worth solving, regardless of how small it seems. How exciting!