Natalia Venditto🦋

18.3K posts

Natalia Venditto🦋 banner
Natalia Venditto🦋

Natalia Venditto🦋

@AnfibiaCreativa

Principal Engineer @Adobe AEM. OSS. CPC @openjsf. @oreillymedia author https://t.co/c8Hsc5MXb6

Katılım Nisan 2012
1K Takip Edilen7.4K Takipçiler
Sabitlenmiş Tweet
Natalia Venditto🦋
Natalia Venditto🦋@AnfibiaCreativa·
This is JavaScript for non-developer or beginner developers that want to learn technical fundamentals, and how to make strategic decisions, to confidently participate of a cross-functional team conversation. >>
Wassim Chegham@manekinekko

Super proud of @AnfibiaCreativa who just released 23 bite-sized videos to help you explore the fundamentals of JavaScript. Check it out on @OReillyMedia! 👉🏽 learning.oreilly.com/search/?q=auth…

English
2
4
26
8K
Natalia Venditto🦋
Natalia Venditto🦋@AnfibiaCreativa·
Quick professional update: I have joined @Adobe AEM Engineering, as a Principal Engineer working on AEM Agents, Agent orchestration and other tools. I am super excited for the future and for going back to full-time engineering and my roots in the Adobe Experience Manager stack.
English
3
1
6
272
Natalia Venditto🦋
Natalia Venditto🦋@AnfibiaCreativa·
This is the most accurate and polished explanation on github.com/web-fragments/… a different architecture for micro-frontends. Huge appreciation for @jeffwhelpley who chatted back and forth with us, to make sure the technology was well represented. Please give a play and like.
Jeff Whelpley@jeffwhelpley

Web Fragments: The Future of Micro-frontends See the full video here: youtu.be/jtz7bBVKcOg @IgorMinar @AnfibiaCreativa @CloudflareDev

English
0
1
3
245
Alison Chen
Alison Chen@alisonxchen·
My very first hackathon why am I the only woman here is that normal
Alison Chen tweet media
English
785
249
19.8K
1.5M
Natalia Venditto🦋
Natalia Venditto🦋@AnfibiaCreativa·
When you come back to X-Twitter after weeks (months?)
GIF
English
0
0
0
215
Julia Turc
Julia Turc@juliarturc·
We need an official name for not-vibe-coding. My top candidates so far: · boomer coding · chewgy coding · trad coding · Coding with capital C Suggestions are welcome.
English
2.5K
212
5.6K
1M
Natalia Venditto🦋 retweetledi
Matt Biilmann
Matt Biilmann@biilmann·
I've heard so many say that Gen AI will be the end of the web and that everything will be disintermediated in chat apps or through MCP servers. In reality we have first row seats to massive growth in both the amount of sites getting built and in the amount of builders on the web. And now we're seeing a full revival of the browser wars of the 90ies or 2000s with the new wave of AI browsers. This is great news for the open web. Nothing drives progress like browser innovation and competition. More bullish than ever.
English
5
3
23
2.7K
Natalia Venditto🦋 retweetledi
Matteo Collina
Matteo Collina@matteocollina·
🚀 BIG NEWS: We just open-sourced the Intelligent Command Center (ICC) for Node.js! After years of watching teams struggle with Node.js on Kubernetes, we're changing the game. The problem? K8s was built for Java/.NET, not Node.js's async model. The cost? 40% overprovisioning. 🧵
Matteo Collina tweet media
English
6
35
330
34.5K
Natalia Venditto🦋 retweetledi
Matteo Collina
Matteo Collina@matteocollina·
The npm team has shipped OIDC publishing from GitHub and GitLab! Has anybody tried it yet? Finally no more npm token leaks! docs.npmjs.com/trusted-publis…
English
14
12
90
10.3K
Natalia Venditto🦋 retweetledi
Matteo Collina
Matteo Collina@matteocollina·
I see the following tweet getting attention. It’s fundamentally incorrect. WebSockets are scalable. There is nothing special about MQTT or any other binary protocol you can invent that make your application scale better. (Differences exists ofc, but not at high level). There are two key drivers: 1. the cost of maintaining a persistent connection in your OSS and infra 2. the capability of your application to offer stateful guarantees while allowing clients to reconnect to multiple servers MQTT semantics provide a fantastic base for this for the 2nd part. Most WebSocket-based applications fail spectacularly at this. WebSocket is a *very costly* protocol, as it cost a relatively high amount of CPU time to decode the messages and encode them again, but you can make it scale very well if needed.
Shivam Bhadani@shivambhadani_

Websockets which a lot of people use while building realtime communication (such as chatapps) are not scalable for large userbase. It can be good for small scale startups but large scale companies don't use it. Most of the times, either companies write their own custom protocols or use pubsub models like MQTT. In websockets, open connections are all handled by application servers. This requires alot of resources. Horizontal scaling can't be done beyond a point since u can't add infinite/a lot of servers becz its expensive. Since browsers only have websocket for two way communication, most companies build their protocol by taking websocket as transport layer. And don't use it as application layer with socketIo.

English
5
8
187
19.6K
Natalia Venditto🦋
Natalia Venditto🦋@AnfibiaCreativa·
Our team at Microsoft @Azure developer experiences and tools is looking forward to chatting with JavaScript/TypeScript devs who work with startups/enterprise and are actively using AI powered code generation platforms for production apps or features. Please reach out via DM!
English
2
0
4
875
Natalia Venditto🦋 retweetledi
Matteo Collina
Matteo Collina@matteocollina·
📗 We’ve written the ultimate guide to help you master Node.js. Here's what's inside: 🔄 Do not block the event loop 📶 Monitor Node-specific metrics 🎬 Use Node LTS versions in prod 🤖 Automate testing, code review ⛓️‍💥 Avoid dependency creep
English
2
34
260
12.3K
Natalia Venditto🦋 retweetledi
Gabriela de Queiroz
Gabriela de Queiroz@gdequeiroz·
💔 Bittersweet news to share: I was impacted by Microsoft’s latest round of layoffs.
Gabriela de Queiroz tweet media
English
314
514
8.7K
1.8M
Natalia Venditto🦋 retweetledi
Wassim Chegham
Wassim Chegham@manekinekko·
Do not push code you don't understand, to production.
English
1
2
10
1.2K