Sumedha Kulkarni (@_rootsrk) header
Sumedha Kulkarni (@_rootsrk) profile picture

Senior "vibe code" janitor. All things frontend. Always caffeinated. Serial reposter.

Toronto 🇨🇦
Joined December 2014
Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)Photo by Sumedha Kulkarni (@_rootsrk)
Sumedha Kulkarni retweeted
From vibe code to verified code…
AI is forcing us to make software be an actual engineering discipline, AI generated code behaves similar to physical matter, engineers need to understand durable principles, know how to measure, and know how to control production. Not just assume code will do “the right thing” because we’ve crafted it ourselves, atom by atom.
220
220
47
3,363
251,697
Sumedha Kulkarni retweeted
realizing all the hard shit you accomplished on your resume pre 2026 is just a prompt now
103
541
69
9,132
220,122
This is the most beautiful thing on the internet. If you’re an engineer who’s contemplating what the role is going to be like, maybe this will give you some food for thought.
A wild scrolling experience exploring what the job of the Human (designer) is in the era of AI. human-md.ai is worth a scroll and may even have you laughing at times.
29
Sumedha Kulkarni retweeted
i may be a meat proxy but at least im like an a5 wagyu quality meat proxy
35
159
14
2,880
70,986
Sumedha Kulkarni retweeted
Replying to @sm0olr
echo "Tautological labels, tests, and UI components are considered harmful." >> AGENTS.md
8
2
1
445
24,854
Sumedha Kulkarni retweeted
- do this and don’t stop until done - review and make sure it doesn’t suck omg i have a software factory
Honestly, I still don't even know how to setup a software factory and I am too embarrassed to admit it
13
3
1
308
9,654
Sumedha Kulkarni retweeted
does anyone remember how to code
2,056
589
398
13,499
974,220
Sumedha Kulkarni retweeted
The sort of thing your agent writes tests for
The chances of being killed by a landmine delivered by a bear are low, but they are never zero.
77
835
36
14,207
328,654
If you have a few minutes, this was a really nice read on the tension between a process and a culture problem.
You CANNOT fix CULTURE with PROCESS. Earlier this year, one of my sales managers slacked me a new Google Form. Every sales engineer (SE) would have to fill it out before every customer call. FOREVER. I get why he created it. A rep on his team showed up to a call the prior week unprepared. The SE was there too, just as unprepared. He spent the call asking the customer questions we should have known the answers to before we ever dialed in. They wasted the customer's time. So he did what most managers would do: "I'm going to create a process so this never happens again - so now before an SE or an AM gets on a call to show the product, they have to fill out this form." Then he spent his Saturday - his Saturday - building a 14-question intake form. Required for every SE. Before every customer call. FOREVER. That is not the answer. You don’t fix unprepared reps with a form. You build a culture where nobody shows up unprepared in the first place. Every process you add is a TAX. And you CHARGE that tax to every person on your team who never had the problem - every day, forever - to fix the one person who shouldn't have been there in the first place. Stack enough of those and you end up with processes on top of processes and everything slows down. Some processes are worth the tax. Most aren't. This one wasn’t, so I told him to kill the form and do this instead: Before you build a process, say the standard OUT LOUD. Get the team on a call, tell them what happened and tell them what the standard is. In our case: “Competing with ZoomInfo should be a DAUNTING experience for ANY of our competitors. This is NEVER acceptable. Showing up unprepared to a customer call doesn't live up to that. Full stop.” Point back to that standard every time someone misses it. Let the people who can't meet it self-select out. Manager: "But Henry, what if it happens again?" Then it happens again. And you have the conversation again. Louder this time. Process fixes broken systems - it doesn’t fix broken standards. Start with the standards.
2
235
Sumedha Kulkarni retweeted
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month. I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
646
1,561
751
15,611
2,863,092
Sumedha Kulkarni retweeted
Unpopular opinion: the people getting the most out of AI are the ones who could do the work without it.
335
526
135
5,965
229,493
Sumedha Kulkarni retweeted
one day you wrote console.log("here") for the last time and didn't even know it
213
1,723
269
17,842
611,534
First they came for the software engineers, I said nothing for I was not a software engineer. Then they came for the mathematicians, I said nothing for I was not a mathematician. Then they came for the product managers and I said "make sure you get all the product managers"
39
269
8
5,757
117,689
Sumedha Kulkarni retweeted
me watching Claude fill my repo with unit tests and emojis
A mom watching her son's wrestling match đź‘€
16
85
2
2,881
45,117
Sumedha Kulkarni retweeted
Dressing for Fall in Canada:
17
631
29
5,909
67,759
Sumedha Kulkarni retweeted
how it feels to get better at AI coding
23
130
16
2,364
71,016
Sumedha Kulkarni retweeted
20
130
14
3,910
109,506
Sumedha Kulkarni retweeted
every app is being CHAT-ified.
117
1,590
487
16,087
2,094,982
Sumedha Kulkarni retweeted
Babe wake up, automated TTC subway cleaning robots just dropped
71
164
72
2,276
137,714
Sumedha Kulkarni retweeted
Introducing shadcn/lint. An agent-first linter for Tailwind design systems. You define what’s allowed. When an agent breaks a rule, the error explains what’s wrong and how to fix it using your components, variants and theme. There’s a lot you can do with this. Let me show you ↓ github.com/shadcn-ui/lint
218
446
167
6,572
1,208,862