The plan is kinda simple "Make it exist first, you can make it good later" hehe

At what point does spending this much time in Terminal become a personality trait?

Btw, if you're learning a new language, framework, or tool, don't sleep on its conference talks. Learning Docker? Watch DockerCon. Learning React? Watch React Conf. Kubernetes? KubeCon. You'll often learn more from the people who actually built and use these tools than from most tutorials.

Will apply for yc endewum 😁

Decide to go with this for now and done with All ui migration hehe

Ngl it takes all my mental Fr

Also

Oops

I let it do its thing while I’m eating.

Me….Little realization

More features ≠ better product.
just because we can build something doesn't mean we should.
More features don't make a better product. Every one adds another thing for the user to understand, navigate, and carry.
So the question isn't "can we add this?" It's "does this make their experience meaningfully better?"
Software isn't everything we were capable of building. It's the things that deserve to exist

♟ often you don't have feature problme but a sequencing problme.

ከ Real problem ወደ Validated solution ወደ Viable economics ወደ Focused plan ወደ
Disciplined execution ወደ Successful launch ወደ Measured learning ወደ (loop back)

miss any link and you get the predictable failures, feature-rich products nobody wants, well-loved products that lose money, or great launches that fizzle because support/sales weren't ready.

features appear only as candidates for achieving each goal. if you can't trace a feature backward through that chain, it is probably a candidate for deletion.
sequence it well.

Day 6
For today … I just wanted to share the thing I promised last time [here]
So I related some real-life experience with the distributed system CAP theorem, so I just published the draft check it out :)))

New tool Soon btw