Pavel Grinchenko

@eugeniu_ghelbur @evilmartians With React specifically, LLMs put all business logic right into components, like many devs do nowadays. This binds code to React runtime, makes testing harder, and slows you down when extending. And I'm not even mentioning useState/useEffect spaghetti.

@eugeniu_ghelbur @evilmartians LLMs handle isolated small features quite well, but when it comes to developing robust and extensible architecture—they usually suck. LLMs can't know how you're going to extend your project or what to consider from the start.

All the buzz around Claude Code got us thinking of these words by @psd_coder: "AI models learn from the code that’s available online. Of course, statistically speaking, most code out there is average. So when AI generates code, it gives you the most common patterns. Not necessarily the best ones." So, while Claude Code is, in our opinion, the best tool for vibe coding and code gen, you still need a developer who can: - Manually edit changes (models use copy/paste instead of reuse) - Design systems instead of treating architecture as an afterthought - Refactor code as you go to avoid technical debt

@FabianHiller @harshmangalam_ @valibot And it's easy to check it with bundlejs.org (which uses esbuild). It's 778 B for wildcard imports and 774 B for named imports, which is effectively the same. The small difference is likely due to slightly different minification. diffchecker.com/66IiC37g/

@harshmangalam_ @valibot Common bundlers should support tree shaking with wildcard imports too as these imports a seen as static.

1/ 🧵Tree Shaking explained (simple) Ever imported a library… but used only 2 functions out of 20? Tree Shaking removes unused exports at build time, so only what you use ends up in the production bundle.

8/8 Submitted a PR to Astro docs—now it clearly explains the behavior when expiration isn't set: github.com/withastro/docs… If you're using ISR with custom cache headers—check your expiration config. A day of debugging, a 1-line fix. Hope this saves some time for others.

7/8The fix—set any expiration value: vercel({ isr: { expiration: 60 * 60 * 24 * 365 } }). Now Cache-Control works. Time-based invalidation works. Manual invalidation still works.

1/8 Spent a full day debugging why our custom Cache-Control headers were being ignored in Astro on Vercel. Fix? One line of config. Here’s what happened ⬇️

Zod Mini is a step forward, but in the battle of tree-shaking as an afterthought vs. tree-shaking as a foundation—the latter wins. Highly recommend Valibot if bundle size matters to you!

Vibe coding works. Until it doesn't. After seeing dozens of AI-generated codebases, the pattern is clear: what gets you to "it works" won't get you to "it's ready for users." Wrote about why you need a developer to turn a vibe-coded POC into a real product evilmartians.com/chronicles/why…

This is the most visual explanation of types in TS. I love it!

Better later than never. Finally got around to the second @pgurtovaya article about image formats! She tells how image codecs work. Great reading! developer.mozilla.org/en-US/blog/ima…

Meet a new mind maps importing/exporting Figma plugin that my fellow developed! @yurimikhin congrats with the release!

We have published new feature in Harmonizer: now you can set custom limit for chroma! Enjoy it!

@AleksandrSl28 Не, ну при 37.2 ты ещё сможешь написать пару несложных плагинов к идее. Про пик Балмера слышал?

Кто делает сертификацию этих электронных градусников Я уже при смерти, очевидно у меня 37.2, какие 36.8 сраный ты кусок пластика

I'm lucky to work with the best backend developers (from Evil Martians, of course), so this problem is mostly irrelevant for me. But deep in my memory, I remember the pain described in my colleague @yurimikhin's article—and API contracts look like a good option to solve it!

A solid intro explaining how our eyes perceive light and colors, and why we need all those colors spaces from @pgurtovaya. Can't wait the continuation! developer.mozilla.org/en-US/blog/col…