Six thinking hats, taught me how to structure my thoughts by wearing multiple hats where hats are perspective

Interesting take on generational wealth.

Interesting satire, would add it to my reading list

In the software engineering world, in 2026 we saw a wave of code assistant products. In 2026, we will see a wave of designing software architecture products, not just on greenfield projects but also brownfield projects.

Thank you so much for sharing this with the community. Starred the project and will definitely try it out within my company. More power to you!

Thanks brihati . Reachout (slack/chat) to us incase you need any support with any usecase

Interesting, how did you come up with this idea? Have you tried it in production workloads?

Thanks! The idea is to build a highly replicated KV/column store for the edge: small Raft core for ordering, lots of async replicas. I have it running on a 30-node fanout in test/staging and am focusing on hardening (crash/recovery, backpressure) before production.

I agree. have you tried any framework such as spec-kit by Microsoft to generate feature specs?

i have not. Just a personal preference to write specs myself because i want as much control at early planning stages.

Great approach, since you are following a pre-defined set of approaches, have you thought of building an agent for it? or do you have a prompt which helps you with getting the relevant answer?

I have a projects folder in the app which has a set of instructions - bot mostly what documents to follow. It works well enough but you're right, I should push it a bit more.

It's great that we can iterate on the solutions and they become general.

What you say is what you get

The problem with ambiguous boundaries, messy constraints and the perception that there is no linear path to transferring meaning in language.

What you don't say is what you don't get

Is 2+2 still 4 :p