Prakash Donga

Building @solutelabs

[Prakash Donga @prakashdonga8]

@pierreeliottlal @romanbuildsaas GOJI

[Guillermo Rauch @rauchg]

Everyone is now a programmer, because the present and future programming language is your natural language. If you can write or speak, you can build. This is the most important evolution in our field since its creation. And it's a tsunami that has *just* started.

[Prakash Donga @prakashdonga8]

@toddsaunders You need to now start cotton mills 🤣 people expecting a clothing brand from you

[Akshay Kothari @akothari]

Imagine a world where we simplify every role in a company down to just two:
1. Builders
2. Sellers

[Nikunj Kothari @nikunj]

What’s funny is I’ll meet so many people in SF who’ll claim they are tokenmaxxing and have all of these subagents looping things for them..

But when I ask them “what” and for “whom” are they building, very few can give me a straight answer.

Shows that even in this insane AI era, simplicity and direction are still ridiculously important.

So before you let your tokens go brrr, take some time to think if what you’re building (for a living) is actually important.

Time is literally the only thing you don’t get back!

[Prakash Donga @prakashdonga8]

@businessbarista ai

[Tom Blomfield @t_blom]

Every piece of advice is a reaction to something that came before.

"Validate your idea before you go all-in" was a reaction to MBAs raising millions of dollars based on nothing but a business plan.

Today, young builders take that advice and quickly "invalidate" every idea they come up with.

Now the missing ingredient is conviction 🤷‍♂️

[Justin Welsh @thejustinwelsh]

The dumb guy who starts a business will always be wealthier than the academic who writes theory about business.

[Ashwin Gopinath @ashwingop]

Claude Tag is a Trojan horse.  Not because Anthropic is doing anything evil. Because the incentives are obvious.

Day one, this looks like a great feature: tag Claude in Slack, let it follow the thread, remember context, connect to tools, break down tasks, chase work, and act like a teammate.

But that is exactly the problem. The moment your AI vendor becomes a shared coworker, it stops being just a model provider. It starts becoming the place where work is interpreted, remembered, routed, and eventually executed.

That is not model lock-in. That is context lock-in. You are now renting your company back from them.

Models can be swapped. Agents can be copied. But the memory of how your company actually works is much harder, maybe impossible, to move: the Slack scar tissue, the exception paths, the customer promises, the unfinished threads, the weird workflows, the implicit owners, the “we tried that in Q2 and it failed” knowledge.

Once that lives inside one vendor’s agent layer, you are not renting intelligence anymore. You are renting your company’s operating memory.

And the pricing model makes it even more dangerous. A human coworker has a salary. Claude has unbounded tokenized activity. The more work moves through it, the more the vendor captures not just IT spend, but labor spend.

This is the enterprise bargain people will regret: Convenience now, and rapid decent into dependency.

The right architecture is simple: rent the best intelligence from whoever is best this month. OpenAI, Anthropic, Gemini, open source, whatever. But own the context layer.

Your company memory should be inspectable, permissioned, portable, and model-neutral. It should not be buried inside the same vendor that sells you the intelligence and the workflow surface.

Claude Tag is useful. That is why it is dangerous. Rent the intelligence, but own the context. Or, regret later.

[Prakash Donga @prakashdonga8]

A software engineer doesn't fail because they used AI. They fail when 'prompt-to-code' replaces judgment - every block of AI slop they merge becomes debt the whole team carries.

[Karthik Hariharan @hkarthik]

Several software engineers will end up leaving the field.

Over the last 15 years, software engineering became a reliable, well paid job. This grew the field immensely.

Now it’s more like it was before this period: a job only for the people who crave change and adaption, even if it means less stability and predictably. And may not end up paying as well as it used to.

[Deedy @deedydas]

Most software engineers are facing an identity crisis bordering on depression.

As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.

The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.

The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.

This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.

[Suhail @Suhail]

My favorite @elonmusk quote that I often send friends:

Do not fear losing. “You will lose,” Musk says. “It will hurt the first fifty times. When you get used to losing, you will play each game with less emotion.” You will be more fearless, take more risks.

[Prakash Donga @prakashdonga8]

Models are becoming commodities; judgment is the moat.

[Nikunj Kothari @nikunj]

https://t.co/N1t71afKPF

[Nikunj Kothari @nikunj]

My shot at how application companies survive the “what if large lab builds this” question 😅

[Prakash Donga @prakashdonga8]

@Codie_Sanchez SMB

[Naval @naval]

Co-founder is marriage without the sex.

[Lorwen Harris Nagle, PhD @LORWEN108]

A Stanford psychiatrist says modern anxiety is not caused by danger.

It's caused by tiny habits that teach your brain to panic when nothing is actually wrong.

You do them every day.
And you call them normal.

6 normal habits quietly teaching your nervous system to panic:▼▼▼

1/ Reaching for your phone the moment you feel uncomfortable.

[Prakash Donga @prakashdonga8]

@gregisenberg Urgency is real, I feel it.

[Paras Chopra @paraschopra]

All vibecoders eventually realize that the difficulty was never in building the product; rather it was in acquiring users.