Munish Thakur

@shreyansj It’s refreshing to see a company of this size successfully call bs on the whole thing to this extent. One group of MTS on a mission, clean.

if after the bun rust rewrite and 1M code merge in a few days you still think that software engineering hasn’t changed massively idk what to tell you

end-to-end testing > unit tests, in the vibecoding era. A massive, almost entirely agent-coded refactor passed all unit and pre-merge tests but broke a critical feature. It was only caught due to my own excessive paranoia making me run end-to-end tests before the prod deploy.

@championswimmer due to tiered pricing per se

@championswimmer as if this isn’t gonna happen in the future 😭😭😭

Man what a great world would it be if everyone else's Codex/Claude were a bit slower (and they sent slop to review to me slower) and my Codex/Claude were 5x faster so I could push my well-thought-out perfect architecture faster. /s

Truly intelligent people can describe complex ideas in a way that a layman can understand. Being verbose is intentional obfuscation to maintain their little "elite" circle.

@tannerlinsley also quite similar to remix V2s loader pattern which i loved and clicked instantly for me

@tannerlinsley keeps on impressing with his philosophy!

Exactly how I’ve felt about RSCs, like I can see **some** use-cases for it but why does my entire App Architecture has to tip toe around it to get the benefit, why can’t it be some niche tool which i can plug into just one component tree (ik ik not as easy as it sounds)

If someone is waiting on you for a code review, that has to be your P0 task. Look, waiting on a code review is one of the most frustrating things because the person is literally blocked on you. It gets even worse when there is a time zone difference to deal with. I get it. You do not have malicious intent and are genuinely busy with something important. But still, I would say it is a prioritization problem. Most people treat code review as something they get to when they have a quiet moment, and that quiet moment rarely comes. Coming from my personal pain point, I would say treat code review as a high-priority task, not a background one. If your teammate has raised a PR and you are the reviewer, that is important work in progress sitting idle. Every hour it waits is an hour of 'blocked momentum' (yeah, fancy term). Also, it is okay to preempt your non-urgent work for it. This matters even more across time zones because a delayed review does not cost an hour; it costs an entire working day for the other person (ohhh, this used to be such a pain). So the next time you see a PR sitting there, wrap up the review, because it is not "someone else's work"; it is yours. Hope this helps.

yet I continue to remain bullish on React.

i'm done with nextjs. rsc looks good on paper but in practice turns simple apps into distributed systems nobody asked for. you stop thinking in react and start thinking in server/client boundaries and caching rules. it adds abstraction instead of clarity

@kentcdodds have had similar feelings, the composability and simplicity just took a toss, having to always think of server client boundaries in my components . Thank god it’s opt in. 🙏🏻

Ok, I've had enough of this. I'm relieved that I never actually adopted RSC and at this point I'm convinced I never will. I'm now firmly in the camp of "RSC was a bad idea." The problems weren't made up. But this solution is not good.

we don't have to live this way. senior engineers have the duty of building guardrails and teaching the next generation of programmers the practices that lead to high quality software. AIs may write most of the code, but you still decide what ships. we should never lose our taste for quality software. i made this analogy a while back: everyone can cook at home but yet restaurants still exist. the floor is rising, but so is the ceiling. the best software will always be made by those who care.

and this is literally after 5-6 hours of research and back and forth discussing all the edge cases tech and organizational with AI. Normally it would have taken me atleast 3 days to research this by myself 😭🙏🏻

Got nerd sniped into asset and icon management strategy for a Design system that supports 3 Brands (as of now ) and 2 themes (light and dark) and boy oh boy never thought something which i simply used as a Basic <Image/> or inline SVG jsx can become so complex for a generic DS.

Deeply experienced software devs eventually realize the hard thing that takes tremendous talent, experience, and taste is writing the fewest LOC possible. Low LOC has significant benefits across every metric that matters. Entropy management is the whole game.

@atulkawasthi agreed, we need re calibration in how PRDs are created now.

@munish710 Hybrid works best: AI drafts + PM ownership + early dev input before finalizing the things. bt ye ni hoga i know😇

what are your thoughts on AI generated PRDs being given by PMs .I understand using AI to rephrase or proof read the PRDs but actual PRDs being created by AI, like they are great cover all scenarios and edge cases but are always too generic and are more like wish list!

@atulkawasthi Can u elaborate more if the focus is more on business points, thats not a bad thing, feasible or not is anywyas devs responsibility upon grooming?

@munish710 They mostly focus on business points not dev points, is it feasible or not, is lacking now,

@Palakgupta2712 and since it was mentioned in the PRD u as a dev are being lazy and dont want to do it 😔 is what ppl think bow, esp since we have given u cursor

@munish710 haha 😅 true that, every feature is important