@loige

#AWS #Serverless Hero & MVP. Senior Architect @fourTheorem, author of πŸ“• https://xitter.cf/t.co/Vhhe4G48Nf & βœ‰οΈ https://xitter.cf/t.co/XMK2BWxVrL #Nodejs, #JavaScript, #Rust πŸ¦€ & #Cloud ☁️

 eu-west-1
loige.co
Joined April 2009
  • Tweets35.6K
  • Following5.8K
  • Followers9.5K
3KMedia
πŸŽ‰ Big news and a gift for you 🎁 Keep readingπŸ§΅πŸ‘‡
Close-up of a person in a black leather jacket holding the 4th edition of β€œNode.js Design Patterns” by Packt, featuring a black cover with a purple wave graphic and small author headshots (Luciano Mammino and Mario Casciaro), against a light brick background.

ALT Close-up of a person in a black leather jacket holding the 4th edition of β€œNode.js Design Patterns” by Packt, featuring a black cover with a purple wave graphic and small author headshots (Luciano Mammino and Mario Casciaro), against a light brick background.

1
6
1
46
4,482
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Matteo Collina
@matteocollinaOct 20
I didn't pass the Anthropic Cyber Verification Program because I use the personal account sponsored by Anthropic. Note: Node.js does not have a Claude company account. At this point, using top AI models for security is becoming a matter for the few elected. How are we supposed to keep Node.js and other critical infrastructure safe?
48
26
6
546
36,394
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Luciano Mammino 𝕏 Node.js Design Patterns@loigeOct 20
Did you know AWS Lambda's Rust runtime has middleware built in? πŸ¦€ It's powered by Tower, so you can handle tracing, rate limiting, errors and headers without cluttering your business logic. That's Chapter 10 of Crafting Lambda Functions in Rust! πŸš€ 🧡
1
1
3
384
Did you know AWS Lambda's Rust runtime has middleware built in? πŸ¦€ It's powered by Tower, so you can handle tracing, rate limiting, errors and headers without cluttering your business logic. That's Chapter 10 of Crafting Lambda Functions in Rust! πŸš€ 🧡
1
1
3
384
more replies
New cover reveal! πŸŽ¨πŸ”οΈ Our mascot made it to the mountaintop. We're at 10/11 chapters + 4 appendices. Nearly there! All the release details: news.rust-lambda.com/p/new-b…

πŸ¦€ New book release: Wrapping handlers with middleware + two new appendices + a brand-new cover

Chapter 10 is here with Tower middleware and a DynamoDB-backed rate limiter, plus new appendices on running Axum on Lambda and deploying with GitHub Actions. And the book got a new cover!

news.rust-lambda.com
1
78
Already own the book? The updated edition is ready in your Gumroad library. Curious about Rust on Lambda? Book info + a discount: rust-lambda.com Which addition are you most excited about? πŸ¦€

Crafting Lambda Functions in Rust - eBook by Luciano Mammino and James Eastham

A practical guide on how to build efficient, sustainable, cost-effective serverless AWS solutions with the Rust programming language.

rust-lambda.com
50
Oh wow, a long time in the making! 🫒
1
1
525
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
ArsΓ©nio@ArsenioMuandaOct 3
Replying to @ArsenioMuanda @loige
loige.co/hidden-design-compr…

The hidden design compromises of Docker layers

How Docker and OCI image layers represent filesystem changes, why deleting a file needs special whiteout entries, and what happens if you create a file called .wh.foo.

loige.co
1
1
116
Tonight i had the weirdest dream of seeing @antirez and @badlogicgames playing tennis table and they were too damn good! πŸ™ˆ What do I make of this? Either I like software (and some of the influential people around it) way too much, or I need to see a shrink... Or probably both!
2
550
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
SolidJS@solid_jsAug 13
🚨 Solid 2.0 has reached Release Candidate! πŸŽ‰πŸ₯³ Async is first-class β€” computations return promises, the graph suspends and resumes itself. Plus optimistic mutations and a reactive core rebuilt from scratch. The Big <Reveal> πŸ‘‡ solidjs.com/blog/solid-2-0-r… 1/3
46
152
38
1,171
233,011
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Ryan Carniato
@RyanCarniatoAug 13
It's finally here! So many thoughts/feelings I couldn't fit them in the blog post but its crazy to think after so much work this is only the beginning.
SolidJS@solid_jsAug 13
🚨 Solid 2.0 has reached Release Candidate! πŸŽ‰πŸ₯³ Async is first-class β€” computations return promises, the graph suspends and resumes itself. Plus optimistic mutations and a reactive core rebuilt from scratch. The Big <Reveal> πŸ‘‡ solidjs.com/blog/solid-2-0-r… 1/3
21
34
5
602
46,642
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Luciano Mammino 𝕏 Node.js Design Patterns@loigeJul 6
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 🧡
πŸ€– Made with AI
Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

ALT Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

1
1
4
675
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 🧡
πŸ€– Made with AI
Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

ALT Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

1
1
4
675
more replies
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.
1
1
94
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/blo…

Environment Variables in Node.js

Learn how to use environment variables in Node.js with process.env, the native --env-file flag, validation, and security best practices.

nodejsdesignpatterns.com
2
95
Load more