Maksim Sinik

bsky.app/profile/node...

Understandable! Using Coding Agents helps raise confidence, though. Making the code changes is a minimal part of the process, and it is the most delicate one for sure.

100 times this! I’ve never been more empowered to refactor a large codebase with confidence

This is by far the best issue of your newsletter to date. Even if I am biased because I 100% agree with you, I still think that the arguments you use make sense to those who have the opposite view.

You are awesome!

You mean the compiler's source code? 🌝

🎉 Author copies are in! 📚

Holding the 4th edition of “Node.js Design Patterns” never gets old. Months of work turned into something I can touch, and hopefully a guide to help you level up with Node.js.

Same grade of confusion.

Introducing OpenAI for Government We’re launching OpenAI for Government, a new initiative focused on bringing our most advanced AI tools to public servants across the United States. We're supporting the U.S. government's efforts in ad...

Even with this fast path to become a structural part? openai.com/global-affai...

Oh! This is amazing. I am still working with Claude Code opus/sonnet, and I do not need to try something different.

Another banger from Marvin on performance wins in the JS ecosystem 🔥

The theme across the series is that orders-of-magnitude wins are often sitting in plain sight purely from eliminating duplicate work & improving algorithms.

These are language-agnostic principles.

I have been reading your posts about the LLMs for a few days, and I share your vision and concerns. I also agree with this midterm vision: “It is too early to go all-in and rely solely on th AI.”

I predict the AI bubble will pop in way similar to how Google products did in the 2010s. They were "too good to be for free", and eventually advertisements kicked in. Product quality stagnated (just marginal improvements), while monetization ramped up a lot, e.g. ads on YouTube.

This picture is so cool, James!

Beyond Vibe Coding Explore how context management and AI partnership transform coding from chaos to systematic strategy through contextual intelligence

I think one is the consequence of the other. I wrote this thing. backend.cafe/beyond-vibe-...
Let me know if it helps. 😃

Beyond Vibe Coding Explore how context management and AI partnership transform coding from chaos to systematic strategy through contextual intelligence

I've returned to writing after more than two years.

Beyond Vibe Coding Explore how context management and AI partnership transform coding from chaos to systematic strategy through contextual intelligence

I did it backend.cafe/beyond-vibe-...

This new human-AI interaction was transformative for me. My productivity skyrocketed, and the AI outputs started to be predictable. I might adjust the tone of my writing to be more about vibe coding -> structured interaction, and still publish it.

A persona-based approach to AI-assisted software development - Human Who Codes Discover how breaking AI assistance into specialized personas can help you tackle complex software development tasks more efficiently and with less frustration.

I was writing a blog post about how I started using Claude Code effectively a few months ago. Then I read this from you, and you used the same “persona” concept I have. Then, I checked your blog and found humanwhocodes.com/blog/2025/06...

I guess my post already exists :)

Wrong context.

I definitely agree with you, but not everyone agrees with us. 😔

Humans have the same error rate, though.

I fucking love the picture!!!!!

We should complete the migration in the next few weeks and put it in prod on a big internal monorepo. I will end up writing something for sure. I also have a name for the references/starter: “monorepo amara” XD

I discovered this feature by chance and went to update the readme. It is a killer feature for Nofe.js monorepos. If I find some spare time, I will create a reference repository to show the whole workflow.

AST based V8 code coverage is finally here! I thought of this feature first time over 2 years ago, but knew it would require so much work that I couldn't finish it by working on Vitest just on weekends. Ever since @stackblitz.com hired me to work on Vitest I knew I could finish features like this.

I reviewed this edition, and what was already a must-read book is now a mandatory read.
I highly recommend it to seasoned developers as well.

Cover of the book "Node.js Design Patterns, Fourth Edition" by Luciano Mammino and Mario Casciaro. The design features a dark background with a dynamic purple and blue wave pattern. At the top, there is a label saying "Expert Insight" and a hexagon badge that reads "Early Access." The subtitle reads: "Level up your Node.js skills and design production-grade applications using proven techniques." At the bottom, there are black-and-white photos of the authors and the publisher logo "<packt>".

📘 The new edition of Node.js Design Patterns is coming soon!

After 9 months of hard work with Mario Casciaro, we're finally ready to share what’s next for one of the most loved Node.js books.

But this is not “just another edition”...

Is it FE, BE or both? Depending on it, you have different options.

Again, there is a way to generate correct releases and change histories, but I get your point, and I share the struggle (but not the hate :))