[mattfrommars]

Amazing stuff. I think I'm in the boat as you OP except I just can't get myself to commit to a project since 1) no idea if it works or is unique 2) look for better opportunity and spend time doing LC/apply for job.

There is only so many hours after work.

> Once you’ve validated your idea,

Could you really break this down. I feel you overlooked this part. How do you filter through tons of ideas into idea that for sure or has good chance for success. For example, to build a yet another crypto exchange is both super technical and far too regulated. What is a known strategy how founder/dev nail down and commit to a project?

[scubakid]

There are many frameworks and approaches, but here are two of my filtering criteria:

1. I don't start a project unless it's something I deeply want to exist for my own personal use. That way I know there's at least one person who would pay for an elegant solution. And even if no one shows up, at least it's useful to me.

2. I don't start a project unless I can envision the solution top to bottom and feel confident about the scope of the technical work. I'm not the most brilliant person at data structures & algorithms, and I prefer solutions where a simple architecture can get the job done. If there are foggy areas in the technical design, or parts I struggle to visualize clearly, to me that's a red flag.

[gilfoyle_7]

Do you make this decision after doing tons of research about how you could implement a solution for the gray areas or do you just decide not to pursue the gray areas that you don't know how to implement yourself?

[scubakid]

Doing some research would definitely be part of the diligence process when considering a new project.

[gilfoyle_7]

ok