brihati

I use both Codex & Claude Code. With Codex, their long running agents are still not as good as Claude Code. But I don't complain because they burn very less tokens as compared to Claude Code for the same task. But having said that, if I am provided limitless tokens for each of them, my go to harness will be Claude Code

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!

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

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

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?

What you say is what you get

Is 2+2 still 4 :p

In distributed systems, at least we have the variables, functions, pods, log traces, spans etc some pre defined structure, and some level of determinism. I would say Causality is still not fully explored territory when it comes to human brain.

When I think of human brain or may be to some extent LLMs, it's difficult to understand what is invisible. For distributed systems we will build tools, there is ongoing research in LLM Observability, but I wonder what about human brain

I come to HN because it's one of the few places left where you can sill watch people think and present new ideas. The people in the world has done intellectual outsourcing, where instead of grappling with the idea themselves, they ask LLMs to predict the next sentence, which has hollowed the real curiosity.

What makes HN valuable to me is the opposite impulse: people trying to understand things for themselves from the community and in the process, maybe, discovering new ideas which LLMs can't supply. Because what LLMs don't know they don't know, LLMs think they know(that's why they predict next sentence) but we know they don't know and still some people think they know

Sometimes, I wish, there is no thinking tax: as a reminder of why this place exists & also to reward people who are still curious and thinkers

I WANT HN TO REMAIN A PLACE WHERE HUMAN CONVERSATIONS STILL HAPPENS.

This was fun, I enjoyed it while claude was busy writing code

BloodHound team: blood is in your hands. You’ve taken the name of an established security tool and attached it to what, based on your description, looks like a lightly engineered LLM-driven wrapper

First of all, thanks for the contributing to the community. This is a good observability tool to reproduce reasoning paths using structured trace of prompts. During this process, I sometimes do replay the prompts also, especially for some of the use cases where we have observed near deterministic behaviour for some standard prompts. Do you have any plans for adding this feature?

Another question: can your architecture scale to thousands of developers & millions of traces?

Frankly, I was unable to distill what you are trying to achieve here

This article argues that the real fragility in engineering teams isn’t the bus factor, it's the loss of decision context. Most systems depend on knowledge locked in a few heads, and when that disappears, teams pay for it in outages, rewrites, and slow recovery. The post proposes a simple operating model: capturing intent through decision logs, enforcing a technical "constitution" and using automation to reduce drift, so teams can scale without accumulating invisible risk.

I would love to hear from the community how are you handling tribal knowledge within your organisation

Post link: https://brihatijain.com/blog/beyond_the_bus_factor

Really interesting project, it nudges you toward learning instead of mindless feeds.

One suggestion: could you add tags to the research papers so readers can more easily filter by their interests? For example, I’m looking to follow recent work from top venues like NeurIPS specifically on training code-oriented LLMs. Tagging would make it much easier to dive into topics like that.

Thanks for your effort

Really interesting idea, thanks for sharing. When working on new projects, a lot of my learning comes from studying what others have already built so I can reuse patterns around architecture, UX, and product decisions. Those learnings tend to be transferable across tech stacks, so they’re not tightly bound to a specific programming language. Could you share the thinking behind using programming language as the primary way to organize or distill these examples?

As a user, clicking an icon in Chrome to analyze the video I’m currently watching is way lower friction than copy‑pasting links into a website

A website makes more sense for businesses, investigators, or military users who need dashboards, exports, and controlled workflows.

Either ways: good luck

Why another tool for solo founders? Given the number of tools like Asana, Trello, Notion, ClickUp etc., the bar for “yet another productivity app” is very high, especially for solo founders who already feel tool‑fatigue. If the goal is to justify a new tool, it needs a very sharp, explicit thesis such as “most tools help you track everything, Tinyfocus only forces you to do the 3 things that actually move the business.”

“More done in less time”: Right now that claim sounds like generic marketing. You could make it concrete by defining: What specific behavior Tinyfocus enforces (e.g., forces you to pick 3 MITs, limits WIP, shows a single “today” view).

How you’ll measure the impact: % days where all 3 tasks are done, reduction in active tasks, or fewer context switches per day.

Even anecdotal metrics like “users report shipping more often and feeling less overwhelmed after switching from a general todo tool” would already be stronger than a vague promise.

Differentiation vs Trello and others From the landing page and description, it’s still hard to see why a solo founder should use Tinyfocus over a simple Trello board or similar lightweight tools.

I don't know if any tool exists in this space or now: founders get ideas in transit, in the shower, between calls, and the friction of opening an app/website, navigating to the right place, and typing is real. A “voice‑first” capture flow (via Siri/Google Assistant/shortcuts) that instantly dumps tasks into Tinyfocus without opening the app would directly attack this friction