Maksim Sinik
@maksim.dev
Senior Engineering Manager @TrustLayerIO - @fastify.dev core team https://github.com/fox1t - Book Author "Accelerating Server-Side Development with Fastify" http://packt.link/DvIDB
Same grade of confusion.
August 15, 2025 at 12:17 PM
Same grade of confusion.
Even with this fast path to become a structural part? openai.com/global-affai...
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...
openai.com
August 13, 2025 at 6:20 AM
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.
August 11, 2025 at 7:35 PM
Oh! This is amazing. I am still working with Claude Code opus/sonnet, and I do not need to try something different.
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.
August 10, 2025 at 10:36 AM
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.”
This picture is so cool, James!
August 8, 2025 at 7:16 AM
This picture is so cool, James!
I think one is the consequence of the other. I wrote this thing. backend.cafe/beyond-vibe-...
Let me know if it helps. 😃
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
backend.cafe
August 7, 2025 at 6:13 PM
I think one is the consequence of the other. I wrote this thing. backend.cafe/beyond-vibe-...
Let me know if it helps. 😃
Let me know if it helps. 😃
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.
August 7, 2025 at 6:45 AM
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.
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 :)
I guess my post already exists :)
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.
humanwhocodes.com
August 7, 2025 at 6:45 AM
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 :)
I guess my post already exists :)
I definitely agree with you, but not everyone agrees with us. 😔
August 2, 2025 at 8:54 PM
I definitely agree with you, but not everyone agrees with us. 😔
Humans have the same error rate, though.
August 2, 2025 at 7:46 PM
Humans have the same error rate, though.
I fucking love the picture!!!!!
June 27, 2025 at 11:32 AM
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
June 9, 2025 at 7:01 PM
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.
June 9, 2025 at 10:20 AM
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.
Is it FE, BE or both? Depending on it, you have different options.
May 24, 2025 at 6:33 PM
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 :))
May 23, 2025 at 10:48 AM
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 :))
You can point the npmjs link directly to the correct package in the monorepo, and that package is effectively what is published. The issue you are describing is misconfiguration on the repository field in the package.json 🤷♂️
May 23, 2025 at 6:33 AM
You can point the npmjs link directly to the correct package in the monorepo, and that package is effectively what is published. The issue you are describing is misconfiguration on the repository field in the package.json 🤷♂️