Udit Kapoor

Building @buildtrailapp — startup journey in public

Software Engineer & Founder

My BuildTrail Journey → yours →

[Udit Kapoor @itsuditkapoor]

Nobody tells you this about “building in public”:

It’s not just posting screenshots or revenue.

It’s documenting:
• the confusion
• the pivots
• the slow days
• the small wins

Wrote about what “building in public” actually means in 2026 👇
https://t.co/bktqtMt548

#buildinpublic

[Udit Kapoor @itsuditkapoor]

@craigweiss The interesting question is what you're actually paying for now. Not the code, but the convenience, hosting, integrations, and not having to maintain it.

[Udit Kapoor @itsuditkapoor]

@AlexHormozi I think the harder part is diagnosing the problem before deciding whether the person or the role is the issue.

[Udit Kapoor @itsuditkapoor]

@nikks_techie I’d put a guardrail between the agent and prod: read-only DB user, query validation, EXPLAIN/cost checks, statement timeout, and resource limits. Never let generated SQL execute unrestricted.

[Udit Kapoor @itsuditkapoor]

@thekitze Honestly, 2030 feels way too close for how insane everything is getting.

[Udit Kapoor @itsuditkapoor]

@JeenaKrish91074 greet() needs an argument 😂 You defined greet(user) but called it without passing user

[Udit Kapoor @itsuditkapoor]

@code_bytein The classic problem is a lost update: both transactions read the same value, modify it, and one overwrites the other. Transactions + appropriate row-level locking or optimistic locking can prevent that.

[Udit Kapoor @itsuditkapoor]

@dark_coderz D. 429 - Too Many Requests. Basically the server telling you to chill 😂

[Udit Kapoor @itsuditkapoor]

@TheGBreaker The interesting part is that starting online has become much easier. The hard part is still building something people consistently pay for.

[Udit Kapoor @itsuditkapoor]

@arvidkahl The interesting shift is going from AI that can execute instructions to AI that can understand context and make decisions on its own.

[Udit Kapoor @itsuditkapoor]

@alexabelonix 100 users. Then I’d spend my time figuring out why those 100 care so much and how to find 1,000 more people like them.

[Udit Kapoor @itsuditkapoor]

One thing I keep thinking about with BuildTrail:

Founders already have GitHub.
Notion.
Linear.
Analytics.
Stripe.
X.

The problem isn't lack of data.
It's turning all of that into a story people can actually follow.

[Udit Kapoor @itsuditkapoor]

@DanielSmidstrup Yeah, and that's probably why the agencies struggle with it. You can outsource content production, but it's harder to outsource actually understanding the community.

[Udit Kapoor @itsuditkapoor]

@dark_coderz Vibe coding is great until the codebase becomes big enough that you're debugging decisions you don't even remember making 😂

[Udit Kapoor @itsuditkapoor]

@agazdecki You start thinking you're building a company and eventually realize you're also building a much better understanding of yourself.

[Udit Kapoor @itsuditkapoor]

@SumitM_X EXISTS feels like the cleanest answer here. You only care whether at least one matching order exists, not about fetching the orders.

[Udit Kapoor @itsuditkapoor]

One TypeScript habit I'm trying to build:

Don't make types describe what I hope the API returns.

Make them describe what the API can actually return.

The difference becomes very obvious when the API starts failing.

[Udit Kapoor @itsuditkapoor]

@arvidkahl The funny part is that Claude's 20 minutes usually leave you with an artifact. Most 2-hour meetings leave you with another meeting.

[Udit Kapoor @itsuditkapoor]

@skpnky Shipping is becoming table stakes. Distribution, understanding users, and actually getting people to care is where the competition moves next.

[Udit Kapoor @itsuditkapoor]

@SumitM_X The interesting part isn't really COUNT vs LIMIT. If you're checking existence, EXISTS makes the intent much clearer