[walolla]

I know that it sounds like a chicken and egg problem, but in my personal opinion, the best showcase is an actual result of a solved problem, for example: "i proposed this approach to team and afterwards our development speed increased by 30%" or "i had a personal problem, so I made this solution and made it useful for other people". Please note that I'm talking mostly about hiring here, as it can be very useful to gracefully outline your prior experiences. But once you're in, it's just natural, you solve problems, you don't hide the results, you talk about it, people acknowledge our skills.

When we talk about literature, of course, it's very important, as it makes learning things faster than just imperial trial and error, but practice and theory should be side by side.

I'm frankly sure, that you've been doing some practical stuff and not just reading about someone's experiences. I mean, it's easy to study and understand how facebook became so successful, but repeating that success is nearly impossible.

Sorry if I misunderstood your point, please correct me, if I'm going in the wrong direction.

[findingMeaning]

That is a nice response! Somewhere along your answer, you wrote a line > "i had a personal problem, so I made this solution and made it useful for other people"

This was the original motive of my original question. How to validate if someone's personal problems are only their own or there are people who need share it?

> you've been doing some practical stuff

Yes, but these are toy problems that only work on small scale. Currently, anything requires designing a large systems, which is seemed rather difficult. Maybe it's just an excuse to be lazy. Weirdly the projects blow-up with their scope after one/two day and just doesn't give that satisfaction.

[walolla]

Great! I think I get your concerns now.

When we talk about problems for potential solving there are pretty much always a group of people, I'm yet to see a case where there is only one person, who uses something. Even if you publish your riced-up arch linux config on github, someone will clone it and it's a pretty niche area :). Of course, if we are talking about starting a business it's better to perform a market analysis, thankfully there're communities for everyone. Let's say you want to do some integration thingy for a cloud-based CRM, you can find a reddit page, telegram/whatsapp group, or something like that, where the most involved users are located and just ask them some questions. Of course, there is always a limit of how many potential customers you can attract, but if you're building something small and niche, you probably won't need to spend a whole lot on development. There are many examples on youtube of devlogs or reports from guys, who made some little thing, like a webtool, that automatically checks TLS certificates and notifies you (idk, just a random idea) and with the right outreach are getting some clients. To get more clients you can post on a themed subreddit, producthunt, HN, etc. It may be small, but it how cool if it works!

Okay, scale. Of course, no one expects you to build huge and complex projects on your own. The point is how you write your small ones, how flexible is it? what about performance, potential for scale, etc. Basically, it's a small example of how you personally think about technical problems and solve them. Sometimes companies give you a small test task, I personally once wrote a pdf invoice generator with an API, just a small thing, but it has shown the employer how I do things. Please keep in mind, that you are not supposed to know everything, "Never worked with some specific IAM system?", don't worry, if you are used to learning new things you will quickly pick up what you need.

Once again, it's not the absolute truth, it's just a part of my experience, I'm sure, that other people will have something else to add or disagree with.