Matteo Collina ✓

@matteocollina · Forlì, Emilia Romagna · joined 25 Aug 2008

@platformatic Co-Founder & CTO, @nodejs TSC Chair, Lead maintainer @fastifyjs, Board @OpenJSF, Conference Speaker, Ph.D. Past: @nearform. Views are my own.

58 046Followers

3 862Following

47 186Posts total

290.4KViews on collected posts

Latest posts

Matteo Collina ✓@matteocollina10 Sep

@matteocollina @matthewcp Hope you’re joking 21.4K views · 213 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina10 Sep

@matteocollina Because TypeScript is better for finding mistakes 8.9K views · 147 likes · 0 reposts · 5 replies Open on X →

Matteo Collina ✓@matteocollina10 Sep

Given we don’t write code anymore… why are we still dealing with TypeScript and transpilation? Models can write perfect JS in less tokens. 193K views · 1.5K likes · 36 reposts · 266 replies Open on X →

Matteo Collina ✓@matteocollina9 Sep

Publishing a large monorepo of interdepent modules has become impossible with the new change on npm: the new scan thing delays every publishing substantially, and it does not recognize a batch. Maybe one should try doing a staged publishing and then do 15-20 clicks to approve 4.2K views · 17 likes · 0 reposts · 9 replies Open on X →

Matteo Collina ✓@matteocollina9 Sep

The HTTP/2 Bugs Hiding in Plain Sight https://t.co/EcZGd8ICML 2K views · 12 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina8 Sep

The thing I like the most about the Omarchy movement is the whole “giving new life” to devices that suffered from planned obsolescence. 2.1K views · 36 likes · 1 reposts · 0 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@matteocollina @nodejs Hmm, so basically it always boils down to if a human is in the loop & has checked everything on their own, it's fine to use AI code. I mean that's the essence of AI imho, we use AI to do stuff faster, coz AI cuts corners & critical stuff can break too, if n 676 views · 4 likes · 0 reposts · 0 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs The most important role in software development hasn't changed. It's not the person or tool that writes the code. It's the person who understands, reviews, and takes responsibility for it. That's what the DCO was designed to enforce. And it still does. Full article 👇 2K views · 12 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs What's next? The @nodejs TSC will vote on disclosure and attribution practices for AI-assisted contributions. This is how the Node.js community works: when there's disagreement, we deliberate and we vote. That process matters as much as the outcome. 1.3K views · 3 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs OSS projects that learn to accept AI-assisted contributions responsibly ill move faster and attract more contributors. We need more transparency, human review,s and clear accountability. Projects that ban AI tools are limiting their contributor pool just as demand is gr 2K views · 3 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs The DCO has never been about how code is written. It's about whether the contributor has the right to submit it - and takes responsibility. This is the same of accepting any Open Source contribution. We've always depended on the person who signs off. 1.6K views · 8 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs My grandmother made pasta with a "Nonna Papera" - the pasta maker every Italian family had. No one said it wasn't her pasta. She chose the flour, eggs, thickness, shape. The tool helped her hands. I chose the architecture, shaped the API, reviewed every line. The code 1.5K views · 15 likes · 1 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs The real shift AI brings isn't legal - it's operational. AI moves the bottleneck from writing code to reviewing it. The human in the loop isn't a limitation. It's the feature. 1.6K views · 11 likes · 1 reposts · 2 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs The concern was legitimate: if AI models are trained on code with mixed licenses, can you really certify you have the right to submit the output? It's a fair question. The DCO exists for a reason. 2.7K views · 8 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

@nodejs But three independent organizations already answered it: - The Linux kernel community (who created the DCO) - Red Hat's legal team - The OpenJS Foundation (Node.js's own legal body) All reached the same conclusion: AI doesn't break the DCO. Accountability does. 2.3K views · 13 likes · 0 reposts · 1 replies Open on X →

Matteo Collina ✓@matteocollina18 Mar

🧵 I wrote almost 19,000 lines of code for a Virtual File System in @nodejs core using Claude Code. It started over Christmas and has been refined over almost three months of review. A collaborator challenged whether AI-assisted contributions can meet the DCO requirements. https:

43K views · 150 likes · 12 reposts · 13 replies Open on X →

Against accounts of the same size

6 posts from the last 90 days, next to the 10K–100K follower range. shown widely, but few of those viewers react.

Median views6 552this account982median for 10K–100K

Reach, %11.29%this account3.75%median for 10K–100K

Engagement, %0.97%this account1.52%median for 10K–100K

Metric	This account	Median for 10K–100K	Ratio
Median views per post	6 552	982	6.67×
Reach (views ÷ followers)	11.29%	3.75%	3.01×
Engagement rate	0.97%	1.52%	0.64×

Others in this range → Compare with another account → How these benchmarks are built →

Growth & engagement

How the posts we collected actually performed: views and reaction rate post by post, what the audience did with them, and where the follower count goes.

Views per post

2.7K18 Mar

1.6K

1.5K

1.6K

1.3K

676

2.1K8 Sep

2K9 Sep

4.2K

193K10 Sep

8.9K

21.4K

Last 14 collected posts, oldest on the left. The scale is logarithmic: one post can outrun the rest a hundred times over.

Engagement rate per post

0.33%18 Mar

0.88%

1.11%

0.56%

0.20%

0.31%

0.66%

0.59%

1.73%8 Sep

0.65%9 Sep

0.61%

0.94%10 Sep

1.71%

1.00%

Reactions — likes, reposts, replies and quotes — divided by views. Median for 10K–100K accounts is 1.52%.

What the audience does

Likes77.9%2 157 in total

Reposts1.8%51 in total

Replies11.0%304 in total

Bookmarks9.3%257 in total

Share of every reaction we collected for this account. Replies mean argument, reposts mean endorsement, bookmarks mean the post was worth keeping.

The follower curve appears once this account has two daily snapshots — we take one a day, and this one is on its first.

Latest posts

Against accounts of the same size

Growth & engagement

Views per post

Engagement rate per post

What the audience does

Similar accounts