Matthew Eernisse

22K posts

Matthew Eernisse banner
Matthew Eernisse

Matthew Eernisse

@mde

Literal rock star developer. JavaScript, music, Japanese, and serial commas. 日本語でもOKです。

San Francisco, California USA Katılım Şubat 2007
210 Takip Edilen2.4K Takipçiler
Samantha Simonhoff
Samantha Simonhoff@RealProductGirl·
I NEED my feed full of builders. What are you working on right now? I don't care if it's a startup or a weekend side project. If you're building something, I want you on my timeline. Reply and let's connect. 👇
Samantha Simonhoff tweet media
English
1.3K
30
1.4K
71.4K
Matthew Eernisse
Now can we just ban React?
Alvin Sng@alvinsng

24 hours ago, I posted this article about @FactoryAI's take on React's useEffect which has surpassed 1.7M views and is still growing. This caught the attention of numerous execs, startup founders, and even the React core team. It has sparked a conversation about a paradigm shift in how we design software for the agentic era. Traditionally, software frameworks were designed for humans who spent time mastering fundamentals before writing their first line of code. Today, that is no longer the case. At Factory, all of our "backend engineers" ship frontend code. Any engineer should be able to prompt agents to tweak features "out of the box" with built-in guardrails. We learned the hard way that when agents write nearly all the code, useEffect often becomes the culprit behind systemic frontend bugs. We only encountered these issues because we are constantly pushing the boundaries of agentic software development. Fixing the process is more important than fixing the (direct) problem. On a note regarding marketing strategy: traditional, polished product announcements from PR teams don't work anymore. Sharing raw, authentic, "on the ground" stories about the interesting problems teams are solving is far more engaging.

English
0
0
1
126
Gergely Orosz
Gergely Orosz@GergelyOrosz·
It’s not X — it’s Y I cannot unsee how so much of the writing on this site (and online, in general) is increasingly AI-generated. It’s still pretty easy to recognize. Probably not for long tho Just alarming that ppl outsource even typing 3 sentences for a reply on this site…
English
154
33
1.2K
45.2K
Matthew Eernisse
Agentic identity, such a huge and interesting thing to ponder.
Aaron Levie@levie

Had meetings and a dinner with 20+ enterprise AI and IT leaders today. Lots of interesting conversations around the state of AI in large enterprises, especially regulated businesses. Here are some of general trends: * Agents are clearly the big thing. Enterprises moving from talking about chatbots to agents, though we’re still very early. Coding is still the dominant agentic use-case being adopted thus far, with other categories of across knowledge work starting to emerge. Lots of agentic work moving from pilots and PoCs into production, and some enterprises had lots of active live use-cases. * Agentic use-cases span every part of a business, from back office operations to client facing experiences from sales to customer onboarding workflows. General feeling is that agentic workflows will hit every part of an organization, often with biggest focus on delivering better for customers, getting better insights and intelligence from data and documents, speeding up high ROI workflows with agents, and so on. Very limited discussion on pure cost cutting. * Data and AI governance still remain core challenges. Getting data and content into a spot that agents can securely and easily operate on remains a huge task for more organizations. Years of data management fragmentation that wasn’t a problem now is an issue for enterprises looking to adopt agents. And governing what agents can do with data in a workflow still a major topic. * Identity emerging as a big topic. Can the agent have access to everything you have? In a world of dozens of agents working on behalf, potentially too much data exposure and scope for the agents. How do we manage agents with partitioned level of access to your information? * Lots of emerging questions on how we will budget for tokens across use-cases and teams. Companies don’t want to constrain use-cases, but equally need to be mindful of ultimate token budgets. This is going to become a bigger part of OpEx over time, and probably won’t make sense to be considered an IT budget anymore. Likely needs to be factored into the rest of operating expenses. * Interoperability is key. Every enterprise is deploying multiple AI systems right now, and it’s unlikely that there’s going to be a single platform to rule them all. Customers are getting savvier on how to handle agent interoperability, and this will be one of the biggest drivers of an AI stack going forward. Lots more takeaways than just this, but needless to say the momentum is building but equally enterprises are acutely aware of the change management and work ahead. Lots of opportunity right now.

English
0
0
1
85
Matthew Eernisse
@RandallKanna This is so crazy. There's this false dichotomy of "agents do everything perfectly" to "agents write shit code." The truth is in the middle. If you're a good developer, the agents you steer will write awesome code. You're a developer, not a "code typer."
English
0
0
0
94
Randall Kanna Franson
Randall Kanna Franson@RandallKanna·
Honestly what is there to compete on at this point for a dev job? Like code reviews?
English
37
0
39
14.4K
Matthew Eernisse
This.
Matteo Collina@matteocollina

@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.

English
1
0
0
102
Dave Kennedy
Dave Kennedy@HackingDave·
Here's why I think software engineering is safe, but different. I'm seeing so much stuff being created from folks that haven't been developers - don't understand programming nor architecture/infrastructure deployment. It's usually really rough, riddled with bugs, barely works - usually very basic. Software engineering - AI will become a massive force amplifier - having 15 developers or more working for you real time and being able to get stuff out much faster. For me, it's sped up my development to 200% or more. Example, the social engineer toolkit, I spent 10 years of my life coding that thing virtually everyday for hours and hours at a time. Sometimes not sleeping for 2-3 days because I was coding. End of 10 years, 59K lines of code written. Project I'm working on right now, 9 months worth of work, 159K lines of code. It's amazing, but software engineering, understanding underlying technologies and infrastructure, being able to articulate exact specs on what it should do, how it should work, the coding structure around it is something I don't see changing with AI. It'll get better, you will always need software engineers. I think the statement that SE are dead is highly inaccurate.
English
32
8
149
12.3K
Matthew Eernisse
@Dan_Jeffries1 Yes, it absolutely is different. How do you not get that? Unlike all the previous revolutions, the AI tech revolution explicitly does not require a human operator. That's the entire point of it.
English
0
0
1
14
Daniel Jeffries
Daniel Jeffries@Dan_Jeffries1·
The labs should hire some folks who have basic economic and history understanding, considering every single tech revolution has created more jobs despite wild fears it would take them. And maybe if their AI is so superintelligent, they should ask it to do their PR because they suck at it. And before you even say it: no this time is not different.
Daniel Jeffries tweet media
Noah Smith 🐇🇺🇸🇺🇦🇹🇼@Noahpinion

The labs should spend a lot more on economics, because "you will be obsolete and maybe killed or enslaved by our product" is the shittiest value proposition I can possibly imagine

English
7
2
25
2.2K
Grady Booch
Grady Booch@Grady_Booch·
One of the things that surprises me about the distant future as envisioned by science fiction series such as @StarTrek is the distinct absence of new swear words.
English
68
7
182
10.6K
Don Park
Don Park@donpark·
We had two American littoral combat ships with mine-clearing capabilities in Bahrain but they were moved. This would've been their first combat. Who the hell planned this? theweek.in/news/middle-ea…
Don Park tweet media
English
1
0
1
119
ELIJAH SULE
ELIJAH SULE@juiceboy_of_abj·
There’s a huge mistake in this folder structure, if you’re a real developer tell us.
ELIJAH SULE tweet media
English
28
44
565
43.7K
Matteo Collina
Matteo Collina@matteocollina·
.@nodejs has always been about I/O. Streams, buffers, sockets, files. But there's a gap that has bugged me for years: you can't virtualize the filesystem. You can't import a module that only exists in memory. You can't bundle assets into a Single Executable without patching half the standard library. That changes now 👇
Matteo Collina tweet media
English
51
267
2.6K
352.7K
Csaba Kissi
Csaba Kissi@csaba_kissi·
Everybody is talking about how AI will generate 100% of the code in a year or two. But nobody is talking about how this code will scale.
English
99
7
133
8.2K
Matthew Eernisse
@svpino I am still at the point where I read every line it generates. The risk of garbage making it in is not worth the speed improvement. Just yesterday I had to remove some complete garbage tests it generated. Like, complete garbage.
English
0
0
0
13
Santiago
Santiago@svpino·
Let's be honest, most people ain't checking the code they're writing with AI. Yeah, it may be important, and we are always yapping about how you gotta do it, but there's absolutely zero chance most people are taking the time to slow down and go line by line, trying to understand everything the model wrote. It's just too easy to produce a billion lines of code now. It's even easier to test the product (rather than the code) and ask the model to fix whatever you don't like. And you know what? I think not looking at the code is fine for many. I've seen a lot of code 100% written by humans. Some of it is an immense pile of garbage, and nobody has died. 100% AI-generated is actually an improvement for those products. But there are many places that can't afford slop, and we always take things too far. Non-supervised AI-generated code is dangerous. There will be some blowback, and companies will start getting very wary of AI cowboys. Some might outright ban AI-generated code, and some will figure out how to make developers liable for their code.
English
109
13
193
24.6K
Matthew Eernisse retweetledi
Cats with Aura 😺
Cats with Aura 😺@catwithaura·
The cat knew exactly what he was getting into 🤣
English
342
2.3K
24.9K
1.1M
Matthew Eernisse
@evadne Sometimes you don't know, and you wake up in the morning realizing what bothers you about it.
English
0
0
0
14
Evadne W.
Evadne W.@evadne·
@mde Yes, I remain quite bothered by the design, but am not able to formulate a coherent reason as to why I am bothered by it at this time.
English
1
0
0
19
Evadne W.
Evadne W.@evadne·
Everybody gung-ho until they see the part of the MCP Spec that describes elicitation. Then Elixir bros resume their gung-ho.
English
1
0
1
108