Naresh khatri (@notHotChaddi) profile picture

Hello im naresh. Im socially awkward 👉👈

Joined July 2017
Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)Photo by Naresh khatri (@notHotChaddi)
Naresh khatri retweeted
Replying to @OpenAI
@OpenAI really bit off more than it could chew. Got everyone hooked with resets, burned through the compute, and now they're quietly squeezing users with pathetic limits. Amazing way to punish the users who switched from claude thinking it's better here @thsottiaux
1
1
1
30
Naresh khatri retweeted
Big one today — Tailwind is joining Shopify 🛍️
1,261
1,118
527
15,785
1,206,996
Naresh khatri retweeted
// AGENTS.md Never, ever, under any circumstances, ever, not once, no matter what, try to start the fucking dev server, it’s already fucking running.
303
278
69
6,597
299,464
Naresh khatri retweeted
software is still about thinking software has always been about taking ambiguous human needs and crystallizing them into precise, interlocking systems. the craft is in the breakdown: which abstractions to create, where boundaries should live, how pieces communicate. coding with ai today creates a new trap: the illusion of speed without structure. you can generate code fast, but without clear system architecture – the real boundaries, the actual invariants, the core abstractions – you end up with a pile that works until it doesn't. it's slop because there's no coherent mental model underneath. ai doesn't replace systems thinking – it amplifies the cost of not doing it. if you don't know what you want structurally, ai fills gaps with whatever pattern it's seen most. you get generic solutions to specific problems. coupled code where you needed clean boundaries. three different ways of doing the same thing because you never specified the one way. as Cursor handles longer tasks, the gap between "vaguely right direction" and "precisely understood system" compounds exponentially. when agents execute 100 steps instead of 10, your role becomes more important, not less. the skill shifts from "writing every line" to "holding the system in your head and communicating its essence": - define boundaries – what are the core abstractions? what should this component know? where does state live? - specify invariants – what must always be true? what are the constants and defaults that make the system work? - guide decomposition – how should this break down? what's the natural structure? what's stable vs likely to change? - maintain coherence – as ai generates more code, you ensure it fits the mental model, follows patterns, respects boundaries. this is what great architects and designers do: they don't write every line, but they hold the system design and guide toward coherence. agents are just very fast, very literal team members. the danger is skipping the thinking because ai makes it feel optional. people prompt their way into codebases they don't understand. can't debug because they never designed it. can't extend because there's no structure, just accumulated features. people who think deeply about systems can now move 100x faster. you spend time on the hard problem – understanding what you're building and why – and ai handles mechanical translation. you're not bogged down in syntax, so you stay in the architectural layer longer. the future isn't "ai replaces programmers" or "everyone can code now." it's "people who think clearly about systems build incredibly fast, and people who don't generate slop at scale." the skill becomes: holding complexity, breaking it down cleanly, communicating structure precisely. less syntax, more systems. less implementation, more architecture. less writing code, more designing coherence. humans are great at seeing patterns, understanding tradeoffs, making judgment calls about how things should fit together. ai can't save you from unclear thinking – it just makes unclear thinking run faster.
136
423
116
2,757
232,629
we have done the math (hard) and can confidently predict that 2027 is officially the year of linux on the desktop
96
174
24
4,173
124,400
Naresh khatri retweeted
Playing @Fortnite at 30,000 ft with ping 49-60 on @AlaskaAir's new Starlink internet is crazy!!
616
651
262
16,702
33,717,339
Naresh khatri retweeted
3
4
31
4,918
Naresh khatri retweeted
109
554
87
11,084
251,581
Naresh khatri retweeted
Ngl this is me
1
1
3
110
Naresh khatri retweeted
He changed frontend engineering forever. The Satoshi of UI. No one knows his whereabouts or his real name. He didn't ship a component system, he shipped a system to ship component systems.
256
360
64
9,291
718,016
Naresh khatri retweeted
Me after pushing to prod on a Friday night.
42
23
8
647
21,653
Exploring Supabase! Built a small app to test Supabase as a database and file storage solution.Handled user auth,file uploads . Perfect for devs who want PostgreSQL power without backend hassle 👉 Github Repo:- github.com/IzharMohammed/sup… 👉 Live link:- supabase-pskxhtn4g-izhars-pr…
1
2
112
Naresh khatri retweeted
It's easier than ever to de-censor video:
116
748
108
9,078
351,039
Naresh khatri retweeted
TypeScript dev watching JavaScript dev fixing “cannot read properties of undefined”
82
459
59
5,237
417,166