Luciano Mammino 𝕏 Node.js Design Patterns

🎉 Big news and a gift for you 🎁 Keep reading🧵👇

@58bits @tannerlinsley let's leave it for another time, when i'll be able to provide more meaningful feedback ;)

@loige @tannerlinsley Seriously - attention is worth everything these days. Would be glad to make a donation to wherever you like 💝

Byline CMS docs are _much_ better. Still work to do - but, I'll donate 100.00 USD to a charity of your choice if you spend 15min looking at them and tell me what you think @tannerlinsley @loige ;-)

@58bits @tannerlinsley PS: nah no worries. Happy to help! ... Although I wish I could do more. Hopefully I'll work on a project requiring a CMS soon. That would be a great way to spend more time actively playing around with Byline!

4:06am at this end. @tannerlinsley , @loige if you take me up on the offer, I'll reply via DM when I wake up :-)

@58bits @tannerlinsley Heya! I had a quick glance and I have to say i really like the overall structure and the general tone. I'd need to deep dive more for a better feedback though. PS: also the landing page has improved a lot since last time I checked! Awesome work

@58bits Still, I agree it requires a significant amount of human supervision if you care about not just the outcome but also about keeping code quality to sane levels.

@58bits I can share most of these feelings based on my experiments. I am trying to expand the matrix of models and started to include GLM5.2 (and hopefully soon Kimi M3) and it's interesting to see they find more useful stuff when reviewing each other code.

Another multi-day session with Opus, Fable, and Sol. Quite a few impressions from all of this. The first, if you're punching above your weight (as we nearly are) - you can easily lose control of the codebase and end up in deep trouble with a spiralling downward LLM conversation full of self-loathing and never-ending self-admonishments and attempted corrections. Second, even with the best environment - including skills, verification and feedback loops and an already well-structured codebase - LLMs still make stuff up. You have to be on top of it - all the time. Press for clarification, press for testing assumptions before proceeding, and probably most importantly, press for expanded adjacency if you're going to let the LLM edit a hot path, or a critical part of the application. It feels to me like LLMs (even with the best harnesses) are like children savants - extraordinary abilities when looking straight ahead or directly behind, but totally blind in 'looking around'. Whether it's conceptual integrity (as Frederick P. Brooks described so perfectly in 1975), or just 'intuition' - adjacency is what LLMs are really terrible at (perhaps ironically too given their entire model is based on probabilistic adjacency). (Note: I wrote this without the help of an LLM. These are human words ;-)) @tannerlinsley @matteocollina @loige

@matteocollina I find beneficial to have them doing an adversarial review of each other but also to swap which model is implementing vs which one is reviewing every once in a while. I don't have any meaningful metric but my feeling is that it leads to a bit more variety and can spark new ideas.

I'm currently developing a new product with a combo of fable + gpt 5.6, one implementing ant the other one review.

@matteocollina @github Congrats and absolutely well deserved! Long time coming 🎉

After 16+ years on @github, I’m finally a star. ⭐️

Environment variables in Node.js look trivial until they bite you: everything is a string, "false" is truthy, and every child process you spawn inherits your secrets. I just published a complete guide. Here's the short version 🧵

The pattern that ties it all together: one config module, validated at startup, fail fast. The rest of the code never touches process.env directly. Full guide (validation with Zod, security, NODE_DEBUG and friends): nodejsdesignpatterns.com/blog/nodejs-en…

NODE_ENV=production does not make your app faster by itself. ... BTW It's a convention, not a Node.js feature. It just tells your dependencies (Express, React, bundlers) to behave like production. If they don't check it, nothing changes.

@mitsuhiko I am not sure how the license would apply, but the git history is still there... github.com/daytonaio/dayt…

Good news everybody! Readme and logo remains free to fork and build on. I guess the open to closed source switcheroos are kicking in at inference speeds now too.

@jenewland1999 💯! I was going to put a graph of the new release timeline (like the one in the official site) in the article but then I realized the new approach makes things so easy that a timeline is pretty much superfluous! The Node.js community is truly awesome! 😎

Really grateful to the Node.js TSC for their thoughtful and thorough deliberation on this too. There's a lot that goes into big decisions like this and I think overall this change is going to really help in the understanding and keeping systems more up to date.