adzicg

It's not impossible, it's just difficult :) Luck plays part like in anything, but consistency and persistence also makes it possible for luck to happen.

I'd recommend scratching your itch first and then finding people in a similar situation. You know enough about your own problem to be able to design a solution around it, and you likely know some other people around that as well. Slice that segment into something worth attacking first. Bill Aulet defined the first group of people worth solving for as a "beachhead market". This is his test for that first segment:

- the customers within the market should all buy similar products

- the customers within the market should have a similar sales cycle and expect products to provide value in similar ways

- the customers within the market talk to each other, and there is a high probability of word-of-mouth referrals, where customers can serve as a “compelling and high-value references for one another in making purchases”.

The third one is for me the key to open doors as a solo founder. You probably don't have the marketing budget to compete with large companies, so word of mouth and happy customers will be your first best marketing strategy. SEO is black magic, and from my experience takes a long time to actually start working - happy customers doing word of mouth and writing/recommending you also helps significantly with that.

Once this segment opens the doors, things will likely change for something else, then you follow the trail.

Hey HN,

Had to record some videos and ended up building a simple teleprompter browser app (all data is stored in local storage, never leaves the browser). It has basic markdown highlighting support (bold/italic) and works with most clickers to speed up/slow down the reading speed.

I found out about dialectical bootstrapping yesterday, looks like a good way to get AI agents to think a bit deeper, but seems to be one of those techniques that help humans do better work as well. In a nutshell, it's a systematic "prompt" for thinking about plausible alternatives and then providing a second guess.

tdd is very present in our process, it's mandated by CONTIRIBUTING.md with very specific instructions on how to structure tests.

hahaha. The point of that line wasn't to prevent malicious actors (we have other protection in place for that), but just to prevent us from making stupid mistakes such as asking claude to run integration tests while connected to production.