It's so hard to find real problems if you spend 90% of your time finding problems.
Having a job is a great fix.
Building side projects with no purpose works too.
For instance, you can sell a boilerplate to make it faster, or get feedback from users and build for them.
Although it's much harder to start, and hard to navigate life without $ for months (years in my case)
Any ideas on how to capitalize on that?
Either I'll build an audience on YouTube
And/Or I'll build new startups
Also, my Twitter is really small so there's much more work to do there.
Any thoughts?
Note: I've been building an audience there for 2 years (the first 4 years was me building in the dark)
I do have a radical idea that I am keen to share with you in particular.
I am the Founder of RocketDevs.com. The 'amazing' thing about us is that we can ethically and reliably source GREAT developers and rent them out for $6/hr or $980/mo. This entry point is cheap for USD earners, but stil a fortune in some regions.
The market opportunity here is early startups. People have ideas, but they can't spend $7k/mo on Turing. Fivver is shit. Upwork is avg $28/hr for mid-devs. With no affordable help, non-technical founders will scramble to find a 'technical' founder. You taught yourself how to code but few are that committed. Technical founders will reliably start a project and burn out quickly due to 0 help.
Our audiences intersect strongly. My radical idea is that we work together. I use my deep technical experience to source great devs. You use your following so I can conveniently focus on the product and avoid the pain of 'building an audience' just to get the word out. Stable income for you and we're helping folks build their dreams.
Look me up at linkedin.com/in/thelastsultan if you're keen. I think im in your inbox already.
> Having a job is a great fix.
My experience differs: it is very easy to find real problems, and it is possible to implement a decent solution for at least some of them. But: many of the problems that various industries have are in my opinion self-inflicted because of their structures. What is hard is convincing potential customers that your solution would help them.
But you can’t fix it by making another multifunctional tool, because you’ll just get people using one or two of your five feature-areas, and two or three other tools for the rest, same as now.
Why is this a problem?
Of course “well just use all the tools the right way and always look where you’re supposed to and put things in the right place” but it never works out so nicely in practice.
[edit] example: paying for a half dozen services that provide, between them, two code repo hosting solutions, four CI solutions, six wiki solutions (LOL), two cloud hosting solutions, two CDNs, three issue trackers, and on and on… and mixing and matching those such that it requires daily manual upkeep to synchronize info between them (you’re not using all the features of each one, to be clear—or, if you’re really in hell, maybe you are), onboarding is messier than it could be, account management is a pain, you’re over-paying at least a bit on everything, “where did/does that go?” is a constant question, everyone needs several pinned tabs opened when they could have, like, two, et c et c. Usually the reasons for doing this aren’t even strong, it’s just how things have ended up.
What's that threshold? Well, that's the hard part. :)
I would bet my entire salary you only believe this because you don't understand the constraints. When I was in my 20's and thought I knew everything I had the same attitude. I have since gained seniorship and worked in regulated industries and it's much clearer to me now. People in the industries you're talking about are generally smart and well meaning, but the constraints imposed by things like regulation and legacy systems (internal and external) make things that seem like they should be easy really hard.
I would counter bet that:
i) I do know quite some of the constraints (though surely not all).
ii) Quite of these these constraints are self-imposed prisons that the respective company/industry created for itself because of historical or "political" reasons.
What you call "constraints" is something that I would rather call "the industry's preferred flavor". Well, I do have a different taste than the respective industry. :-)
Believe me: In the past, when I was frustrated of my job, I made use of an opportunity to present some ideas that I had to some former friend who has been working in business consulting for many years: he really told me that some my ideas could be as impactful for the respective industries as I imagine it, but they would be insanely hard to sell (and a huge part of his job is selling things to customers) because they so different.
To give an even different perspective: at my current emplyer's Christmas party, my boss' boss said that I am the kind of person who cannot be classified on an optimist-pessimist scale, since I don't behave like an optimist or pessimist, but rather like an statistical outlier in a data set. :-)
I made the decision to first get real work experience in a relevant industry, learn the problems there and only then start building a product. This opens up the door to building software for industries like the AEC industry, defense or healthcare, where you could have far greater impact, instead of getting stuck on building todo apps, online communities or platforms.