This would be deeply surprising to me, and I am the target audience for this repo. I'd expect the default here to be Widely Available only with some opt-in for the courageous. I don't know that I'd even enable it.
[0] https://github.com/GoogleChrome/modern-web-guidance/blob/4dd...
CSS @function
CSS calc-size()
CSS interpolate-size
CSS corner-shape
CSS border-shape
CSS flex-wrap: balance
CSS text-fit
CSS text-decoration-skip-spaces
CSS scroll-axis-lock
CSS scroll-target-group
CSS :target-current
CSS scroll-initial-target
CSS container scroll-state queries
scrollsnapchange event
scrollsnapchanging event
HTML focusgroup
Element.startViewTransition()
CSS view-transition-scope
Interest Invokers (interestfor)
LanguageModel (Prompt API)
LanguageDetector
Translator
Summarizer API
Window.fetchLater()
Speculation Rules API
Long Animation Frames API
VisibilityStateEntry
PerformanceSoftNavigation
InteractionContentfulPaint
Connection-Allowlist
CSS url() integrity() modifier
HTML meta name="text-scale"
HTML template for
HTML processing instructions
PasswordCredential
Promise-returning scroll methods
Web App Origin Migration
Local Network Access permissions
Request.targetAddressSpace
beforeinstallprompt event
To be fair, the skills also recommend ~11 features not supported by Chrome itself. And the project does seem concerned with compatibility: "Guiding models to use sensible, lightweight fallbacks."That index page should link to plain markdown versions of all of the documents, and should be designed for search with grep to find the right answers.
That way I don't have to install anything at all - provided my agent has the ability to make HTTP requests I can tell it "Look for tips on https://googlechrome.github.io/modern-web-guidance-src/skill..." and it will fetch the index, then navigate to the most relevant documents - no MCP or npm or installation required at all.
- Quoted phrase in the opening sentence
- Opening quote: “Find some prior art that will invalidate these claims”
See Dan Gelbart's recent video on that very subject: https://youtu.be/v5d8nwgiSYI?si=iM9AFZiRTjxu4OuZ
- Quoted phrase in the opening sentence
- Opening quote: “Look what you made us do”
DisplayLink on the driver side just compresses frames to send them over USB.
It would be interesting to analyse if Synaptics haven't stolen code from open source ffmpeg or VLC to do the compression.
Obviously this is intended as a scare tactic, but, surely that could never hold up in court? Surely the burden of proof is on the owner of the patents to prove that someone's work is infringing, and you can't then say "We are charging the defendant to prove that we have a valid case against them." ?
https://lkml.rescloud.iu.edu/hypermail/linux/kernel/2610.1/1...
According to patent prosecution records, the independent claims for GB2484736 originally lacked any network transport limitations and were deemed entirely unpatentable against the prior art listed above.
To get the patent granted, DisplayLink’s attorneys amended the claims to specifically add delivery of the display data over a "general-purpose data network." The validity challenge relies on proving that adding a general-purpose transport layer (like USB or Ethernet) to existing image-compression methodologies was an obvious step and completely unoriginal in 2010, given the widespread existence of USB monitors and network-attached graphics at the time.
WireGuard by itself is not a stealth VPN, but the things that make a VPN "stealthy" are all things you'd layer on top of a WireGuard design, not thread through the middle of it. A datagram-based protocol can run under any obscured transport.
We did this at Fly.io when we discovered that, for one reason or another, 5% of our users simply couldn't reliably use UDP. It was a one-day project to run it under WebSockets instead, and that was before coding agents.
I expect that Anthropic will have success in some of their side hustles if they're reinforced by the model ecosystem and double down on them, but you should also expect that at some point in the future we will talk about the "Anthropic Graveyard".
Dots in particular display some insidious methodology, they've hidden the "programmable" portions of an agent. They want to make it 'magic' (all your work goes through a single tool) but... that's pretty much exactly what businesses DON'T want. We need to see what it's doing, accessing, working with, underlying data, etc... It's an explicit business requirement for us.
The more they can 'hide' what the backend does, the harder it is to get away from the product.
Buuuuut, I don't think it's going to work. I can still export it somehow if I want to, and it would probably take 10-15 minutes... The whole point of these agents is that they're 'plug and play' with whatever technology you want.
And if they don't build them this way, someone will whip up an open source version that does it cheaper and more transparently in a couple of weeks.
Software being free now hits both of these companies exactly where they want protection.
- Quoted phrase in the opening sentence
- Opening quote: “city”
There's sizeable demand for people who want to be able to do runs to the bigbox stores for garden and DIY renovation supplies and store it the rest of the time.
Yes, I view most 'new' TLDs as scams. They lure you in with a low price, a rather pricey renewal and then price hike after price hike down the line. They also charge a premium for most dictionary words right from the start.
Unfortunately I am stuck in commitments on a few of these domains and just had to eat the cost increases, the rest I moved to .com/.net.
.consulting was the worst offender.
- Quoted phrase in the opening sentence
- Opening quote: “first.last.name”
I did notice that my domain kept working past the supposed shutdown date, but I let the domain registration expire.
I'm so mad now! I assume there is no way to get my domain/email forwarding back :(
I suppose I could try to ask the registrar, but I highly doubt they can do anything...
(Edit: I'm not actually mad, but it was annoying to have to move accounts from my first@last.name email to another one)
No doubt code quality increased substantially, but I've been wrestling overengineering for a long time, with both GPT/Claude - they will take any small chance to write excess code/documentation/specifications, anything - they seem to love reinventing the wheel. Heck, even prompts sent to subagents are walls of text.
Explicitly requiring simple solutions works for simple problems, but for more complex ones, complexity quickly creeps in. I even ask the alternative model to challenge the complexity of solution, but doesn't work really well.
There is a perverse incentive for AI companies to train models to be verbose, as it increases the tokens consumption.
"AI writes shallow tests" - used to be true, not true anymore since Astra and Fable 5.1 / Opus 5.5.
"AI writes overly complex ccode" - only if you let it. A "do not overengineer it" or "Pareto, 80% result with 20% of effort" go a long long way.
"Reliance on AI decreases human understanding" - human understanding does not decrease, it just moves up a level or two. The same way you do not really understand how the Linux kernel works, nor do you know how assembly really works (with probably a bunch of exceptions here given this is the HN crowd!). And then there is hardware and physics too.
Understanding code, algorithms and data structures becomes a rarer need than it used to be.
"AI moves too quickly to maintain a high quality bar" - if you are stuck with the mantra that humans must review the code today, then obviously that statement becomes true. The problem is the assumption, not the observation. The good news about AI progressing fast is that coding AND reviewing get better and better with each release.
I know it is tough to let go. But as a software engineer, the sooner you do it, the quicker you will learn to yield a much, much more powerful weapon.
- Ordinary term used more than once in the same comment
- “confidence” appears 2 times
AI can generate "confidence" only in very limited amounts. It can help with testing, but that becomes very expensive and hard once we leave the realm of tests that can be simply written with code, like unit tests. At some point, the only way to increase the confidence in a codebase is actual testing with actual, real user interaction. And once that's maxed out, the only way to further generate more confidence is to get it into production and let real users (not test users, production users) find the remaining bugs no tester and no AI ever managed to hit.
This is the sole reason why AI doesn't make code "disposable" - yes, it can rewrite any codebase far more quickly than any human, but that new code will start at low confidence values - AI cannot transfer the confidence that the old codebase achieved simply due to being smashed against reality in production use to the new code it writes.
This is also the reason why it still makes sense to maintain libraries, even though AI could not just theoretically, but also practically write a lot of functionality from scratch that we usually import into projects via open-source libraries: the newly written stuff doesn't come with the same confidence as the already-battle-tested library does.
- Ordinary term used more than once in the same comment
- “Maintenance” appears 2 times
"Maintenance" does not mean "development after the first week".
- Quoted phrase in the opening sentence
- Opening quote: “AI generates...”
My immediate question would be what kind of adversarial reviews and deterministic gates did the author write to capture the dimensions of maintainability (lack of DRY, cyclomatic complexity, unclear naming, poorly architected flows, etc) that they cared about.
Don't get me wrong. When I was speeding along at 200 PRs a day (personal projects - I would not have inflicted them on others) I pretty quickly slopped together a big ball of mud, but as I'm re-generating my estate (a) the models are a little better but (b) I'm adding a lot more rigor around verification (correctness, performance, security, operational costs and maintainability). It's not an easy problem to solve, but it feels to me like an engineering endeavor, not speculative rocket science.
I fully understand that many AI generated code bases do indeed suffer from more incidents and less maintainability, but I think it's important to distinguish between what is common and what is possible as the fix for one is improving the rigor of your verification whereas the fix for the other would be either accepting crappy code or giving up on LLMs.
Reminds me of a possible apocryphal anecdote I heard about Alan Turing. He loved going on long bike rides, but one day his bike developed a distressing habit of slipping the chain. After the third time it happened, he realized it was due to a broken tooth on both the front and the back gear. He went back home and calculated how many revolutions of the pedals it would take for both broken teeth to line up when they were at the critical part of the rotation, and he built a little mechanical counter that would click on each link in the bike chain, and at the calculated time, a little arm would reach down and clasp the chain, holding it in place long enough for the teeth to re-engage.
He showed the device to his friend, who said "Why didn't you just buy new gears? You could have gotten both for a dime." And Alan replied "Oh, that's clever, I didn't think of that."
- Ordinary term used more than once in the same comment
- “Local Push” appears 2 times
I only use "Local Polling" or better, and highly prefer "Local Push".
In a moment of weakness, I bought a D-Link wireless (wifi) water detector for the sump pit (it was on clearance for $30); it relied on a D-Link Home cloud service (free) that was closed down a few years ago.
Not wanting to toss it, I repurposed a spare Chromebook 14 that I was going to recycle and turned it into a Alpine monitor for the water detector, which I'm powering from the Chromebook's USB port (if power is lost in a rainstorm, I need to know about it before the sump pit fills up).
An immediate issue was that the D-Link firmware tried to "phone home" every 24 hours and would drop from the local network, since the server was kaput, and I had no clue what response it was expecting from the server to keep it alive. Solution; "reboot" the unit by interrupting USB power (with a Pico and MOSFET) every 23 hours. There's no question that home automation should work without the internet.
I was on holiday, and stopped at a second hand bookshop to grab something hopefully a bit trashy to read. I picked up Nova Switch because the cover made it look like some weird sci-fi detective romp. But after about three pages it became apparent that I had happened upon something very special indeed, and when I made it to the end I did something that I'd never done before. I turned back to page one and read the entire thing again.
It is magnificent. Everyone should read it. It turned out to be the second book in a trilogy, and maybe that was part of its appeal. It didn't explain anything, it just launched into a beautiful and strange sci fi world, filled it with extraordinary characters, and moved languidly through the story.
So much science fiction is just dreadful garbage. Harrison is most definitely not.
Then, they essentially bankrolled their enemy by giving websites a way to monetize spammy content. By the late 2010s, they started losing the battle for many types of organic queries - although many HNers forget that the most common and "important" search queries are things like "Nike shoes", not "an implementation of a Bloom filter in Rust". And then, in the 2020s, they pioneered LLMs and made the technology public, and drove a final nail in that coffin by making it possible to produce SEO spam on any topic, including Bloom filters, practically for free.
Now, they see AI answers as their salvation, steamrolling a variety of non-monetizable use cases that never really mattered to them. And this will probably work only until AI-poisoning SEO is in full swing, at which point Google will find themselves with dissatisfied users and diminished ad revenue.
- Put the public authorized keys in /etc/ssh/keys/%u immutable, monitored for checksum changes.
- Have CIDR restrictions in said public keys.
from="x.x.x.x/n,x.x.x.x/n" ssh-ed25519 AAAA[snip] Text-Identifier
- Have NFTables checks for MSS, TCP SYN TTL, Window sizes, CIDR blocks permitted on the public ssh instances (throw away nodes) and behind a VPN on more important roles. If I have a need to keep netfilter disabled then I put sshd behind L4 haproxy with ACL's.- Quoted phrase in the opening sentence
- Opening quote: “underappreciated”
Some folks out there still think .NET is Windows only. Some folks out there haven't looked at C# since the .NET Framework days. Some folks out there are still salty about some of Microsoft's decision around OSS (debugger, hot reload fiasco, etc.)
But day to day working with C# and .NET for backends? It's really fantastic. AI seems to like it a lot and a lot of tools for agents to go HAM. Roslyn analyzer, source generators, workable hot reload (for a compiled language), tons of really good docs from Microsoft, generally low variance and high consistency from codebase to codebase (e.g. encountering Drizzle vs Prisma vs TypeORM vs Kysely vs ... in Node land).
My previous team switched from TS to C# and F#[0][1] and it was a blessing; a lot of the platform ops have been simplified. It's just one very solid tool chain and packages are generally stable (a lot less effort on maintaining platform config/tooling and more focus on just building). First party packages get consistent security updates and C# doesn't have nearly the same level of exposure to transitive packages that one encounters with JS/TS ecosystem.
C# feels like a really solid choice in the age of AI coding because of it's general stability, strong static analyzer, insistence on types, and really good tooling. Not right for all use cases (e.g. CLI, serverless functions), but fantastic for backend APIs.
If you're looking to do AI with/on C#, I wrote about some of my experience with making codebases successful for AI[2].
[0] https://engineering.usemotion.com/moving-off-of-typescript-e...
[1] https://typescript-is-like-csharp.chrlschn.dev/
[2] https://chrlschn.dev/blog/2026/08/the-unexpected-ai-stack-cs...
I wound up going to college after working retail at Disney, then after college, my first job was supposed to be C# but they didn't have the project approved, so I got my first exposure to Python - which I loved, then JavaScript - which I hated but have a love-hate with to this day, and finally C#, but it wasn't .NET 3.5 no, they started using .NET Core, which was... something else, lots of teeth pulling during the original .NET Core days.
So many wonderful projects made with .NET my only complaint is I wish Microsoft would make a cross-platform GUI stack they'd actually stick to, and make it work on Linux too. ;)
I know there's alternatives but nothing beats telling your coworkers "lets just use the built-in" when choosing a GUI stack.
- Quoted phrase in the opening sentence
- Opening quote: “underappreciated”
Some folks out there still think .NET is Windows only. Some folks out there haven't looked at C# since the .NET Framework days. Some folks out there are still salty about some of Microsoft's decision around OSS (debugger, hot reload fiasco, etc.)
But day to day working with C# and .NET for backends? It's really fantastic. AI seems to like it a lot and a lot of tools for agents to go HAM. Roslyn analyzer, source generators, workable hot reload (for a compiled language), tons of really good docs from Microsoft, generally low variance and high consistency from codebase to codebase (e.g. encountering Drizzle vs Prisma vs TypeORM vs Kysely vs ... in Node land).
My previous team switched from TS to C# and F#[0][1] and it was a blessing; a lot of the platform ops have been simplified. It's just one very solid tool chain and packages are generally stable (a lot less effort on maintaining platform config/tooling and more focus on just building). First party packages get consistent security updates and C# doesn't have nearly the same level of exposure to transitive packages that one encounters with JS/TS ecosystem.
C# feels like a really solid choice in the age of AI coding because of it's general stability, strong static analyzer, insistence on types, and really good tooling. Not right for all use cases (e.g. CLI, serverless functions), but fantastic for backend APIs.
If you're looking to do AI with/on C#, I wrote about some of my experience with making codebases successful for AI[2].
[0] https://engineering.usemotion.com/moving-off-of-typescript-e...
[1] https://typescript-is-like-csharp.chrlschn.dev/
[2] https://chrlschn.dev/blog/2026/08/the-unexpected-ai-stack-cs...
I wound up going to college after working retail at Disney, then after college, my first job was supposed to be C# but they didn't have the project approved, so I got my first exposure to Python - which I loved, then JavaScript - which I hated but have a love-hate with to this day, and finally C#, but it wasn't .NET 3.5 no, they started using .NET Core, which was... something else, lots of teeth pulling during the original .NET Core days.
So many wonderful projects made with .NET my only complaint is I wish Microsoft would make a cross-platform GUI stack they'd actually stick to, and make it work on Linux too. ;)
I know there's alternatives but nothing beats telling your coworkers "lets just use the built-in" when choosing a GUI stack.
My personal "AI Pro" Gemini has 3.5 Flash-Lite, 3.8 Flash, 3.1 Pro, 4 Argon.
Pretty inconsistent.
- Ordinary term used more than once in the same comment
- “tail” appears 2 times
Many puns and easter-eggs in both! Recommend giving it a quick glance, some are pretty fun. Some examples include 'fable' as a 'tail' (IE 'tale'), and 'universe' as a 'scale'.
Words can be present in both lists when the entity is applicable to both a tail and a scale, so a tailnet named `koi-koi.ts.net` is theoretically possible too.
Found out about it after I randomly lucked into rolling 'miku' as my 'tail' when first creating my account :)
The only permanent remedy is to outright ban those - or better: mandatory transparency into what politicians spend how much time with whom, where money streams come from and go out of organizations, etc, etc. All transparent in a public ledger. (and no: it is not 'anti-competitive' if it's the same regulatory landscape for everybody, but a way to safe-guard the government permanently from corruption). Of course if you there are ideas that would complete this or are truly overall better, feel free to throw them in the comments hat.
IMO that's a better model for consumers since you do get something at the end of it. And if you are a professional, you were probably already getting the latest and greatest every time anyways.
It's that, yes.
They didn't prove that the code has no bugs; they proved that none of the current bugs (known or unknown) are security-breaking bugs, per their formalized security model.
> First, our researchers collaborated with a mix of models to translate Signal’s security goals into formal mathematical specifications, with human experts reviewing every one. From there, agents powered by Gemini Carbon did the proofs, generating over six million lines of Lean, a computer language that mathematically proves the accuracy of code.
The generated Lean code here is just being checked against the "formal mathematical specifications of Signal's security goals", not checked for the low-level properties you might care about as a programmer, e.g. "will it ever leak memory" or "will it ever crash", etc. And in fact, the code is not even being checked for the reachability of non-security-violating protocol failure states, e.g. "could the protocol ever deadlock such that neither side can send messages any more".
It's still perfectly possible for the code to have all of these problems. It's now just known that, as of the commit they did this analysis against, none of those low-level problems, as far as they exist in the codebase, can cause a security-model violation.
Or, to put that another way: the system has been proven to "fail safe" in all its current failure modes, per their specific definition of safety (which is basically "keeping to the security guarantees Signal markets itself to users as having".)
It's going to take way more than throwing a more advanced LLM at the problem to make any progress.
- Quoted phrase in the opening sentence
- Opening quote: “you look like a cat that's proudly showing me the mouse that it caught”
Our dog goes outside and hides in the lavender bush if a smoke alarm starts making a "I need a battery" noise.
So I went into this project with the attitude that I would like to solve this class of problem forever.
The thing is the parents normalizing this kind of intrusion of privacy think they are in the right while creating a very dangerous world. Even things like going through your kids rooms (yes even when they live at home) is a huge privacy violation.
No wonder the "but think of the kids" argument is so effective, we all grew up being propagandized by or own parents and environment.
They hated us for it. Other parents called us crazy. “They should learn how to handle social media!” And now their kids are unmanageable and ours thank us for shielding them.
So parents keep their children indoors for fear of being arrested from them crossing the street on their own. Politicians are unable to renege on "child safety" laws because the populace will believe they are harming children and vote them out.
But these things work the way they do because of the social consequences embedded in our culture, caused by the perceived harm to children from inaction. People want to avoid accusations of being complicit in harming children by supporting politician X or failing to do Y, as that has legitimate societal consequences when taken far enough, so there little incentive to diverge from this narrative.
I especially liked "The Perfectionists: How Precision Engineers Created the Modern World" and "Knowing What We Know: The Transmission of Knowledge From Ancient Wisdom to Modern Magic".
But all of his works are great.
- Quoted phrase in the opening sentence
- Opening quote: “transfer learning.”
If you want to make a ticket classification model, you don't need to train across many customers doing ticket classification, who might not want you to train on their data and whose data is impossible to obtain unless you already are a large company. Instead, you can train on a completely different task which forces the model to learn the syntactic and semantic structure of the English language — say predicting missing words in Wikipedia articles, which you can't do successfully without a good understanding of English — and then fine-tune that model on your specific task with much less data.
Because the initial task is so general, you can have one company do the expensive pretraining, share the base model, and then have everybody else just do the finetuning on their (small) proprietary dataset.
LLMs and models like Jev go one step further, letting you use them as classifiers with no training at all, with nothing but rules in the prompt. And with a few tricks, you can indeed use them to get pretty high-quality labels, which you can then distill into a fine-tuning dataset for a much smaller model.
I checked just for fun and there are actually a LOT LOT more than 92M tickets in the past year.
An issue in industry was that companies would not allow training on their data across customers. Understandably so, as SVM dimensions are readily interpretable given some thought. General purpose datasets were ill-suited too depending on the task.
So you'd start from scratch every time, annotate features like crazy, and often didn't have enough training data overall.
LLMs "solved" that by just ignoring the previous rules and training on everything, which lets the necessary world knowledge seep back in.
I'm sure we'll see many combinations of LLMs and regular machine intelligence in the near future.
— "Let's build efficient classifiers"
— "Forget about the silly classifiers, LET'S BUILD A MACHINE GOD"
— "Ah, that machine god is often too expensive and underwhelming. Let's build efficient classifiers"
[1] "Linnaeus: A highly reusable and adaptable ML based log classification pipeline", https://arxiv.org/abs/2103.06927
NOTE: the work was actually accepted at the International Conference on Software Engineering (ICSE) in 2021.
[1] "Traffic Flow Estimation using LTE Radio Frequency Counters and Machine Learning", https://arxiv.org/abs/2101.09143
- Quoted phrase in the opening sentence
- Opening quote: “bending”
Oh well, there have always been ways to snoop on someone like that. Back in the day it was CRTs emitting measurable waves through the neighborhood, with some papers even going as far as restoring the displayed image through a wall. Nowadays it's fiber and WiFi, and those seem to be much easier to work with even. Plus everyone carries a device that is tracked by their mobile provider's cell network. shrug
- Quoted phrase in the opening sentence
- Opening quote: “Art is born of constraint, thrives on struggle, dies of freedom.”
The world has changed and we can never go back.
While it's nice that LLMs are getting better at arriving at the desired deliverable with fewer surprises (or broken things) doing it is not necessarily a sign that the model is actually smarter, just an indication that what you are doing is likely a well-trodden path for the model, the RL and the harness.
- Quoted phrase in the opening sentence
- Opening quote: “one-shot”
This really was more like a normal person had access to a game developer team (with artists and musicians) and had a custom game built based on interviews and playtesting.
Opus 5.5: https://claude.ai/artifact/UuT7P936dU1XoPByYZ7xyD Fable 5.2: https://claude.ai/artifact/UszKFvuonWAT5psjMttAEg
There are some areas in which Fable is clearly better but subjectively the Opus 5.5 version feels more fun.
Both are one shots, Opus 5.5 was done a few weeks ago before they added "guardrails" around recreating games. Fable 5.2 changed some game mechanics despite my prompt asking for them to be the same as original game.
If VC money gets tight, they would have to issue debt, that pay interests. With a current negative EBITDA, their bond will be junk at IPO, paying higher interests and having a lot less market than AAA debt (e.g. Google has access to that market). Both things combined translate to "running out of cash".
- Quoted phrase in the opening sentence
- Opening quote: “we'd get it from Coreweave or whoever is still alive”
However, I wouldn't be willing to try it under proprietary-software terms. Last week, I was thinking about eliciting open-source software with the Ultorg look and feel from an LLM, thus replicating Bakke's HCI research and enabling other HCI researchers to build on it, which won't be possible under a proprietary license.
My notes on Ultorg may be of interest; you can
git clone http://canonical.org/~kragen/sw/pavnotes2.git
and read sieuferd.md (5200 words).The introduction:
> Eirik Bakke’s [SIEUFERD][0] (or, as he sometimes spells it, SIUEFERD) is a really interesting and promising generic database frontend, a “schema-independent database UI”. The elevator pitch is “a new kind of graphical query interface [with] the power of SQL but the ease-of-use of a spreadsheet”. (Unfortunately, he forgot to implement the DDL part of SQL, just doing the DML part.)
I can highly recommend Bakke's 5-minute talk on it from 10 years ago at https://vimeo.com/173726371.
- Quoted phrase in the opening sentence
- Opening quote: “10x”
Yeah.
I'm not going to claim to be any particular multiple developer, but as someone who has been doing this a long time and as someone who has received praise from coworkers and bosses alike for being very good at the job, I enjoy my job a lot less than I did a year ago (or anytime since I started doing it in the 1990s).
Don't get me wrong, being a Senior Agent Babysitter probably still beats flipping burgers or being a roofer (so it could be a lot worse) but agentic AI has really sucked a lot of the fun parts out of the job.
- Ordinary term used more than once in the same comment
- “10x” appears 2 times
As a "10x" engineer I am not excited. I'm still working on projects with agents getting more done than ever, but I feel like software engineers has lost its soul for me. I don't really feel like I have a true understanding of anything anymore, I basically just spend all day making a set of small decisions or adjusting prompts to guide the agents down the good path. It used to be that I could close my eyes and visualize the code that I worked on--if there was a bug report I could often use that map to immediately know what the cause likely was. In meetings I could intelligently discuss various tradeoffs without having to refer back to anything. Now if someone asks me a technical question I basically have to forward it to the agent first, then interpret their response in light of my experience.
This is the real fear. We had a flood of engineers who entered the profession in the past 10-15 years who were decidedly average. No real interest in software development beyond "it's a cushy desk job, or better yet WFH job, that pays really well." No interest in whatever product was being developed by their company. Just show up, their PM assigns them a ticket to make a widget with a button, they use their TypeScript bootcamp skills to code up a widget with a button, ticket moved to In Review, job's done.
Now an agent can do that, and you need fewer of these types of people. Like, a lot fewer. Every engineer on your team who isn't a 10x-cum-100x engineer feels like a massive lost opportunity.
The "10x" engineers I know have never been more excited about their jobs. I'm really unsure what's going to happen to the average ones.
- Quoted phrase in the opening sentence
- Opening quote: “sandwich”
The problem is that software in corporations has typically been product managers at the front, software engineers in the middle, and QA at the end. Software developers who also have good product sense and do diligent QA are still needed. Programmers who treated their job as leetcode exercises are not needed anymore.
Of course, the “don’t update after this firmware version” bit would always be the case (since any widely-distributed such vuln will be patched eventually), but deliberately moving the timeline to the left is sad.