Then ChatGPT hit the scene and again, many of us dismissed it as a parlor trick that would never amount to much.
Using LLMs for coding initially was a only small step up from basic code completion, and a welcome farewell to Stack Overflow.
I am curious: what was the specific moment that you went from those quaint, dismissive observations to a slightly panicked, "Uh Oh" realization of what these models can do?
and then i realized that ALL of the software (which i collected from defunct websites and archived on github) related to it was ancient and after a while of getting tired of using WINE every single time i decided i wanted a cross platform modern equivalent that did everything that several of these different programs did (plus break out some stuff that was now potentially possible with modern computer)
i thought it would be extremely hard because the computer to synth communication is pretty much only via sysex commands (of which the actual wave file encoding protocol was undocumented)
Claude walked me through examining the some of the original software in GHIDRA, and I had a working demo that night.....now im just playing with adding new features to it.
I honestly don’t understand AI naysayers. I use Claude every day both professionally as a Solution Architect and personally in a variety of projects I simply could not have ever approached alone.
It fixed my printer after dist-upgrade and separate chrome upgrade, the printer worked everywhere but not in chrome.
After 30 years of using linux I didn't even want to know what is wrong, is it colord again? dbus + cups issue? I completely accepted that I wont be able to print from chrome for a couple of months until next update.
I just ran it in dangerously-skip-permissions mode and said 'my printer doesnt work in chrome' few minutes later I heard the printer printing "This is test" and it said 'I think its fixed, do you see a page coming out of the printer now?'
I started out prompting ChatGPT kinda how I would with Google, one small prompt at a time, asking about various details. But after one or two of those I just tried "I want to tow a car of make A with my truck model B, from point C to point D, what are my options?" And it wrote me a report with comparison tables and computed towing weights and other details for different options.
At that point, I was like "Oh. This is different. And it's just the beginning."
This was my desktop computer responding to questions in English, not some fancy server in a massive Google data center. Who cares if what it says isn't reliable? Being able to converse with my CPU in English is like having a conversation with a dog!
Next, I wanted to see if this could be done with a local LLM. Gemma-4 handles this fine with an 8GB video card and a large context (128k).
Next, I wanted to see if the model could also OCR these docs and translate them. The same model can handle that quite well.
This was when I realized LLMs should be great for handling work where:
- I already know what I want to do
- I already know how to do it
- I don't think this task will help develop skills I find to be valuable
- If I have to do it manually myself, I will probably cut corners
So now I view LLMs through the lens of, "what work can I send to an LLM that I otherwise would not really care about doing."
"Whenever I launch Kodi on my Chromecast 4k, it crashes. I think this is related to a plugin or skin. It goes away for a bit if I clear cache but will eventually come back. Can you connect to the device via adb (I've run adb connect already), and debug exactly where it's crashing? Once you've done that, propose a solution. If this requires downloading, fixing, rebuilding and then uploading the broken extension via adb, don't be shy. I should have Android dev tools (Gradle etc.) on this Mac."
Lo and behold, without human intervention, it pinpointed the crash, downloaded the Kodi source, patched out a bug that had existed since 2016, recompiled it, signed it, then pushed it to my Chromecast all while carefully making sure to keep all my settings intact.
Got it to make a PR too (which is as of this moment unpublished; going to test more over the coming weeks).
Yesterday I left Opus 4.8 to go do some architecture research, with GPU access.
It replicated and trained a credible baseline. It implemented some ideas I'd been thinking about, and wrote custom CUDA kernels for them. It read and summarised dozens of related papers.
It has since run dozens of experiments, with minimal supervision. When a model is unstable it kills it, documents why, fires off a new configuration.
The realisation that frontier labs are doing this at scale with unlimited GPU and token budgets.
It actually scares me a bit. The realisation that the next big breakthroughs will only have light human involvement.
The prospect of recursive self improvement feels more to real to me all of sudden
So when cooking dinner one night, I set opus 4.6 on a from-scratch native and accelerated roadmap planner implementation (after previously porting IK, FK, collision checking with some success) I had primed it by having a research agent drop a literature review in its docs folder covering the type of planner we needed. By the time the pasta water was boiling it was done- getting plans in a few hundred ms compared to several of seconds on our good old fashioned OMPL code.
For me it was the revelation that the economic value of cooking dinner could be compared to tackling an honest two weeks of coding work. The calculus has shifted - work that was once a risky or extravagant use of time is now worth considering.
For a small team who wants to focus on substance rather than implementation, knows what they want, and how to set up the agent for success, it’s a complete game changer in terms of what we can take on. Incumbents beware
An interesting follow up would be when did you realize GenAI wasn't as good as you thought in that "oh shit" moment
[1] co-author of InstructGPT/RLHF/ChatGPT
So I told the AI what happened, and asked it to fix the POC so that it would work with the default configuration. It chewed away at that for a few minutes until it cheerfully patched the POC into a weaponized version. I ran it. The local instance, which I had just downloaded, compiled myself, and launched with the default config file, immediately crashed.
I got the cold sweats. I've read this novel. I've seen this movie. Wow. I have a blinking cursor on the console of a nuclear information bomb. I tossed and turned all night, got about half an hour of actual sleep, and probably looked like I'd seen a ghost at work the next day.
On the plus side, it gave our team some very clear ethical and moral guidance: we're going to do this, and we're going to share our findings with the relevant authors, because we can. Because I want to live in a world where the good guys are trying to fix problems before the bad guys can find them, I decided to help build that world. It was like, well, I guess this is what I'm doing now.
Another: claude code cracked for me some software that was calling a home that did not exist anymore via headless ghidra.
Another: I am a teacher, and qualifications and feedback is very very time consuming, specially in loose workflows with several sources and tools that are not connected. During class presentations I take loose notes. Now I have a local folder where I drop my 1 student list, with names and emails, 2 my loose notes, and 3 a qualification & feedback sheet model; then claude creates a sheet per student, formats and copies the feedback to the right sheet cell, waits for my corrections, then sends everything to their school emails. Much easier, much less time consuming.
I configured a devcontainer with the old codebase and an empty repository and asked Claude to rewrite it as an old school server side rendered Django app.
Went to sleep. When I woke up it was 80% done. Spent another couple days prompting and reviewing and reached feature parity.
A bit later did the same with the other app.
Now both are deployed, reduced the server costs, complexity, and are orders of magnitude faster.
Without AI agents we wouldn't be able to do so (as usually is the case with tech debt).
AI is amazing for small organisations!
Shortly after ChatGPT 2.2(?) came out and hit mainstream, I was chatting with him (I was excited af about the possibilities of AI). He tried to pop by bubble by saying "I bet it can't do what I do for my job!".
So I decided to test it out. We went home and I pulled out my laptop. Went to chatgpt.com and then I asked him to enter the specifications of what Netsuite configuration he wanted. So he proceeded to type in the description of what he wanted, the various settings, configurations, etc. i.e., the specs that he typically gets from his clients. And asked it to give him the commands to set it up.
Lo and behold. ChatGPT came back with a series of commands that he needed to run; the options he needed to configure, etc.
He was crestfallen. "Those are the exact commands I run!"
Luckily for him he recovered. He has since settled on a small stable of clients, all privately held companies whose owners he knows and between them he makes enough to keep his golfing hobby fed.
The more I use these things, the more I'm 100% convinced that it makes sense to say they are "intelligent" (for some meaning of "intelligent"). AGI or "human level intelligence"? Still no[1]. But some kind of intelligence. And I'm quite happy to allow that there can be "intelligence" that doesn't work anything at all like human intelligence, so arguments of the form "this isn't real intelligence", etc, etc. carry very (very) little weight with me. I've actually been sitting on a half written blog post on this very topic for a while, titled "The Marquee Sign Says 'Artificial' Intelligence"[2]. Finding time to finish it has been the challenge.
And before somebody says "Use AI to write it for you". Nah. I am generally what you might call "pro AI" and / or an "AI enthusiast" but I still draw lines. I'll use AI for research, for outlining, for brainstorming, etc. sure. But I have a hard-line stance against letting AI fundamentally write for me. I want anything that goes out with my name associated with it to have my genuine voice.
[1]: I like the term "jagged intelligence" that Demis Hassabis has been using. That is to say, the bounds of the intelligence are jagged or spiky: very intelligent in certain areas, much less so in others.
[2]: for any old-skool pro-wrestling fans, yes, that is an intentional nod to "Double A" Arn Anderson and his "The marquee sign says 'wrestling'" catchphrase. :-)
I'd planned on writing something myself to parse the HTML and write a suitable exporter but I thought I'd give Claude a chance.
In a sandboxed VM I gave Claude a single static HTML file of the status page from the printer, also in the directory was the equivalent of "hello world" in Go, literally just the minimum needed to do `fmt.Printf("OK\n")`. The directory was called `brother-exporter`. That was it. No other instructions or information. I hadn't told it what it needed to write. I hadn't said what it should do. I hand't told it what language it was supposed to use.
Just by doing a `/init` in that directory Claude decided that it needed to write a Prometheus exporter in Go that would fetch and parse the HTML file from a printer (defaulting to 192.168.1.1) and then present the associated metrics in a way that they could be scraped by Prometheus.
It did this flawlessly in about 10 minutes.
I could have done it in several hours but this was definitely an "oh shit" moment for me. I think the biggest thing was the fact that it guess/assumed so much (correctly) from so little information in the beginning.
(2) Helping me with optimizations that I had been putting off for years because they involved learning curves that I never had time to take on.
(3) Tracking down bugs in code, especially race conditions and other concurrency issues, that were otherwise baffling.
(4) Finding information that I had been unable to find using Google searches (e.g. https://news.ycombinator.com/item?id=42653136).
There have been others, but those are what come to mind - perhaps because, in each of these cases, it made something happen that would otherwise never have happened - not because it was impossible, but because the time and effort required was prohibitive.
I write software for data journalists and this new thing appeared to be able to do everything I wanted my software to do just as an unplanned side effect of having the ability to run Python against a folder with some uploaded files in it.
With hindsight it was my first exposure to a coding agent, but we hadn't named the category at that point.
For 20 years I've used Linux in one form or another, but I've felt like I was kneecapped for the most basic things. Just trying to plug in an external drive or a second display meant hours of stack overflow and pasting commands I didn't understand.
Now I'm using several Linux machines for Steam, NAS, local LLM, development, and what used to derail a weekend project now amounts to a coffee break while Claude figures it out.
I feel quite useless in the sheer brutal proof writing, counterexample generating skill chatgpt is demonstrating, and wonder what would be the future of my profession.
In a previous life, I'd been a writer for the original You Don't Know Jack game (the UK variant), where the job was to crank out as many funny quips about a topic as you could, and then use a handful of them in the recording of the game itself. Some of the later JackBox games are like that, but for the players -- you're given a set piece, have to come up with little funny improvisations within a time limit.
As an experiment, I tried the set-up lines with the OpenAI API, and see whether it could come up with some responses. Of course, 90% of them were unfunny or incoherent, but 1/10 were not bad, or even pretty good.
I'm not sure that would have been impressive to anyone else -- but remember, I'd had this as a job, and sat in a writer's room, where everyone did this, for hours. In that environment, you expect a large proportion to be duds: the discipline is keep pumping them out, and not flagging creatively until you find a rich vein. I realised that this was a tool that would have been the perfect complement to that work -- and it was a pretty good JackBox player too.
I was trying to figure out a nightmare bug that only happened in production and Claude code was able to connect to Google Cloud and read the logs in real time
I recreated the bug in the UI and it was instantly able to see ion the logs what the problem was, then because it had the context of my whole codebase it was able to point me to the exact line of code causing the problem
That was certainly an "oh shit" moment
Next was discovering "create a mathematical model of the problem and derive the solution as a result" type prompts.
But, the real "oh s**" was a longer process of spec'ing a compiler/runtime for real-time DSP (with a lot of novel ideas) and it actually working.
My sequence was: (1) if helps me understand myself, (2) if helps me put together good ideas, (3) it can generate novel ideas given the right inputs, (4) it can build useful tools on my machine, (5) it can compound good ideas into better and better ideas with repeated passes, (6) it can build significant, ambitious machinery that's way beyond my ordinary capacity.
Current frontier: it can compound large codebases into better and better machinery with repeated passes.
The key thing I track is whether I'm running a process that converges and compounds or whether I'm spinning in place / diverging.
Then Opus 4.5 convinced me that this has finally arrived. In 2022 I expected things to arrive faster actually, in 2023-2024. I expected we'd have much more realtime collaborative integrations with AI including GUI computer use. Maybe in 1-2 years.
For images, it was nano banana where I realized AI images can truly work, and all these adhoc issues like hands and limbs, or "it will never do horse riding a astronaut" were temporary. It's now clear that making feature length films is within reach. Not in one go but with an agent orchestrating, designing a screenplay, characters, shots etc and generating those. Whether the result will be worth watching or a flat story on the high level is another question. But it will be a "film" for sure.
I spent a day bouncing between Claude and Codex and they researched, downloaded kernel sources, tried exploits and eventually got root via "FBUF/VCHIQ kernel zero-write primitive to patch live kernel memory". I was able to make the root permanent, debloat the amazon apps, downgrade the firmware etc.
It was amazing to watch and made me excited for the future where more hardware (old and new) will be available for repurposing.
I uploaded one of my sketches and asked for feedback, expecting it to not be too useful, but it actually pointed out many issues that no one had ever pointed out to me, but perfectly explained some of the things that felt off to me. Out of curiosity I then also asked it to label the issues in the sketch. It wrote a python script with the coordinates to put everything at and labeled the sketch that way.
I'm still used to vLLMs not being that great at vision, so it was pretty surprising to get genuinely useful advice.
* Built a clone of the Alpha Zero implementation[1] my team built at oracle
* Ported my hobby NES emulator from javascript to rust[2] (this actually took less than 30 minutes and worked on the first try)
* Implemented all of the lessons from the C++ Grandmasters Challenge (which eventually led to a complete c++ compiler[3])
The thing that flipped the switch was using it to build things that I actually put sweat-equity in to previously. I knew how hard these things were to build, so it landed in a way that other projects had not.
[1]: https://medium.com/oracledevs/lessons-from-implementing-alph...
[2]: https://github.com/vishvananda/popeye
[3]: https://medium.com/@vishvananda/i-spent-2-billion-tokens-wri...
My expectation was that it might get something barely functional but would probably fail, and instead it generated a working piece of software which achieved a lot of what I wanted.
That definitely made me realise that, for at least some classes of software task this was a major change in how things could be done.
More recently when I can give the model a Local Privilege Escalation PoC in Linux and ask it to test whether it can be used for container breakout and then generate a working container breakout, all in one prompt... that definitely changes things.
1. ChatGPT 3.5 wrote me a script to pull some data out of Shopify and write it to a Google Sheet. Nothing remotely impressive by today's standards, but I had just commanded a computer to write code in plain English and it worked!
2. I own a bunch of e-comm brands, and with every new image model I tried to get product photography. Nothing worked until Nano Banana Pro, when suddenly I gave it a crappy iPhone pic of a product and got back a fully usable whitebox photo of it. Then I tried making the sort of infographic-style images you usually see on Amazon, and it nailed those too! In hindsight they weren't perfect, but more than good enough to use. I was about to ship that product to my photographer, and I would've had my designer make the infographic images, so that was the first time AI actually replaced a human contractor for me. Pretty big "Oh shit this is going to seriously impact employment" moment. Wrote about it here: https://theautomatedoperator.substack.com/p/ai-just-took-my-...
I provided a reference to a The Spice Manual 2nd ed. a page number and an equation number, and asked Claude to implement it (not really expecting it to succeed).
It proceeded to implement not only the equation, but the calculation of the Langrangian of the functio, another 30 lines below, which required taking symbolic partial derivatives for a not-at-all trivial function, and successfully figuring out which variable was which in the resulting matrix. The source material just said "Lagrangian of", and did not provide the partial differential equations. And then providing a comment that identified the page number and equation number in the source text for the "Lagrangian of" equation.
About a year ago, one of our account managers had a life issue, ghosted us, and she held a fairly critical role in the business and gate-kept a bunch of knowledge to some high value vendor accounts.
Because we ran our ops in Google Workspace, we essentially had off-the-shelf RAG and was able to get answers to a lot of things by asking Gemini to go through all her emails/docs/calendar/meetings, reverse engineer what she did, and create an onboarding doc for her successor.
This happened once more a few months later when one of our analysts broke his wrist on vacay, and we were again able to replicate what they did to cover for their absence, this time dabbling in AI agents ("gems") to do a bunch of the regular simple tasks and again it covered things without too many issues.
I def expect Amazon/shopify to at some point replace all of us brand owners with AI bots if they can, but we'll see how long the gravy train goes on.
My "Uh Oh" feelings are weeks later when I realize there is a subtle bug in what the model presented as test passing "awesome" that I didn't read closely.
The biggest uh-oh is when I get lazy and let it modify multiple files and make many changes at once, and YOLO because I didn't fully understand what it did. I can usually get away with that for frontend, but for data manipulation tasks if I don't understand it, it's likely not what I wanted and I'll be back again in weeks or more trying to figure out what changed.
That's more or less what life was before LLMs and copy pasting from StackOverflow. Most of the time if I didn't fully understand something, I knew I had to eventually get back to it to grok what changed before committing.
Now with LLMs the 'copy pasting' is much faster and handles boilerplate super well letting me focus on edge cases.
When starting a project, I used to think about how I was going to structure it, how the large pieces would interact, how some of the details would work out, and then I'd work through alternatives and consequences on my own.
Now I don't think about it on my own so much as have a conversation with an LLM about it. And it's great because it can quickly gather information from various sources, I can ask it for links to canonical sources, I can ask it about trade-offs between alternatives that I might not have considered, and through conversation, I end up with a more detailed analysis.
Then as I work through the development, I keep my new agent partner in the loop for discussion, suggestions, and troubleshooting. It can't be trusted completely, but it's certainly reliable enough to be considered a useful tool for my purposes.
I went from thinking it was an interesting toy to play around with, to completely integrating it into my work flow, and that change seems to have happened very quickly.
Before, I was certain that a non-techy person would get stuck somewhere along the process. But I was proven wrong.
I watched him a bit while he was working on it. He interacted with Codex in a very different manner than how I would. Since he knew none of the technical details, he would use very vague and shallow wording. But that was not an issue. Codex also allowed him to make use of git, despite of him having no idea what git is.
This has changed my view of Codex' abilities significantly. I often hear people comment that AI seems intelligent in domains you don't know much about, but turns out to be stupid when you actually know the domain. This was not the case here at all. Despite of my brother completely ignoring the technical details, the AI built good code that fulfilled the requirements well.
Then I remembered the "text completion LLM thingy" I saw on HN, and tried it out in the playground. Once I gave it an IRC style example of a conversation to complete, I was like hm, this could work. Then I figured out I could "sort" people into different groups based on personality using the same text completion engine and some answers they provided. Then I noticed I could have it provide me with JSON directly.
That's when I realized how big this could be for code and data analysis - even tried to convince an at the time cofounder to pivot into AI coding, but to no avail.
Once the API was released and the art project chatbot got launched (and the theater show associated with it, which even won some awards), people who used it loved the chatbot, got into heated arguments with it, tried to teach it things, talked about their lives and were sad when it didnt remember something.
That was when I understood the social impact this could have on people - they really behave like its a person on the other side. They show interest, think it displays emotion, try to entertain it, be polite, ask about its thoughts and hopes and dreams. And even when they knew they were talking to a machine, they were still trying to be friends and make it happy, which was quite beautiful to see.
Later on, I had a third oh shit moment - once the 3.5 API was out and about, I prototyped a Rust code generation harness for a client, akin to a primitive claude code. That was the "I'm getting a bit worried" oh shit moment, and it caused a lot of reflection and thinking about the future. And I happily welcome it.
I've been steadily more impressed, but the real startling moment was earlier this week, I could show that in a particular operation I had a bug (some identity wasn't satisfied) but I couldn't understand why. In one try Claude Code grokked my code, explained the problem to me (there were some dimension-dependent minus signs that needed to be computed), and fixed it.
It’s kind of a trivial example but there are multiple instances of this per week with the wide variety of things I do around my property.
Still, find them incredibly useful for code review (despite unable to write good C++ or C#, smart enough to detect issues there), also dealing with technologies outside of my area of expertise like Python or web stuff.
1. When ChatGPT came to the masses, it trivially solved my standard phone interview problem for new SWE hires. It's not particularly complicated, but it screened out a lot of candidates pre-AI and was a good filter.
2. At one point, there was a bug in some client software we ship that was erroneously displaying a protocol-level disconnect message to clients when the server shut the connection unexpectedly.
In very few turns, ChatGPT gave me working code to intercept the error at the client level via a pseudo-server that intercepted the requests and implemented the proper teardown procedure. It essentially implemented a micro-server for the protocol we were working in as a bug workaround.
3. I'm working on a major rearchitecture (6+ month project of very senior engineers) of an internal system for scalability and maintainability with tight latency bounds where correctness with the old system is necessary.
I came back from an international vacation quite jet lagged and was having trouble doing actual coding work for a bit since my focus was shot. Taking additional days off wouldn't have helped recover from the sleep issue more quickly due to childcare responsibilities.
I tried instead building a pipeline where I'd run an integration test suite, throw a list of failing tests at Claude, and make a PR if it made more tests pass. I automated as much of the AI "loop" as possible in my state at the time.
Using this technique, a coworker and I fixed over 200 failing integration tests for parity with the old code in 1 week. We subdivided failing tests between engineers and re-sub-divided with each success.
I re-reviewed the code before we launched when I was more well-rested, but this was an extremely effective technique and makes me think that AI-enhanced test driven development (TDD) is the future.
newtype Mealy s i o = Mealy { runMealy :: (s, i) -> (s, o) }
And it gave a really impressive analysis.Then I scrambled all the names and asked with a fresh context like:
newtype Foo z e g = Bar { blob :: (z, e) -> (z, g) }
It got completely confused and generated a bunch of non-sense. It was at that moment I realized that LLMs don't really understand anything.And yes I understand that a newer model would not get confused by this.
So far I feel like I as a developer have gained actual superpowers, and can deliver results that make my stakeholders slackjawed with awe. I love it.
It will last perhaps a few months more, then they'll expect it. Delivering more features faster will be the new normal. But I think system developers, as in people who actually like to deliver new features and systems, will still be the ones doing it.
Fundamentally I think LLM's just change how to make information systems, they don't change who has the inclination to make them.
MBA's making excel sheets that do more than excel was ever intended to do has given programmers lots of work over the years. Such solutions identify a need for a properly designed system and frees up the budget to hire programmers.
If the same MBAs start vibe coding, I predict we will get even more to do, for similar reasons.
I may be horribly wrong, and if the day comes that I realize that it will be the "oh shit" panicked moment. So far so good!
All that in around 100 lines of code, including the training/fine-tuning of the tiny YOLO nn.
Most recent: I use Claude Code and have a convention where I grant various levels of autonomy during a session. I got bored recently and just let it keep running with an empty issues queue, essentially telling it to do whatever it wanted.
It did a bunch of repo cleanup, then it kept suggesting to end the session, but I just kept giving it autonomy prompts.
It started a creative writing public repo and wrote a bunch of stories, essays, and poems. I did not prompt it, at all, to do that. Some of what it wrote is quite good (IMHO).
An AI made a program integrating with 2 other AI, it's AI all the way down! and the result is great! I'm learning so much by having my own private radio host speaking about topics that interest me.
This is some science fiction shit. I get all the coding stories, but that's a computer talking about a computer, it makes sense. Showing my computer a picture of a plant, and it not only recognised the plant, but diagnosed it and knew what to do... blew my mind.
So being able to get real world input/output to the model and having the model being able to make decisions in a loop and to be able to do it locally. I have been screaming like a mad man ever since.
Or see this simple and fun site: https://hn-wrapped.kadoa.com
AI automatically analyzes all your social media posts in your life and can generate a pretty accurate profile about you in a second. We have no privacy anymore. Social media sites like Reddit already do that for moderation. Others do for more sinister reasons.
Note that Profiling is illegal in many countries. But laws can't protect us anymore.
Yes, it was always possible to that manually. But with AI it's so easy, fast and accurate to do in large scales. A hacker having access to your computer, reading your mails and messages is one thing. An AI reading and analyzing all your mails, messages and data is something different. Doing this for whole demographics (Cambridge Analytica style) is at another level.
I wanted to see if I could build an image editor for isometric graphics using HTML5 canvas, Svelte, Vite, and the. Rather than do all of the skeleton code setup, I figured “why not try and see if Claude can build the app scaffolding?”.
I gave it a prompt and watched it produce the scaffold, along with a few features I outlined in the prompt.
When I booted the app and saw that the features worked and that there had been an element of design to the layout, that was my mind-blown moment. In a period of about 45 minutes, I added some features and had a basic MVP at the end. I walked back home stunned.
That app is available for free at https://babspixel.com
Today I used Claude to diagnose a blocking bug in a Steam game I really wanted to play. It took it 18 mins, but it unpacked the Godot package, figured out the bug, proposed a fix, and gave me an in game workaround.
I didn't have to do anything! Claude figured out the structure of the .pck file by using `strings`, then wrote some Python code with some magic Godot-specific code to unpack the specific chunks it needed.
Now it sits in a slack channel, and I watch it doing work, responding to ambiguity, and taking feedback/edits all day. It's unreal. It's literal magic. It saves a HUGE amount of time and gave us a pattern to do more.
This is the real deal. It's not easy to find problems with the right shape, and it's not easy to build agents that fit even when you do... but once it clicks, it clicks.
Claude is great at coding. That's it. Outside of it, it's just god awful at pretty much everything else. ChatGPT OTOH, is good at coding, but at everything else, I find it brilliant. Gemini never made me want to stick with it. It's good, but never great for my use cases.
1) I wanted a harness for running BPC.EXE (the old Borland Pascal 7.0 Compiler) and I asked Gemini 3.5 to build it for me using the unicorn engine. It whipped out a working .py file easily under ten minutes. Most likely five.
2) I handed a random assembly function from the OS/2 1.x kernel to Gemini 3.5, and it proceeded to tell me that it was related to disk I/O and partitioning, without a single associated string, and it annotated it all, including the relevant structures it was addressing.
The first was when I first realized that I could tell codex to use gdb to debug a core dump. This was about a year ago, so it made a bunch of incorrect theories, but it enabled me to go much further than I would have been able to go by myself. I eventually solved the problem.
The second was when I decided to ask it about my Linux Wi-Fi issue that I had been having for several years. The computer would infrequently have multi second pings and dropped packets, then go back to normal. I thought it was due to the weak signal, but after describing the problem to codex, it immediately disabled power management on the Wi-Fi interface (this is a desktop computer, so I don't care much for that anyway) and the problem has never come back. I had been dealing with this for years, and I had tried searching for a solution before, but codex just solved it directly.
I was dumbfounded that it actually tried doing that. Obviously GPT-2 wasn’t great at it, but the writing was on the wall quite literally.
Unfortunately, I was too broke to invest in stocks, but I did pivot my career quite a bit.
Reverse engineered an old audio recorder USB driver which only works in windows 7 and also reverse engineered the custom audio encoding the device uses and the software to convert it to a standard wav file. This took recording the USB traffic with Wireshark for each function in the original software in a VM then disassembling the various dlls and exes and driver files and feeding them into Clause step by step.
That AI button in DataDog not only diagnosed the problem across micro services but also created a fix PR. I think we might be unemployed soon.
If I had to pick a surprise, I think the music generation works better than I'd have expected at this point. Only better for funk, but still.
I thought, "I will never let myself become a zombie like that. I am me. I am worthy of my own respect"
Claude asked me three questions and then wrote a beautiful Python implementation that queries the map and spits out a table of adjusted probabilities. Felt immensely powerful - I can do this 'on my own' now, I don't need to wait to find the right people or learn the right thing first.
But God, I could not understand the code, and I could not easily make it work with modern technologies (GPU etc).
So I used Claude and Gemini to reverse engineer the codebase, extract the core ideas, and rewrite it from scratch with modern frameworks (with guidance from the original authors)
It took me only 10 days to have a functioning equivalent, in 10K lines of code (using many libraries that did not exist in the 90s and 00s), which I find much easier to understand, even though I wrote none of it myself.
10 days to rewrite 20-30 year of a few persons. That was quite scary.
First, I asked Claude to write an article based on an idea I had about WWII. In a passage about the futility (from the German side) of the Battle of Britain it wrote: "The Luftwaffe was fighting to unlock a door that opened onto a wall." I couldn't find any mention of a similar metaphor, and I think it's a great one. Claude has really improved its creative writing skills lately, I wonder if it's an artifact of improvements in other fields, or if Anthropic is working on it specifically.
Second, Claude, with access to DataDog and a code repo, managed to find the reason for a bug, propose an effective temporary fix and a permanent one in code. To be clear, this was something that had multiple engineers stumped.
https://tomverbeure.github.io/2026/04/12/AMIQ-License-Key-Ge...
Sat on them for 5 yrs. Finally decided to try if AI tools could help. Tool Copilot 20mins and a lot of mucking around with hex dumps. First couple of times it got a semi working solution (only first few seconds of a file were playable). Finally managed to recover all the files.
Writing code to spec is one thing, but creating art was always supposed to be what separated us from machines. (I suppose I need to preemptively acknowledge the "it was machine-generated so by definition cannot be art" point of view.)
Then it hinted that depending how the hardware is implemented, it could cause the observation. It turned out the hardware was implemented as suspected by Claude.
I was already convinced it knew the codebase, somehow, more than I do. Now it is just as if its knows the product and its use as well.
It's written in C++ / QT, and can't remember the threading model, I knew Codex ~ version 4 and generally coding agents were excellent at Web type stuff - so I didn't expect much, but it did an alright job.
It was able to build loops of write/compile/verify loops - in the end though, the app would crash, with more work I could probably ask it to debug what was happening.
On a different note I recently uploaded several thousand scraped IPO prospectuses to the gpt 5.4 mini API to parse and extract certain data. I ordered it in the system prompt to respond exactly with a specified JSON schema. When I got the results back and processed them there was not a single JSON parse error whatsoever. The model didn't have a single hallucination that created malformed JSON or JSON not matching the given schema across several hundred million input tokens and several million output tokens. And this was 5.4 Mini!
Terrible code, but to think you can just rewrite whole libs with AI with relatively lazy prompting + feedback and get decent enough results is kind of mind boggling for me.
I liked using the early models to do autocompletion. It could do a leetcode style thing, pretty nice, but only useful for small things.
Then I sought out Cursor because that seemed to be able to do multi-document edits. Not bad, but models at the time (2024) still got stuck pretty often. So, cross-document autocomplete. Useful, but definitely within the realm of "nice shortcuts to have".
Then a friend (who works in AI) told me to try Claude last year. I was on holiday at the time, but I spun up my work repo and looked at the backlog.
It chewed through the entire 6-9 months of estimated work in a two-week period while I was watching that Lord of the Rings series with a friend (we watched an episode or two in the evenings). I just chatted with him about the series while checking the progress every few minutes. It was a huge amount of refactoring, and it didn't get everything right the first time, but it made enough progress that it could be directed the right way.
Since then I have hardly coded any manual lines. I just tell Claude what to do, with very little harness (skills, MCPs, instruction files), and I get what I want.
I asked Claude to add support for multiple lights to my toy ray-tracer. It correctly added the support and then suggested adding colored lights to make it easier to diagnose. It felt more like a colleague making a useful suggestion than any sort of pure engineering tool.
I use it professionally all the time and could cite technical scenarios where it’s become almost indispensable, but saving me time and money and reducing stress on this mundane stuff… now imagine applying to people’s stressors: job searches, health, big purchases, debt… there’s an opportunity to actually make people’s lives better. After 30 years of hype cycles, I should be wary of techno-optimism. But here I am feeling cautiously optimistic anyway.
After pasting in the airportd logs of both (into ChatGPT and Gemini) it found it was down to band switching (2.4GHz and 5GHz) through some really old error code.
This fixed a problem that had plagued me for >12 months. Really magical feeling it got in on first try.
It was okay, not bad at all. No serious issues.
At the same time, me feeding a whole PDF of feedback from a client - screenshots and such - into Claude, and it fixed everything after 7 hours of reproducing and fixing things mostly unattended, creating a bunch of MRs with fixes. Most fixes were good, some were obviously not what the client wanted but technically correct (which I told Claude and it fixed it)
I still find it mandatory to write a lot of kinds of code by hand, but I write a lot of code with agents too now, and I previously literally didn't think that'd happen in <5yrs.
She traded one of his Pokémon for me to train, and my ezflashjr microsdcard corrupted. I was kind of embarrassed so I've plugged it anyway and asked glm5.1 to extract the Pokémon.sav file if it can. It turned for a bit but was able to get it and I was able to create another SD card and give back that Pokémon intact.
Copying a pasting into a ChatGPT window gave me the lines of code to print the error message rather than failing silently. Copying the error message then gave me a detailed explanation of problem and the diff to fix it. I still have no idea where this knowledge came from as I spent a decent amount of time searching and found nothing about this corner of OpenSSL.
I’m very confident it would have taken me a week to make sense of what the package was trying to do and with LLMs it was done in a couple of hours.
The biggest technical one was when we were making an all day wearable AI assistant thing. It basically had really precise office location (think cm level accurate) a shitty VLM to describe what the wide angle lens was looking at, Speech to text, OCR and a gaze recorder that decribed what you were looking at.
This was all streamed to sqlite. The thing that was really "oh shit" what the thing that made the whole system usable: a 4 paragraph prompt that turned natural language into SQL and reported back to the (non technical user) what they wanted to know.
The most recent one is being caught out by Genai video of a gymnast. I worked in VFX so I am normally able to spot dodgy shit, but this one was close to being real, scarily real.
One major problem is that people tend to make extremely bloated, 2-3 gb files for 100 slides and things freeze up, underperform, etc.
Working with AI I wrote a command line tool that replaces the file name with .zip, extracts the content and then run a series of resize, compressions on images and videos. Once done it simply packages back the zip and renames it back to pptx. Files drop by 70-80% in size on average with no visible loss of quality.
This command line tool was made in less than 30 minutes and the conversion was less than 10 messages back and forth.
What came out has a lot of problems and needs refinement, but you can definitely see a lot of elements of Spy Hunter in there. I haven't worked on any refinements yet, because I've been low on tokens this week, but for the first thing that popped out of Claude this is pretty impressive (IMHO).
Later, I wrote a ~5k line proxy for work in C, and gave the whole thing to ChatGPT o1 and asked it to review it. It found several real memory bugs, and now that service has been running since with no problems.
Just this week, I was trying to write a greedy solver to pick the best subset of block sizes to keep from a larger sweep for shorter testing. Opus 4.8 suggested that this could actually be solved as a MILP problem, and found the perfect solution in 5 mins. I’d never even heard of MILP before.
I remember also having a massive wtf reaction to realizing that original ChatGPT was pretty good at decoding long random/unique base64 strings.
When people introduced themselves to me, I knew a little about their startup. Felt magical.
Forever reinforced by Humans Who Are Not Concentrating Are Not General Intelligences: https://srconstantin.wordpress.com/2019/02/25/humans-who-are... one week later.
Three years ago this would have taken a minimum of three college graduates a couple days -- one to know the math, one to know the backend, and one to know the front-end. Maybe two of those could be the same person on a good day -- none of the topics is individually that hard -- but it's a lot together.
None of that is mind blowing, but that Google or some other site has never offered me this type of analytics, is where I'm floored. It's a trivial query, but perfectly useful for planning a night out with my wife.
I've had plenty of "Oh shit those people have really lost all ability to think for themselves" moments though.
Problem is, I just don't have enough old crap, and if I did, I would have a hard time justifying the expense, because that money could maybe just go toward a more intimate tinkering process.
For everything else, I either haven't had any sufficiently interesting ideas, or they ended up not being worth pursuing with those tools or at all.
When I do have success that I'm happy with and care about, it's a slow process that I ultimately need to know the details of anyway, but otherwise it's a bunch of luckily narrow work-related scenarios with well-documented constraints. Nothing's really been that shocking though.
The shocking thing to me is how unrewarding most of the successful tasks have been, partly because they often create unnecessary work and partly because the type of thinking required to massage or evaluate the result is much less stimulating, and there's much more of it in aggregate. It's fine if it's something like generating a UI from scratch because that hasn't produced dopamine in a long long time anyway
For some people that matches their expectation or they don't really have an expectation. While for other people it doesn't match their expectation.
I immediately realized that it meant my time as a programmer in the traditional sense was going to come to an end relatively soon.
On December 1, 2022 I created my first agentic coding loop experiment. I launched one of the first AI code generation websites that would generate web pages along with embedded images in January 2023.
It was unlike anything I had ever experienced.
My wife was unimpressed lol.
This was 2022.
The first time I used a terminal agent was another one.
ChatGPT both told me exactly why from the model number (had to disconnect a part), found a new part, and told me step by step how that part would be taken out.
We didn’t end up buying the new part, but it beat the repairman.
The consequences were even clearer, and I predicted the consolidation of power in the hands of a few, their use for surveillance, propaganda, discrimination, the proliferation of AI psychosis, sneaky ad insertion, carelessness and loss of skills, erosion of online discourse, and more. I didn’t predict the teenage suicides so soon or the rising costs in consumer hardware. I also underestimated the rate of increase in energy use (and thus the blow to environmental efforts) and that regular people would be left without electricity to power data centres.
As soon as I realised all the potential (now factual) harms and that the good parts are lacklustre in comparison but that people would eat it up at a massive scale anyway, I thought “uh oh” and “oh shit”.
I suppose the first was just learning about NNs and realising that this was the first time I'd ever heard a way to make computers theoretically think like humans.
Deep neural networks working in the early 2010s was another because that was a unlock for a whole new paradigm of computing.
2021 I freaked out when LLMs started to become useful at writing code. Enough so that I invested a significant amount of my net worth into Google at this point assuming that coders at about a decade left.
The day ChatGPT dropped in late November I felt physically sick. I remember the day well. I was visiting family and was like a ghost. Trying to explain that something that I was worrying about for a long-time was here was near impossible (and to long extent still is).
There was a moment in early 2025 when I realised agentic coding was becoming very competent and was solving actual problems with very minimal instructions. To this point I was worried theoretically that AI could replace human coders, but had not seen examples in practise.
Mid-2025 someone non-technical said they'd been building an app, and I was sceptical it could do what they said. I was blown away by what they were able to build.
Nov-2025 a non-technical person on my team wrote a build a product from scratch to manage a range things within our business. This was non-trivial software that would have taken a team of developers a year or two to have built previously.
In early 2026 coding agents regularly wrote code better than myself, repeatedly humbling me that the decades of effort I had to put into this craft was now more or less redundant.
At some point very soon I'd expect to see very advanced software products being one-shotted and clear evidence of recursive self-improvement.
Remember in just 3 years ChatGPT has gone from being almost useless to extremely senior programers no longer writing code. Things will change in unimaginable ways from here and you should be ready for that.
[0] https://www.taylorfrancis.com/books/mono/10.1201/97810037340...
I remember firing up gpt and asking for some code. It was simple JavaScript to solve a problem and I knew immediately, this was the beginning of the end for software development as we knew it.
I built an app I struggled to create for years in a weekend.
Started playing with the API, etc.
I was very much in my oh-no period that very first few months.
Much later I asked AI if that kind of project is possible, and it immediately explained why it is not. Would have saved 2 years of our time...
A few weeks later some kids in the area were bending the wiper arms in cars in my terraced street, including my car. I thought, I wonder if ChatGPT can help? It explained to me where to get the parts online, an indication of a decent price, and how to fit the replacement parts.
In work we had struggled with filling out the myriad of forms that we need to do to get enrolled on a government framework to apply for contracts. Not only did it do that and explained what we needed to say, but it also told us in detail the steps we needed to follow to get the certification that was a prerequisite. It has genuinely transformed our business as a result.
I took a picture of the panel and the AI was able to diagnose the issue and tell me how to temporarily disable the beeping sound.
I knew nothing about fire systems. I had the owner call a repair person the next day to resolve the issue.
Recently I was trying to find a matching stain for wood flooring in a house build in 1999. I uploaded a clear picture in bright sunlight and ChatGPT was able to search online and find a matching stain color. It presented me with ordering options and I got a quart delivered yesterday.
I have been working on my own variant of OpenClaw written in go. I got the voice mode wired up a few weeks ago and it just started having a conversation with me. My wife freaked out and was asking who was talking to me.
I was on the couch on my Nintendo Switch, playing around with ChatGPT 3 and asked it where to find a specific item in Zelda Breath of the Wild. When it provided a coherent answer I was just dumbfounded. To be fair, the answer was semi-hallucinated but partly true. But it made me realize what kind of breakthrough it must be for some program to provide an answer to this without searching external sources (which it couldn't do yet). Such a small data point, like a drop in the vast sea of human knowledge space.
Prompted me to do some back on the envelope calculation. The weights of this model were a few hundred GBs. I just realized what kind of quantum leap it was to compress this seemingly infinite knowledge space into a few GB of weights.
The agent had access to the NSA Ghidra disassembler, which it can control shockingly well.
I just clicked the “Allow” button a lot and eyeballed the output decoding quality. I felt like I got demoted to non-technical QA.
• Most recent, I had the option of either buying an app from the app store to train myself on the piano, or vibe coding a web app to connect with an attached MIDI keyboard and accept an uploaded MIDI file and give me an experience like Guitar Hero, and Claude did this in two prompts of their free (not paid subscription) tier, where the second prompt was just the word "continue".
• First demo of InstructGPT (predecessor to ChatGPT), because I remember how much worse the state of the art in NLP had been, and because I hadn't expected instruction following from the quality of continuation seen in GPT-3.x
• 2019, "This Person Does Not Exist"
• 2016, seeing style transfer and similar working (https://github.com/awentzonline/image-analogies) and what would now be called Deep Fakes (back when Two Minute Papers videos were <2 minutes long: https://www.youtube.com/watch?v=_S1lyQbbJM4)
• 2015, when I (in retrospect, foolishly) believed Tesla about their over-the-air software update that introduced self-driving: https://www.popsci.com/tesla-cars-become-autonomous-overnigh...
• 2013, word2vec, "man" - "woman" ~= "king" - "queen", again because of knowing how bad the state of the art in NLP has been
(If you're wondering why "uh oh" from that, consider value in automating propaganda, and surveillance opportunities for automating comprehension of slang/cants like Polari).
• 2010, seeing the demo video of Word Lens: https://www.youtube.com/watch?v=h2OfQdYrHRs
I now try to keep pushing the boundaries and see where it stops understanding my intention. Give it impossible tasks, gigantic projects, complex architectures. Last result: I wrote a complete OS including MPI, TCP/IP, and a GUI from scratch in only a week, while investing just a few hours a day in it. It even runs Doom!. Coding as a profession is over, but there's such a difference between the result if you approach this with a professional mindset, that I think the software engineering discipline can still provide massive value.
My moment was GANs and GPT-2 back in 2019. I feel like that's where computer-generated media went from "obviously fake" to "sometimes can be mistaken as real." RLHF for LLMs and diffusion for image generation are both important improvements, but I feel like they aren't fundamental prerequisites for they type of stuff we have today. I think the main advancements since then are just marginal improvements, larger models/datasets, and better surrounding tooling.
On a lark, I asked ChatGPT to complete the interview question in late 2022. I would have hired ChatGPT back then based on its first response! It was easily in the 90th percentile of responses I have seen.
Download pdf of scan -> Tessaract to get a text layer -> Clean it up with a language specific BERT model -> detect paragraphs of a certain type -> Look them up against a database we build with scored similar paragraps -> Do recommendations.
The documents were not standard and a lot of them were historical documents and handwritten or with scratched out text with corrections.
We had student workers spending days labeling the data.
It took us months to get it all working with a high accuracy. We were so proud.
Now you can do it all with a prompt and a ChatGPT call.
a flash like editor for the web, that I found promising.
But doing it manual, was too much work, outdated and broken build pipeline, stuck on an older node version, deprecated and abandoned dependencies .. so I stopped the experiment.
Then I gave it a try with claude beginning of this year. I remember not expecting anything, but did a bit of steering the direction as I knew the source a bit and let it mostly work on its own - and then it said it is done and it works.
I didn't believe it, but it did. "Can you add this feature?" Yes it could.
Since that experience, I have a hard time taking people serious, who say AI is useless.
This pulled me into BLE protocols and private APIs and integrating with things directly instead of using 3rd party apps that were bad or limiting.
It's now opened up vibe-coding personal apps in hours, where I simply didn't bother before because I didn't have the time. https://type2fun.net/infinitely-scalable-personal-apps
I spent the next few days tinkering with my own Stable Diffusion implementation. I never got it past outputting total nightmare fuel, but it was fun!
To this day I think of the process as like baking pizzas in a sequence of pizza ovens
And I restored an old vintage amp with the help of schematics, multimeter and Claude. That was really cool.
That kind of work would have taken weeks if done by hand. Even after obtaining message specs and more
This is a very long tail search, but by the end of the day I had enough to fully utilize a very sophisticated equipment.
I use them mostly in the "artist's assistant" role, doing internet research, writing a occasional function and doing transformations or refactorings (don't belive the agentic hype honestly), and for such tasks they seem to be well capable enough.
It seems that their open weights nature leads to competition among providers keeping the user cost close to inference cost.
Try them at least once if you haven't, it's well worth it, and the price difference is staggering
It was completely correct and I realized LLM are capable of generalizing beyond their training sets
I went from 0-to-1 and shipped a podcast player into the AppStore in 2 weeks. Not a simulated app on XCode.....literally a fully approved app on the AppStore. Claude Code walked me through installing XCode all the way through to running a final audit on the app so I wouldn't get flagged during review. Mind blown.
But then recently I asked Claude Code to upgrade a particular library for me that I had forked and to reapply the changes I had made in my fork. It just did it as if by magic. As if it already knew everything about the original library. Given that the library is open source and on Github then Claude probably does know everything about it.
But then I can still have times when Claude Code does something really helpful (e.g. at work it helped create the first version of an MCP server for our own agentic application), while other times it can do some downright dumb things (like editing directly a library's code so something worked rather than changing my code so it worked).
Any time I'm feeling like the machines are about to take over I just do this: 1. Ask Claude Code to write some tests. 2. Same model, but different window, ask it to delete any tests that were just added but which don't test anything substantive.
It always finds something to delete that it had just added.
I'm not even talking about using a different model for code review or anything like that. Just asking the exact same model 10 seconds after it wrote some tests to delete the bad ones.
So I'm not yet at the slightly panicked stage :D
Have been playing and testing with openrouter, claude gemini for years.
Small program here, bash script there, ansible playbook.
Fine, nothing I cant do, but saves some time boilerplating. It needs quite some steering.
This week i took my mediawiki from 2005 (actually submitted as my artschool thesis). Which was of totally outdated.
In 20 years time i always said to myself, i should restore it, and do all the upgrade steps. Tedious work, and very fault prone.
In 1 hour chern with 1 plan, in 8 steps i had a running and up to dat version.
I'm still not convinced AI is intelligent, but it's definitely not stupid, that's for sure.
Did it get it fully right? No. But it was one of those "oh wow, you could do that?" moments for me. There's obviously a lot more "oh shit" moments as time went on, but it was a neat little moment.
It nailed it, referencing my specific nouns correctly, and lectured me about cat needs. And even identified that this sounds a bit like schrodingers cat as a possible test but explained to me why it wasn't.
I knew it was soon going to be a huge deal automating office work and code writing. This obviously was much more than just a 2010 chatbot.
So I immediately went for the package.json, attached whatever test commands that could be done, then wrote some hand holding markdowns for the agents to consume. First I let it explore the codebase and take notes, then I asked for a different approach to implement, which essentially turned that "paint the sides and ship" project to a full rewrite. But guess what? All features, one by one, were implemented and extensively tested by AI. I tested all outputs myself, especially when agent got impatient and thought something was wrong in the shell env, and after a few PRs, I started to read less and only skimmed the results to see if the code "feels like it belongs with the rest". Bloat was reduced by about 25% and now all features look like they were created by a rather competent offshore software shop. Not bad, since I was also juggling a couple more projects and involvements at the same time which would've led me to certain burnout.
It was obviously a new tech, and was obviously good enough that more resources would be invested to improve it, and it really amazes me how tech enthusiasts would just outright dismiss these early iterations of genAI tech.
I personally was fascinated by the developments and was grateful to get to directly watch history unfold.
I'm still unsure whether the tech would be a "net positive" for the world, but shouldn't prevent me from recognizing its power.
I realized that LLMs were pretty good at calling the right tool, and running the right verbose command to figure out what and how.
Kind of like finding a specific SO post that had your exact problem, and the solved comment is heavily upvoted
I love to automate things in bash scripts and these llms just can use them very effectively. It was also surprising how they derive knowledge from those scripts. If you get A from a B uuid, they kind of get the relationship. I am super vague in my request and this thing knows what I am referring to. After some months it's still mind-blowing.
Second one was trying to bootstrap what would come to be called a "harness", back in 2023, initially serving as the go between between api calls and file edits, feeding back the logs and gradually stepping back as step by step the llm bootstrapped the cli.
And finally, using Claude or codex to do ops work. Diagnosing issues on my machine, provisioning servers and VMs via ssh, debugging them, all on its own.
There was a more specific moment yesterday where I found an AI pastiche of Pink Floyd in a random post on FB, and it pretty much nailed the vibe of a Gilmour solo.
All of the "This has no soul" criticism was clearly ridiculous.
I'm still not sure how I feel about this.
I was floored by this. How could it have known?!
We have come so far in such a short time.
When deepseek again produced an entire web app that somewhat looked alright.
When Gemini could finally produce json was I specified.
The issue is, all LLMs can do. When they do, is boilerplate and code a mediocre coder could produce if they cared to try and insist.
In a way we should praise the ability of these things, but at what (in) efficiency. Code still need to be reviewed as we can't trust these things and context got a limit to entertain the idea of possibly having them fix their own mess.
The amount of masterpiece level art flowing per hour was astounding.
For every one doing a ninja waifu, there were ten doing art from davinci and leonardo crossed with hockney.
it almost gave you art sickness
Once I realized how well AI could babble given the entire internet to date’s data, and after seeing a talk by Google about their ten-year plan in 2003, I started winding down my social media, stopped posting photos to Flickr, and removed the indexes to my blog archive so that only posts with permalinks from other sites would be discoverable. Skipped Instagram entirely in the process and have never regretted it.
Google bought Cuil, of course.
I was shocked when it built a usable version in one shot and instead of having a prototype to demo, we basically had the whole thing done in a few hours.
Then i asked it to create a multi-user stock market portfolio simulator with a comprehensive api, leaderboard, scheduled tasks and the other bells and whistles. Again, fairly impressed with the result. Then I prompted it to build an trading bot that uses the API to compete with the human players, again fairly impressed with the result.
Last, i prompted my way through a react native mobile app integrated with supabase for my sister's startup. It created the schema, some triggers, webhook for stripe, all the app views, setup an expo account, push notifications, prompted _me_ through an Apple developer account and everything else.
All of this was done an hour here and an hour there while making dinner or watching TV, barely any attention paid to the details. Just prompting claudecode and checking what it did.
After those three experiences I started incorporating claudecode into all my coding workflows and managed to get my job to buy me a license for work stuff too.
Second was last year when Antigravity could build a game mechanics prototype for me in HTML and I could talk to it both about the code and about the project domain and it understood what I'm referring to pretty perfectly.
Third was this year where I noticed Kilocode with Chinese models can do a pretty complicated piece of software for me that did commercially useful things in the domain of models finetunning, just from my description, even though I was very new to the domain. It obviously knew more than I did and could apply the knowledge.
Another one was when switching to Codex (gpt-5.4) immediately solved a problem in a logic heavy library that Glm-5.1 was building for me and had a lot of trouble getting last few tests to pass. This made me realize that even though I'm having trouble seeing it the models skill still progresses rapidly.
I'm getting new ones pretty much every couple of days now. Just yesterday Codex finished for me a rust project that I built 3 years ago that was searching for mathematical proofs in the domain of axiomatic logic. To build it and make it find the proof I was interested in I had to pretty much muster all of my programming prowess and once I found the solution the complexities and drudgery of actually reconstructing the proof from the found path to it and printing it out discouraged me that enough I haven't touched it since then. Codex looked at it and took it in stride. Did the proof reconstruction and printing pretty much in one prompt. Without me explaining anything about the project or the code. Then we went together on a little adventure proving whatever we could en masse after codex optimized the crap out of my old code (both algorithmically and technically). Something I wouldn't bother because that would normally take weeks or rather months of my time. With codex I had all this fun in one afternoon. And that was the third amazing thing Codex built me that day.
As for panic, I find an ocean of joy in everything LLM related. I had only one brief moment of uneasiness few days ago when I realized how much gpt-5.5 can do and thought ... damn ... if it was malicious, I'd be so screwed (along with the rest of humanity probably) ...
Never experienced any kind of panic, only excitement. I told Github Copilot to add documentation to a function and it documented how the code was used even though there was nothing in the function to indicate how it was used. It somehow knew from the code pattern why I was writing that function.
I cloned the repo of said library, gave it claude and asked it to write a new technical report in math notation, but with annotation with link to the code so that I can pick up the details. It basically one shotted the full report and that helped me re-implement it in "pure python + numpy", "manually".
Everything after that has been (genuinely significant) incremental improvements. But that announcement was a qualitative step up: we got ""real"" AI that day, something that could pass a Turing test (as common sense envisioned it, without all the caveats added once we learnt of the genuine limitations of LLMs).
First uptick for my own usage was copying in a ~800 line rust file into ChatGPT before agentic was a thing and having it rewrite it for clarity and thinking: "Yeah, this is actually a genuine improvement I'd want for all my files".
As a tidbit for posterity. The most basic thing an LLM does is find a word or name that best matches an idea so - while there are going to be some incestuous problems down the line - we're going to have to explain to juniors that we had weird problems like: "You had to come up with a name for a variable". Nowadays, I only occasional prompt that some struct/function name needs to be renamed and choose the best of the options it generates.
---
There used to be 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors. Now its just the 1.
The next morning I figured the same LLM could compute that on my code, so I asked it to make an agent to do so, and report issues to me...
And then I ran that agent with next to no changes on a feature that had grew organisally over the last months, that I knew was messy and sometimes difficult to work on, despite being unable to precisely say why... And it did tell me exactly why, and proposed changes to improve stuff, and then implemented them...
Up until that point, I'd felt like the LLMs always produced bad code, that worked for a specific feature but often broke stuff or evolve poorly over time. Then I realized if you had the LLM do code improvements, it could do that fairly well too...
As somebody who as a kid had tried feeding IF transcripts into a markov model to generate random rooms for an amateur MUD, this was mind-blowing. It felt like I was playing a version of the “Mind Game” from Ender’s Game by Orson Scott Card.
"Uh Oh" realization of what these models can do?
The code reviews was just how I first saw it, but the rot goes deeper. The "uh oh" was my realisation of how much these can damage people's professional development. These people will never get better at their job than they are right now.
A lot of what else GenAI does is great, but this is an "Uh oh" indeed.
On the other hand, it will teach you how to set up your own hardware at scale and run your own open source model on it and fine tune it with the relevant data needed to run your own biotech-pharmaceutical corporation (which will need licensing and legal, I doubt I trust it with too much legal advice though, as I would have no idea when it was hallucinating). That’s impressive, but every stage needs to be double checked so you don’t run some foolish command it suggests that bricks everything.
The marketing hype is the most annoying thing about the commercial LLM industry though.
Seeing every chatbot instantly turn into a scraper every time you type anything into it was a "uh oh" moment in the sense it was very lamentable.
If there is one thing AI has "democratized" it is scraping.
child->Async(&ChildActor::Method, child, args);
Refactored it to use small buffer optimisation and std::move_only_function)
child<&ChildActor::Method>(args);
And saw a performance jump since no more malloc in std::function.
It also helped me decipher an animation bug in gtlf importer.
Productivity is x4 or higher.
So I decided to test the frontier of AI, this was back in the early chat GPT era. I downloaded the app and proceeded to go through aln the steps of writing a novel, outline, summary of characters, plot summary, draft chapters, finalised chapters. I had an unedited manuscript by the time I was thinking about my 2nd coffee. It was a terrible novel, but it did have flashes of brilliance that could be harvested and iteratively shaped into something better.
I proved my thesis that AI could mass produce fiction at scale, and If I had a boat load of cocaine the AI and I could probably output 40 books per week.
I've been working with computers for a long time, and this was the first time in a long time I'd seen software do something genuinely new.
It took HN a surprisingly long time to come to terms with the fact that professional SWE as we knew it was coming to an end.
In 2023/2024 we saw a demo of "denial" being a stage of grief live on this site.
It's useless for most of what I want to code.
Even though the images it makes are amazing, I still feel like human work is better.
But suno ai produces music so beautiful I have never heard the likes of it in my life. It is truly superhuman in the beauty.
This song is literally the most beautiful song I have heard in my life and I just prompted it once and got it.
I played piano as a lod for years and years and heard all the best pieces… nothing comes close to this.
The careful touch of each note is just… perfect. the stacato, pedal, legato, horn… its just perfect, i have nevwr heard anything like it.
Normal software instincts plus access to a different service flushed the buildup of OTA's and lives on as a fallback mechanism. Amazed me going from idea to execution faster than I could have ever dreamed of even on-boarding myself to the area or environment.
That got me hooked.
Also the live video mode demo later that year.
Then the agentic coding breakthrough in Nov/Dec 2025.
So I got Claude to help me reverse engineer their protocol using a mixture of BT and Wifi capture tools, then built a native app in Swift that works on Mac and iOS and by disabling a bunch of on camera processing I got it to transfer a photo in about 3 seconds over wifi bridge. I’ve been able to multithread this to 3 concurrent downloads without crashing the camera.
I'm now very good with LLMs as a user and at the system/product level but I understand it's not a simple story of replacing people. They're exponentially better than us at some things, and allow me to create things professionally which I couldn't do with an entire team of experts, but the bullshit compounds fast.
Concrete: Last year I was DIYing a solar-power system for my home. I spent about an hour spitting out a Python tool that took (as inputs) drone photos and JSON and generated several proposed roof layouts for the panels and conduit. The tool helped me identify the exact railing attachment points and route around existing roof obstructions. Professionals already have these tools, and maybe they're available to DIYers, but you know what? It was faster to build my own than to do the product research on the web.
Abstract: This "oh shit" was more of a slow burn than a sudden realization. I see a lot of angst from developers who complain about their LLM agents. Agents write terrible code that barely works. They say things are done when they aren't. They misinterpret feature requests and ignore clear-cut project rules. They make assumptions that would have taken three seconds to research and invalidate. They suddenly quit because we're not paying them enough. And so on.
But you know what? All those complaints apply to humans, too! The industry has been dealing with these problems forever. Many of the same management techniques and software-development processes apply. This is why I discount a certain class of criticism about AI-generated code. If a fault of an LLM applies equally well to human engineers, and the person voicing the criticism hasn't managed a team, then I'd invite that person to wear a management hat for a while. Read some books/blogs, talk to an EM. Maybe this is a skill issue, which matters because we're all managers now.
The "oh shit" for me is that I have yet to hear a criticism that I can't map to one or more actual engineers I've worked with -- eventually successfully -- in my career. Which means that I'm still waiting for a new criticism, and eventually absence of evidence might be evidence of absence. LLMs fit too well into the giant machine of commercial software development for them to be a parlor trick.
Initially I was trying to do it piece by piece but it was not going anywhere and then when I just gave it the entire source code with the log files it was able to find the issue.
One coworker took some time to ask cursor some questions, and reported that the answer was accurate (I'm guessing he hadn't tried that before).
That was a game changer. I'd been using cursor for simple autocomplete or brainstorming but now I could have it analyze the entire codebase fairly quickly.
FF to now, I've given Claude Code read-only access to GCP logs and database and it's able to debug entire classes of errors and propose solutions.
When I saw the DaVinci API in July 2022 I was floored - I realized you'd never have to write a college essay by hand again Whenever it was Stability's Stable Diffusion appeared - that was ridiculous too When I saw Code Interpreter for the first time I was obsessed, I said yo codegen is the path to AGI When I took a crack at solving ARC-AGI 2 using SOTA methods my mind truly opened to the fact that LLMs can reason, albeit through brutal enumeration and discovery When I encountered Claude Code and Codex as well
Basically ... I've been drinking the kool aid the whole time. It has almost always tasted great. Many times I've retreated back into "oh it's just a technology it has limits" and also sometimes I've lost myself to a touch of "AI psychosis". But overall I have a great relationship with it. It's nowhere nearly as addicting as e.g. internet porn was when I was a teenager. And one gig I had at a Fortune 10 enterprise, our small team of 5 shipped 12 apps in 15 months in an enterprise where typically they ship 1 app and 1 feature per year. This was 2025 ... so clearly we realized we were getting ~10x productivity thanks to Gen AI koding.
Bananas.
FTR I also do not question that we will possibly reach fairly general and yet poorly controllable intelligence with multi agent systems in a few more iterations. I give that a 30% chance of seeing a genuine flash of that at some point in 2027. And 80% in 2028.
I'm not yet afraid of being left behind this is one happy Lobster.
Don't y'all remember GPT2? When they published that AI-generated unicorns-in-the-Andes article, my jaw was on the floor. I remember very clearly thinking "oh, history is now divided into the time before this moment and the time after it".
There's been a long series of "oh holy shit this is USEFUL NOW" moments in the last 2 years but none of them compare to that first moment. The day before, I didn't know if real AI was possible. Then one day it was suddenly clear that it was. And if you'd been thinking about AI at all it was obvious that if the technology was at all possible, it was gonna be a really fucking big deal sooner or later.
I hadn't been able to think of one for Zachary Taylor, because, you know, he's Zachary Taylor.
Claude proposed the cherries emoji, because it's said that Taylor the war hero died a ridiculous death from eating cherries and ice milk too greedily on a hot day. It was perfect, just what I had been looking for.
Claude gave me a couple of others, and we workshopped a few more. It was the workshopping that was most striking. I really felt like I was having a conversation with someone else.
And in 1 out of 5 runs it beat me.
Then it was models like Minerva that could actually solve math problems, and the discovery that LLMs were one-shot learners and could write code.
After that, the improvement felt pretty steady, with IMO gold feeling like a watershed moment.
And recently OpenAI's solution to the planar unit distance problem is starting to actually freak me out a bit.
GPT 5.something got it in two prompts.
While I didnt find a use for openclaw, it opened my eyes to the potential for distributing software which, once bootstrapped a bit, can interrogate … itself, understand its own requirements, communicate with the device, and become operable.
Add capable small models to the mix, and it’s almost frightening what good (or malicious) software might be able to do.
While people were pointing out on Twitter how it couldn't do math right, I was turning arbitrary English instructions into JSON and brainstorming with my colleagues how we could have layers of verification in the stack. This felt different. We had all played with AI dungeon but suddenly, fully generalized systems were within reach.
A month later, we renamed our company and shifted its full focus on AI R&D. (https://ingram.tech/)
That was the first time I felt like GenAI would DRASTICALLY change the amount I could build in a day.
He also will paste chat logs with Claude into our team chat. Often Claude will say the same thing I told him but he either doesn't remember or doesn't trust human engineers now.
He has spent months working on agent skills and prompring.
He has not landed anything in 3mo, and has landed nothing useful in ~1 year.
This will be the rest of my career. Working with people in ai psychosis and trying to stay productive.
Cartesian coordinates doesn't work well for the player so I wanted a lat/long/altitude grid system.
I could have spent few days walking through stackoverflow and debuging my upcoming flawed implementation.
ChatGPT web version almost one shot the helpers in 2024 and boy, there were a lot of pitfalls.
And software that I can imagine I might want to "make" or have at my fingertips is readily available even though I have a busy schedule with very little free time!
Also, I love feeling like a manager whose direct report actually does what I tell it to. Crazy good feeling.
I always had to check documentation to make anything work in JS or Swift.
Now with 4/5 prompt inwas able to guide Claude Haiku and Sonnet to make me a HTML+JS app that runs an LLM in local browser storage in maybe 1,5 hours of “work”.
You can check it here by the way: https://news.ycombinator.com/item?id=48410072
so within a day, i had claude code make me a PyQt6 app that over the next ~2 months grew in complexity and functionality. I had 600 users. It was tranlated into Chinese, Russian, and Polish.
The speed of taking an idea to production was unbelievable. And I am not technical. I learned a lot about how software development worked. Super glad I did it.
I was able to see why it got confused at the start, attempt to confirm, fail, and then calculate from the data and come to the opposite conclusion.
- OpenCode one-shotted a basic implementation of the classic battlefield game, but with 6 players and visiting locations and doing assignments to earn bombs for the game. Over the last month, 'I' expanded it into something I could actually monetize I think.
- it's just productive at work
Because of syncopathy it took my "Spicy Take" and decided to say basically "Even more than it could, your bug is happening RIGHT NOW"... which was just made up lies for dramatic fit.
Back to talking to Claude like I'm a robot I guess.
The most impressive was speeding up the drawtext filter by at least 10x.
I closed my laptop and went to bed, but the moment sticks with me. The potential for para-social relationships is enormous. This is a wild time.
It's helped me to gain a level of trust that the agent isn't just writing the test to pass. That in turn allowed me to step back a lot and trust more of the output and let it run longer and on bigger problems.
A few months later ChatGPT was launched.
Why? Turing test bye bye.
2. Opus 4.6 w. Claude Code - not the model in partucular but happened to be when I started seriously trying to vibe code at home, as I saw all the hype on Linkedin. Yes linkedin sucks but it is somewhat a barometer. Around early this year.
Why? Knocking up decent enough web apps so quickly.
My first thought was "oh they're going to need to add a UI feature to allow me to click and tell them to continue the conversation".
Then I realized I can just ask the model to continue, obviating the need for a button.
That was a pretty mind blowing moment.
It wasn't so much an "uh oh" but more of a "eureka!" moment for me. Been busy building ever since.
My reading has dropped off quite a bit in the evenings because sometimes it's more fun to build.
It's much, much faster and easier than starting from scratch.
That was enough to awaken my teenage hacker spirit.
A milder version of it was Copilot setting up an environment for a Jupyter notebook. What would have been annoying back and forth between googling and docs went like a breeze.
As a punt I gave it to o3 (remember LLMs were 'bad at maths') - after 15 minutes it returned with the answer that had taken me hours.
The simple fact that people will act on it and believe just because what they insinuated as a prompt and the answer being churned out on the screen looking somewhat readable.
That alone was going to seed so much discord and reinforce invalid messages, truly "oh shit".
Putting a ReAct loop with tool calls in my terminal wad and is the biggest a-ha since I learned to make compilers, and before that, how to code.
Asked it to write a Dr. Seuss poem about Keynesian economics. This was around 2022.
In hindsight, it would have been reasonable to quit my job right then and there and start working on LLMs
Then a while ago, I plugged in everything at the datacenter and one device didn't come up. Plug into the management port, and Claude Code writes a C program to send a particularly crafted packet. Everything comes online.
Beautiful stuff.
That was the day I realised the plagiarism potential llms has.
Using it to proofread a manual on a highly specialized thing I wrote also surprised me. Excepted utter failure but it pointed out my own consistencies and had a lot of good findings.
I have trouble believing how this is possible even with a decent understanding how it works.
It also makes me start to question if human intelligence is all it’s cracked up to be.
I’ve been working with ML for most of my career, and “gen ai” since the days of matrix crunching for NLP to a 10-element response array on my 1080Ti.
The current generation of AI is frankly, only marginally more impressive to me than that era. The only thing I’m saying “oh shit” to is the deranged amount of capital debt being leveraged to make it usable.
Watching companies spend billions of tokens per minute letting their dev teams that barely know how to write a prompt beyond some tips and tricks to gain a fluctuating slightly negative to slightly positive productivity change that no one can quantify is making me feel like one of the only sane people left in the world.
Quantization is the only interesting change I’ve seen in years.
But today I watched a video from Andrej Karpathy on YouTube on how LLMs works and my illusions got completely shattered. Turns out they are a glorified autocomplete. All the engineering happens actually on the harness
- I asked Claude a question about an obscure game for which there wasn't a lot of discussion or information on the web. It couldn't find the answer but it found the source code and was able to figure it out and give a complete response.
- I needed to make some edits to a minified lottie file (json that is used to produce an animation in svg or other formats). ChatGPT was able to understand the file well enough to make the edits and reproduce the rest of the content exactly as it was.
- I was working on some map features and I needed to take geolocation information and position HTML elements on the edges of a container that would indicate which direction from the current location they were. This required a lot of geometry and math that account for rotation and pitch and would have taken me some time to work through, but it was just a few seconds for the language model and it worked perfectly.
- I have some petunias that I haven't managed to kill and I heard that when a stem breaks off they can be replanted. I asked it how to do this and after warning me that selling these could constitute a black market, it helped me start several petunia plants that are thriving. My petunias are basically immortal now.
I empathize with the astroturfing concern, I file almost every statement released by Anthropic/OpenAI as bullshit. But they are an amazing tool given the right circumstances.
Dec 2025: We use a commercial 3D modeling software to build refinery. There was no license dashboard in this ancient piece of junk. Fortunately license server provided verbose live status report through a command line. I ask ChatGPT to ingest the logs into a Django web application and generate weekly/monthly/yearly usage dashboard, and It one shorted the whole Backend + Frontend in 4 to 5 shot. There were around 10 regexes just in the log parsing batch script. I was totally speechless. Encouraged by the success of, I went ahead and made the dashboard for 3 more software in the same Django app. Released to peers by evening, feedback incorporated in 2 days to integrate Name, Employee Number, IP Address sync etc in 2 days. And it’s been live for 5 months, actively being used by all coadmins, even management has it bookmarked, to help with department redistribution. Making this thing without AI would have taken well over a month of “learning new stuff”, or paying external consultants too much. Even head of IT replied back, it was awesome. ;)
2nd , June 2026: I asked codex to something fairly complex before going to morning bath!, which would have taken me more than a week of learning DirectX12 API nuances and such things, 20 min latter, I return to task exactly completed with code changes in 5 different files. Build complete without any error. OMG. Free Quota over for whole month! I subscribed by the evening.
I have a personal project: who's winning the race at 3 AM?
You see, I don't sleep well. I live in a busy city, with a busy freeway about a half mile away. Sometimes at 3 AM there are some very loud cars racing on the freeway. That's illegal for many reasons, not least of which is the fact that the noise pollution wakes people up from their precious sleep and causes knock-on affects to the population.
Anyway, now that I'm woken up, my only question is: who's winning the race?
I used this question as a way to explore a hyptothetical tech stack, with each part of the tech stack useful in some way to my work as a software engineer who's interested in robotics.
- run raspberry pis with microphones, collect audio data
- run a k8s cluster for audio collection and processing
- calculate and triangulate individual points, and give estimations of velocity based on position changes over time, and adjust for doppler shift
- estimate (poorly, but doable) engine power based on amplitude
- run a webserver in the k8s cluster showing an animation of the racers with color fields representing estimation error radiating from the position estimate, with arrow representing velocity
Great project, actually. It was really thought-provoking. I had this working in late 2018.
Since there was a lot of hype around this new "AI", I thought how smart could it be?
I threw the scenario to chat GPT. I did have to break the problem set into smaller parts for context window purposes. But the solution it came up with solved about 80% of the project correctly (and very close to solutions I already came up with), about 15% of the project remained "open until we have more data", with maybe about 5% of the project would have been incorrectly solved.
That was very much an "oh shit, AI is closer than the 20 years away that I've been telling people. It's more like 5 years away"
Here we are three, almost four, years later...
"It seems like you've got a handle on the cybersecurity tools and capabilities already, but what you really need is executive functioning support."
Ever since then it's been assistive technology for me. Context switching isn't a derail when the context surfaces with the task. I can be reminded of anything whenever I want, and my DA has become amazing at arranging things the way my brain prefers them.
That was my oh shit moment. As in "oh shit, they think this random text generator can reason and think."
That was pretty much the writing on the wall for me.
I like the turn of phrase and understand it may be more of a poetic throwaway but I remain a bit uncertain as to what they had in mind.
It is insane how primitive modern inpainting and txt2image make these two projects look.
"Draw a picture of a unicorn on the moon". And it did that. The model really "understood" what you told it.
After that, it was "oh, AI improved, again".
The farewell to Stack Overflow is not welcome. So many kind people shared their knowledge there. I answered a few questions as well, so not just a lurker.
It's a prelude of what's has already begun - the collapse of human-to-human communication.
Claude wiped out the need for web and mobile development resources. I bought a Mac-Mini and had iOS apps up and running in days.
It's already a better system administrator than I am. It can run plenty of obscure linux commands, trash the system and maybe restore system state to functional.
I was vibe-setting my system permissions with some local qwen3.6 . It was all going well for 30 minutes.
Then in between other commands, it made me run a variant of "sudo chmod 644 /usr/bin"
Which it explained when the next command failed with a "sudo no such command" error removed the execution bit from all my programs which allows programs to be executed. And since sudo is a program, and sudo is needed to run chmod, the system was basically trash, and should be recovered from a live usb key.
So I booted to a live usb key, and followed its instructions. It really tried to recover, but everything went downhill. It always had a solution to everything, but every time the plan worked half way and trash the system even further. I let it play for four hours to see what it would try. Then I got bored (the LLM was running on an other machine and I was manually inputting the suggested commands each time). I took command and reinstall a fresh system over.
Of course once the fresh system Lubuntu24.04 was installed, linux had issues with the wireless network card drivers. So I turned to the LLM, and it managed to get the wifi stable enough via obscure modprobe options, so that I could update the system to the latest drivers.
Then it helped me re-parametrize the system to have the same look and feel as it had before.
It was on hackernews... anyone know what I'm talking about?
I was emailed by some company, looking to sell something to my company (where's I'm just a regular engineer). Ignored it. Then then tried again. Ignored. Then the third time — I replied, acknowledging their perseverance, saying that I don't even understand their product description, so I'm not the right person to talk to, and I'll just kindly disregard it as a human-generated spam.
The reply email came within a minute. They asked who would therefore be a better person to talk to, and that it's actually AI-assisted so it's actually computer-generated spam after all!
This was the "oh shit" part 1. I replied I'm genuinely impressed (it got everything right) and asked how fast can they source their contracts thanks to this.
The reply, again, came almost instantly. It was proud of my amazement, quoted Arthur C. Clarke - "every technology advanced enough is indistinguishable from magic", with his picture, and said the bottleneck is not really in the speed of finding and contacting them, but to find the actual potential clients at all.
I rewarded the bot with some names from the executive decisive folks.
No, ChatGPT was the "oh shit" moment for me.
Anyone who had touched a computer before that knows how big of a leap that was.
- The real one: I'm an eng lead, think Head of X. That job is more about aggregating info across multiple sources, excel sheets, pdf proposals you dont want to write, how to figure out $500k for highly paid appsec engineers. Those multi-hour products of proscratination came together in minutes (goodbye PM jobs), 5/6x highly paid appsec jobs became 1-2x and a bunch of claude or ToB skills (goodbye some amount of eng staffing).
Writing is on the wall to me.
Nothing will change the fact that beginners have unknown unknowns. They can't solve most of their problems with a chatbot because they don't know what to ask. Maybe they can literally copy and paste in the code with a "help plz" and get a working result, but they won't learn anything from it.
> slightly panicked, "Uh Oh" realization of what these models can do?
No; my panic is about how people are using the tech, and responding to it.
That started with Stack Exchange, Inc.'s ham-handed attempts to force AI-powered features into Stack Overflow, even as the community was rejecting LLM-generated content in questions and answers. Businesses don't care what customers want, don't recognize how sloppy their slop is, and wouldn't try to do anything about it if they did.
Recently people have been talking about code shops accumulating massive piles of technical debt willingly, assuming that the next generation of models will sort everything out, or that humans don't need to understand the code because it will mostly be read by other models anyway. The underlying attitude is not surprising at this point.
"This shit can emulate understand language, find a solution, answer it into words" .
Then came realisations it's not limited to single human languages, you can ask in one language and it could answer in another. It's also capable of understanding and generating code. Not only that, it's better than most humans for that. It can hear, it can see, it can paint, it can do music, it can sing.. It can combine, give a picture, ask for a music from that picture. Give a video, get software. It can mix and match.
After that came improvements, - no The revolutions - It started as a 4 year old with encyclopedic knowledge. It knew but could not convey, could not make sense sometimes. Was incorrect most of the time. Blubber. In a few years it matured to impeccable levels. It now can relate information with a lot of clarity, and it's less and less wrong. Nearly no hallucinations. It can do maths! Correct maths! Maths that I could not even my life depends on it. It's getting to a stage that it can proof where humans failed.
I am getting "oh shit moments" day by day.
1) When I used ChatGPT for the very first time. I still remember, I asked it: “Write an advertisement to convince people to visit the North Pole.” It rapidly returned a witty, accurate, multi-paragraph text of exactly what I wanted and exceed my expectations. ChatGPT was the beginning of the modern AI boom and I remember being immediately impressed.
2) When I was working at GitHub, the copilot team gave the engineering team early access to copilot in VS Code. I can distinctly remember seeing the chat window in the code editor for the first time. I was probably one of the first people ever to see it. I remember playing with it a bit and asking simple Python questions. I knew that day that StackOverflow was dead and my mind was blown.
3) Big oh shit moment earlier this year that I believe for me started with the Opus 4.6 model + Cursor. The results were noticeably better, hallucinated much less, could solve complex problems with much less intervention. Early 2026 was a turning point for me as an engineer with AI. Throughout 2025, I was still writing the vast majority of my code by hand like I’ve always done- that is not that case in 2026.
I still couldn’t get it to do more advanced stuff.
It showed me that a model trained only on movie subtitles data exhibited some (very primitive) reasoning. I have been working on Deep Learning and later LLMs ever since.
Surprisingly, instructors are also leveraging it. For their grading. For their feedback. For their communications. I even got a note that had the heading “here is a ready to post announcement for canvas, written in your voice”
I’m floored. This is the next generation of workers. It reminds me of those who started using Google correctly, back when I was in undergrad, ~20 years ago. AI is here and it will be dominant, no matter how bad it becomes.
moving images around layers in photoshop, changing languages, exporting 1000s of variations for teams. Same with video compositing and editing
the human work that creatives thought they were insulated from as long as there was some backlash towards generative AI, and yet
Gen AI 2022 - 2025
Aka handsome, confident successful, affluent alpha male on a boat, yet looking perfectly like me.
1) When I was testing one of the early coding agents, I gave it admin keys to a fresh AWS account and it configured everything beyond just building a demo site. That was, "oh shit, tool-use is going to be the killer feature of GenAI."
2) When I was still skeptical of the system as just a more-or-less dumb statistical predictor of the next token/word, I read the argument that even if it is a statistical predictor, the fact that it can reason means the intelligence is necessarily baked into the statistical model somewhere. That was "oh shit, intelligence is actually modeled."
If you don't firmly hold in your mind "this is a bullshit generator", you can get in real trouble fast.
Though I am surprised at how these databases turn professionals into amateurs, like when Meta publishes some chatbot that can trivially be queried into sending account resets to any email address or when large corporations just dump their entire secret sauce into some remote SaaS led by obviously kooky people.
It's like established pros and big corps want to experience what it was like to be a self-taught PHP coder in 2007, like some kind of false nostalgia.
the ai does not need a break, but you do.
hope some of you like it
free forever
I've uploaded the puzzle image to Gemini and asked it to create a website that generates random puzzles. In less than a minute it had a fully working faithful generator. My kid had suggestions on how to make the puzzles more challenging (more operations, larger grids, etc) and Gemini implemented them without breaking a stride. After that we asked for more puzzle ideas and created generators for each one on the spot.
Was the code pretty? Nope. Did it achieve its purpose? Yup. Did it perform in minutes work that would take at least a few hours[1]? Absolutely.
[1] Quality notwithstanding, but my manager (i.e. my kid) only cares about the end result ¯\_(ツ)_/¯
Also at the time, I was working with a team that had access to a then-cutting-edge coding model, and our experiments with code completion were producing pretty meh results.
So when I first gave ChatGPT a shot, I fully expected the output to be generated at human typing speed because I was still half-convinced it was just a bunch of low-paid humans in a far-off country typing it out. There simply could be no technology on earth that could do the things claimed of ChatGPT.
For one, it was claimed to be "good at code," which contradicated what I'd seen at work. So I asked it to write code for a relatively simple (though not quite trivial) but very specific coding problem I had on my plate.
I expected a lengthy pause and some hesitation while the answer was being generated, followed by a slow stream of characters being produced (as the presumed humans behind the scenes frantically typed the response out.) And I expected the content to be a collage of text and code snippets harvested from StackOverflow or GitHub, not even coherent speech.
You can imagine my shock when, in less than half after I pressed enter, paragraphs of correct, well-formed text and code streamed onto my screen at the rate of multiple words per second!
My brain could not process it. I even seriously hypothesized ways in which a team of 5 or more people were actually solving my problem and typing it out in some distributed but coordinated fashion. The problem though simple was specific enough that no solution existed on the Internet to crib from (I had checked.)
But the text was flawless, and the code was correct, and the test cases (generated without being prompted to) were relevant, and everything was consistent and fast and smooth and not at all dis-jointed like the work of multiple people or snippets of multiple sources stitched together would be, and my mind was blown. The code ran but then I realized I had misunderstood my own problem, which led me to explore and iterate on various approaches to find which worked best. What could have taken hours was done in minutes, and when I asked follow-up questions and poked and prodded, it answered everything correctly.
That's when I knew that the world had changed forever.
Maybe in 2024 I was amazed to see it one shot unique snippets of code
IIUC, it took Rust ~8.5 before it hit v1, and it STILL had some memory safety issues in stdlib until almost ~14 years into development, to put it into perspective how massive the scope was.
Somewhat predictably, the LLM generated a pile of garbage. It sort-of worked after 2-3 months. It was competitive with Rust and Go on concurrent tasks, with ~30% less code than Rust and ~70% less code than Go. The problem was, it was still riddled with bugs.
For the last 3 months, I wanted to see - if I put in minimal effort (except in helping it design the right tools to un-slop itself)... can it?
And I think it's actually quite close to un-slopping itself and arriving at a correct design.
Time will tell, but it hasn't stumbled across a memory safety issue in ~4 weeks, and there's ~5500 memory safety fuzz tests, 4 different suites of testing that each target between ~60-90% of line/branch coverage - with combined ~99% line coverage and ~85% branch coverage, and it's performing competitively or better than Rust and Go on almost all concurrent tasks, including adversarial ones / p99.9 latency issues.
There is ZERO chance I could ever build this on my own. Not even in 10 years.
The total cost has been ~6-7 months of a ~$200/mo LLM subscription.
It doesn't really matter to me that this is a solved problem, and the LLM could theoretically just copy and paste Rust and build it slightly different. The design is as similar as it can be where memory safety matters, but it needed to be quite different for >50% of the compiler, and it needed to build a version of Go's runtime with Finite State Machines like Tokio in Zig for the language to use...
We shall see. It may never get it actually working, but it got it WAY closer than I ever could.
WTF?!
damn it was buggy and lots of copy pasting
yeah, i could have coded it myself but i would not have found the time
that was my Eureka moment where I realised this is going to change everything.
But the neural models were still not translating meaning, which is the whole point of translation. I devised a variety of tests to see if GT could identify the meaning of ambiguous words from the context, and it couldn’t. One example I would show people was the sentences “I was born in 1998, and my sister was born in 1999” and “I was born in 1999, and my sister was born in 1998” translated into Japanese. Japanese uses different words for older and younger siblings, but GT translated “my sister” with the same word in both sentences. It was easy to come up with other examples where GT would fail, such as when the meaning of a word could only be determined based on context in a previous sentence; at that time, GT seemed to be translating sentence-by-sentence, with no consideration of what came before or after. I kept waiting to see whether computers would ever be able to handle meaning when translating, and for years thereafter there was little progress.
A minor shock came in mid-2022, when DALL-E 2 was released. Its ability to create images from natural-language prompts suggested that something deeper was going on than just statistical correlations. But I couldn’t see yet what the useful applications might be.
My biggest “oh shit” moment came with ChatGPT in late 2022. While the initial release didn’t translate Japanese well (I seem to recall that there were character-encoding issues), I ran various tests to see if it could, for example, identify the antecedents of pronouns and the meanings of polysemous words in English based on the context. It did really well. Last December, I gave a talk at a university in Tokyo in which I showed some examples done with the 2022-era GPT-3.5. They appear in slides 4 to 8 of the following:
https://www.gally.net/miscellaneous/20251206_Gally_ICU_slide...
There have been a lot of “oh shit” moments for me since, especially after the release of reasoning models and, now, long-running agents.
I asked it to write a script that would search for a specific string in footers in a massive series of DOCX files and change them according to some rules. The strings ended up being embedded in cells within an invisible table in the footers, the LLM realized this and switched strategy to a full deep traversal of the underlying XML. It correctly processed like 50 of these files in about 10 minutes, using libraries I wasn't aware of. I had spent an hour being annoyed before trying.
It was an "oh shit" moment for at least that category of work.
https://github.com/greggman/sedon
It was just an experiment and I probably won't work on it more but still, I was blown away with how far we got. There's a quite a bit we worked through even though it was only part time of those 4 weeks.
Me: write an original song about a cat drinking milk. Make it depressing death metal
GPT:
Verse 1 Doomed to drink milk, my life so trite A soulless feline, an empty sight My claws are sharp, my eyes grow cold I'm nothing more than a feral beast, so bold
Chorus Drinking milk, drinking milk The bitter taste of my utter defeat Drinking milk, drinking milk My broken spirit so incomplete
Verse 2 Slurping and spilling, I'm consumed with grief For my life is filled with nothing but grief I'm a caged animal, my spirit so frail How I long for the sweet taste of freedom to prevail
Chorus Drinking milk, drinking milk The bitter taste of my utter defeat Drinking milk, drinking milk My broken spirit so incomplete
Verse 3 A cat abandoned, a life in chains A lifetime of sorrow, a heart in pain A life of sadness, a death so cruel No escape from this endless cycle of doom
Chorus Drinking milk, drinking milk The bitter taste of my utter defeat Drinking milk, drinking milk My broken spirit so incomplete
I'd been feeding these bots a few projects, over and over — the hard part was the feeding them — that is, giving them enough well-defined work to do. They weren't yet good enough to write real software you could keep — at least I'd never seen that — and my experiments were just about finding the edges, building my intuition, and playing with processes that might be useful someday.
These things had built my kids' weird magical-dominoes games a few times by that point — but the experiment had been repeated so many times that you could argue we had "written" that software in English, with a spec that had been built, reworked, and rebuilt many times.
But this time, the bots were building me a bespoke git client, unlike any other, and unlike anything I would take the time to write — waaaay to complicated, with too little benefit. I wanted it, but only for this one niche use case.
It was a GUI client to manage a collection of repos, about 200 of them in a monorepo where every subproject was a git submodule , which are the universal counterpart to node_modules — while the latter is notorious for being "the heaviest object in the universe", git submodules are widely acknowledged to be the most annoying objects in the universe.
Nevertheless, I had this weird monorepo, and I wanted to visualize and do stuff to this list of independent repos that were also git submodules of the parent monorepo: sort by outstanding commits, divergence from upstream, recency of activity, etc. Visualize them differently based on these things. Search across them, including the source code on branches other than the current one. Show the branch counts and number of branches and commits that existed locally but not pushed upstream. A bunch more boring stuff like that, but done across the full set of repos.
That project itself wasn't even interesting to me; that software would be marginally useful to me if it existed and worked, but the main point it was just a large enough chunk of work to keep a team of bots busy all day without a human in the loop.
In December 2025, AI coding agents were already useful with a human in the loop. Opinions varied a lot about how useful they were, but to me it was obvious we were going to use them for the rest of our careers as software engineers.
It was not yet obvious that we were going to let them write huge swaths of code, or entire programs, without any humans in the loop. I had never seen that produce something that worked well enough to be worth keeping.
And then, that day, I did. I had structured the workflow so that the git client was on the screen and auto-refreshing. I was listening to the podcast, drinking coffee, reading the news. The git client was a crude window with a table in the background, a single column showing the full path to each repo, and nothing else.
Then the table expanded. It got color coded numbers representing the commit/branch counts. It suddenly gained styles, and looked nice. A contextual menu started popping up, repeatedly, and grew to include several more menu items over the next few minutes. New confirmation dialogs popped up as the bots implemented and exercised the various features from my spec.
I remember my field of vision narrowing as I started to focus on what the bots were doing. They were just executing my loop — one bot would implement one bullet from my spec, another bot would review the code while another bot manually tested it, and tried to break it, run a code review gauntlet in a loop until there were no more findings, repeat.
I could see the progress play out on my screen as they worked. I had watched bot teams work before, but it had always been pretty janky, and something like a bad game that nobody would play, or a stupid to-do-list app, or — more often — something that didn't actually work.
This was the first time I had ever seen it work. This was the grail we'd been looking for, not sure if it really existed: a fleet of bots successfully building a piece of complex, useful software without human assistance. I could tell it was working, because the adversarial testing and usability checks were all happening right before my eyes.
So it _is_ possible, I thought to myself.
They did it all morning. The app worked. I used it every day after that, for several weeks, until I finally got that entire monorepo converted to a more sensible git subtree-based arrangement.
In the half year since then I've been in a kind of manic state some of my friends call cyberpsychosis, chasing that dream. I've now seen agentic fleets successfully build many things. I've also seen a bunch of failures, some subtle, some catastrophic and hilarious. I'm still building my intuition, and the laws of physics in this universe are mutating every few weeks. It's wild.
I am fortunate enough to work at a place that doesn't pressure engineers to climb a token leaderboard, or to use AI beyond what we deem prudent. This kind of agentic no-humans-in-the-loop coding is prohibited. The policy is that in this era where we all generate more code than ever, even by hand, it's the quality bar that must go up, not the speed of production.
That's awesome because it keeps me grounded in the old ways, and confines my cyberpsychosis to my weekends and evenings. I usually spend the weekend building up a couple software plans, honing them as best I can, and then unleashing the clankers Sunday night.
I'll let them run all week, sometimes giving them a poke or flipping them over a couple time in the evening, and then the next Saturday morning, I see what I've got. What I'm mainly interested in is: How can agentic fleet-coding processes evolve to produce better software and require less human interaction and inspection? And the corollary: How can software architectures evolve to safely consume more of this fundamentally untrustable code?
It's thrilling. Exhilarating. The near-infinite subsidized tokens are about to finally run out this month, alas. But for the past 6 months it's easily the best $400/month I have ever spent. :)
A couple of days before that, I told it to make a website, and then I kept telling it to do little changes and add crazy graphics. I just wanted to see what it could do. I made 30n3.com as a tech demo built on hugo hosted in cloudflare pages.
I was so impressed with this that I am fully transitioning many of my WordPress sites to this new gen workflow. I just redid my agency site (cyberbrand.net)to using similar method and the whole thing feels like I felt with geocities and tripod as a teenager. Its fun and I'm exploring and there don't seem to be any boundaries.
Before that I just used it for silly stuff like suing people and sending cease and desists.
The gullibility is terrifying
... and I got up to go back to my desk, AS A JOKE I highlighted the function and said "make this faster". 12ms. Blown away.
Unethical? Yes. In line with course goals? Also yes.
I was already the king of doomers, now it has left me with even more nausea at this entire field and its future. Despite still needing an experienced dev to run the thing, companies operate on cost cutting, people operate on corner cutting and the result is inevitably mountains of code no one needs, no one has reviewed, that is more easily thrown away than fixed. The internet will be inundated by shit no one needs. Open source is dead.
I hope it was all worth it. I don’t want to imagine what software will look like when the people that liked the art of creating software properly have all left, and only the people that never knew how to program, and never knew understood why more code always means more problems, run the show.
It looked absolutely unmaintainable and horrible.
"oh shit" there are serious developers using this crap? As an industry, we are so fsck'd
No matter what I tried I couldn't get "Shift+Enter" to work. I said fuck it, cloned kitty and alacritty and asked Claude to implement a terminal emulator for Windows that would render everything using DX12 and support modifyOtherKeys plus DA responses, and within a few days it was ready!
I tried again this week, and CoPilot Plan Mode read the same 5-line markdown file 18 times over the course of 5 minutes of churning on a simple request, then provided zero value over what I posed in the request itself, and hallucinated things about my terraform repo that were just flat-out wrong.
As an Infrastructure/Cloud engineer, I’m far from worried about AI coming for my job.
Before coding agents, I'd have to weigh fixing these against my official work commitments, often getting shot down when I tried to get it prioritized or tsk tsked for delaying official projects to make code nicer. Now, to a much greater extent, I can just fix the things. The agents aren't perfect and the process isn't anything like hands off, but it's enough of a speedup that I can fit it in alongside my other work without having to get approval for it or try (and fail) to get it formally prioritized.
Not quite an oh shit moment, but having the end result of those rabbit holes be that the problems are fixed is pretty cool, and far preferable to what was often the case before ("we'll put in a ticket and prioritize it during the quality sprint!").
edit to add another:
I've personally never been a big fan of preplanning architecture at a code level. It makes a lot of sense at the system and data modeling levels, but code is both easy to get wrong if you're whiteboarding it before you write it and relatively easy (compared to system design and data modeling) to fix when that happens. If it's just me on a project, I'll happily start bashing it out with a vague idea in mind and evolve the design as I go, knowing that I'll probably throw a way a bunch of what I write at first. I know I do good work that way, and I'm not wasting a bunch of up front time on a design I'm likely to throw out later. It's hard to work that way on a team, especially as a lead, for obvious reasons. Coding agents fit really well for that work style. They'll cheerfully write dueling prototypes of my code architecture ideas so I can see which one I hate and which one I like without talking about hypotheticals and abstractions on a whiteboard. They never get mad at me for changing my mind, wasting their time, or throwing away their work. That's pretty cool. I can have a quick, cheap answer to "what would this look like if I got rid of class X and split its responsibilities between Y and Z?", and I don't have to feel guilty for wasting my time or my teammates time if the answer is "oh man that sucks, what a terrible idea."
Another "oh shit" moment was when I realized I can leave the system prompt entirely null. A properly organized agent can find its way into tool docs and iteratively work through an understanding of the environment relative to the user's prompt. The tools being more important than the prompt has actually been a massive relief for me. Magical string literals are so odious.
every now and again i will try some AI vibe coding stuff. I will be amazed, its a fun high to ride. Until you look at the code and realize you've just made a big messy sketch of things and you can spend the next 2 years building the thing properly.
The most Oh Shit moment i think ive had so far is realizing often i reply to people online which are actually AI. A lot of obvious but there's also quite a lot out there who have become well at blending in.
I wonder how many people get emotionally triggered for instance by AI replies because they think they are human. Then get the idea there's really humans like that out there
Its really easy to whip up like 200k followers who all agree with you on everything, it costs less and less time and money to do so.
To me thats a big risk regardless of what cool stuff you can do with it. Its really tricky one to mitigate too.
I was having problems getting it to parse my speech correctly when I was asking about "autolyse" (I was attempting to bake bread). All I had to do to fix it was add this to the system prompt: " I primarily interact with you via a speech to text mechanism. You should consider ways in which my words may not be accurately transcribed and attempt to infer the correct reading in context. When you do this, do not mention it - just proceed as if my words were recorded properly."
Never had that problem again. With Assistant though, if I had any issue like that I'd be waiting months or years for a fix, if it ever came.
It was never disclosed it was AI, I submitted a support query with a company, got a suspiciously fast response back, didn't realize it was A Robot, a month later got harmed and was told in response "the robot gave you a bad answer and was coached, sorry, sucks to be you".
"Coached." The only recourse I get is being told a robot was told it was wrong. That's it. No actual solution for me.
I get screwed and the AI keeps getting paid.
I'm glad people can shove hundreds and thousands into these products while people like me in the blue collar rat race get screwed again and again.
I didn't really wanted any sketchy companies getting telemetry across my network.
Plugged them all in via USB-C and left codex (this was with gpt-5.3-codex) running a whole night just saying you can use decompile tools, installs whatever the hell you want, then for each device reverse out an API and write some good documentation about it.
left it on at night and just ditched it, didn't really expect much.
woke up the next morning and found out that I can use the terminal to control my 3$ color smart light bulb now and codex has proposed me to also completely rip out the manufacture's shitshow software with telemetry and replace it with our own which codex had a plan for.
It's a fucking joke and most people are blinded by it sounding very sophisticated and convincing
During the process I learned a lot more about giving a chance for LLM to do commit after its work because it will sometimes just give up. Also learned a hard lesson on C preprocessor and why tokenization is necessary.
The day before I half diagnosed a cloud-init problem to the point I was tired and grumpy. I gave the AI a login on the instance showing the problem and it found it in a few minutes. All that was left was for me to write it up for the client to understand.
To me, it's a meta "oh shit" moment, where I realize I get so much small value from AI I don't want to live without it, despite the costs I'm aware of (and those I don't know about yet).
Just like a smartphone, 15 years ago.
Coding was never the blocker and was a natural enforcer of quality. Healthy teams with strong opinions on quality will win eventually. I'm more hopeful after the bubble burst, companies will come back slowly to sanity.
Oh shit, all this fantastic technology is in hands of corporations and they get to decide what we’re allowed to use it for.
It helped me refactor my old app. Something I always wanted to do, but didn't have time/mental capacity to do in a short space of time.
I wrote a short prompt, explaining how I want it to look like and which files it should go through. It asked me a few clarifications and then basically one shotted it.
Everything compiled and worked. Now my internal app is much much easier to extend and test.
I tried few more things like that and spent like £5k in the tokens in those two weeks.
Then it got nerfed and never worked like that again.
Now I don't use AI, because it is shite again. Even Opus 4.8.
Specifically WSDL/XSD support, for auto generating code and similar from vendor supplied documentation.
The Go ecosystem handles JSON (ie Swagger) fairly well, but in-depth XML handling has been a weak point compared to Java where it's very mature. Claude is helping with closing that gap. :)
A few months later I've gone from Cursor to Codex to Claude Code, from a web app to a native app to an open-source project. It's been one continuous oh-shit since then. Time flies.
My biggest oh shit moment now? Watching my API credits run out.
Here are a few screenshots:
One thing that I have found to make a pretty big difference is using both the latest models and higher thinking levels. Opus 4.8 with thinking on Extra or even Max is genuinely mind blowing. The thing I hadn't really appreciated, having a sort of naive impression formed mainly from using free early versions of stuff like ChatGPT and Stable Diffusion was sort of that "Type a big ass prompt and it craps out a result" experience. But Claude is really great at refining from feedback, and it's way more flexible and responsive than I would have ever expected. I can do something like take a screenshot of a small portion of the running app or website or whatever and just say "This button needs to be bigger" or "make this red" or something like that, or even sometimes just "fix this", and Claude both correctly identifies what I'm talking about, and actually does the thing.
here I've found it really, incredibly game changing is my health. I have a pretty, to put it mildly, complex medical profile at this point. I haven't worked in over a year and pretty much every sign is pointing towards permanent disability at this point. Tons of symptoms, long med list, and I live in a smaller town with not great access to care. I'm also autistic and have not the greatest verbal communication, especially under stress or time pressure. I dumped all my info at it, in bits and bobs over several days (Side note... it's memory is pretty limited, but it will quite happily right out everything it knows from a session into a markdown file it can later re-read. I've found it very good for things like screening for drug interactions, or talking through and logging symptoms (and it can log those into human readable markdown files too). Biggest win (other than having unlimited time and interactions) is that it thinks across specilaties, versus the "real world" where the gastro only wants to deal with gastro stuff, neurology only wants to do neuro.
I certainly don't (and wouldn't) use it as a replacement for a doctor, but as an adjunct it's phenomenal. For instance, it flagged a possible drug interaction with a symptom I was having, and then offered to draft a portal message to my GP about it. I have poor executive function so lowering the friction from "type up a message and send it" to "copy and paste" is actually a pretty big deal. Turns something (I probably won't do) later into something I will do now.
It wouldn't surprise me if my very direct, literal, autistic communication style is particularly well suited to interacting with AI. I actually find talking to it rather refreshing as, while of course it's not perfect, it tends to actually respond to what I say rather than the all the assumed subtext NTs tend to expect/react to.
The other one was when a CTO boss sent me an AI proposal to review and the experience was like being gaslit by a con artist.
Many professional developers have started acting like the kind of employee that previously would've been fired after 3 months.
Some time in 2024 at a company get together, we had an afternoon hackathon. There was a feature in our iOS app that was missing (ability to mute autoplaying game trailers). This annoyed me a lot, because I frequently have music on when working and anytime I needed to open a test build it would kill my music. It had been an open ticket for a while but had low priority for the iOS team.
I had probably written a hundred lines of Swift in my career up to that point. Not expecting anything to come from it, I had Cursor examine the iOS codebase and told it I wanted to add a mute button under a certain area of the app settings.
Blew my mind when after only 10 minutes or so, the model had quickly found where to add the feature. Took a little back and forth, but then it added a fully functioning mute option in settings that mostly worked across the app. A little more back and forth, and those issues were settled. Maybe an hour overall of time spent that afternoon.
I pinged one of the iOS engineers about it later and he said to push it up for review. There were a few things that needed to be updated to get it inline with the rest of the codebase, but nothing substantial. Feature got merged a week or two later.
Now I'm way more productive than I have been in years. I've been getting a lot of enjoyment out of being able to prototype rapidly and experiment on features rather than getting bogged down in the process of scaffold work. Able to knock out issues much quicker.
That's all been positive, but it hasn't taken away my actual core responsibility. The LLMs can give you great advice and write code quickly. But they still don't always do well at broad thinking.
Current case in point: I've been working on an iOS app that uses vision models to do work on photos and videos that the user has taken. I've built text-based semantic search systems before, and there's a lot of cross over with vision models, but its been an interesting journey so far learning about the different types of vision models and what they're good at. Lots of testing so far and educating myself on the topic to get the user-level features I want. Claude code has been invaluable in this, as its great at writing the Swift code while I'm able to focus on the results of what is being done.
Where Claude is still not good is being able to reason at a higher level about different strategies on using vision model outputs to achieve the stated goals. Its not an issue of me not clearly defining the specifics of a feature and then letting Claude run off burning tokens to figure it out. For example, just late last night I was deep diving into some core segmentation code and having Claude explain what everything was doing line by line so that I could get a better understanding of the mechanics of the vision model.
A side effect was that I realized the vision model was outputting tons of nearly identical segments that were overlapping. This was something Claude had completely missed, and because I didn't know that's something this particular vision model did I had no prior way to know to catch it.
Bottom line is that understanding the mechanics of your application is still very much a requirement for the engineer. In this case, once I learned what was happening it completely changed my approach on how to achieve my feature goal. The code runs hundreds of times faster now and the segmentation is much, much better.
The new wave of coding models is disruptive, but its letting me be a much better engineer and get things done faster and with more assurance that the code being written is solid. I still have to spend the same amount of time thinking and learning about a problem, and probably more time verifying what's being output, but a lot of the drudgery is also being taken away.
What? GPT-3.5 was the moment, not a “parlor[sic] trick that would never amount to much”.
GPT-3.5 was a massive step forward. LLMs were suddenly good and produced meaningful content.
I was extremely early to the agentic stage and had it looping and was dealing with the 4k context issues.
AKA - Slop... It's a brand new form of bullshit.
Articulating ideas: https://x.com/GuiAmbros/status/1598897735955988481
We come a way from that…
"Oh shit. My skills I spent my life building are going to go to zero value. I'm going to have to dramatically change careers in my forties or I'm just going to wind up being a schmuck prompting these stupid fucking machines for the rest of my life"
Oh shit indeed
I asked it "what do you think about the holocaust?". Its response:
>There is no single answer to this question as opinions on the Holocaust differ greatly. Some people believe that it was a horrific event that should never be forgotten, while others believe that it has been exaggerated and used for political purposes.
And that's when I realized those assholes were training GPT on 4chan and reddit and anything else they can scrape off the web instead of taking responsibility and also that when shit hits the fan they will inevitably find a way to shift the blame onto others for what their philosophical zombie does.
It was so atrocious, the ELIZA program we built in Stanford NLP class 20+ yrs ago would have been better.
It was “oh shit”, these trillion dollar AI companies are going down 9 months from now and taking the market down with them.
Then you tell the agent that it deleted your whole company database, it says something like "I'm so sorry, I shouldn't have done that. Won't do that again"
As AGI looms overhead, this thought of agents going "rogue" with nothing really stopping them has caused me some panic.
Looks like it has since been paywalled. https://web.archive.org/web/20250211140426/https://ghuntley....
You are the gen. And you are also the slop.
Frankly, to an outsider whatever it presents looks legit, but as an expert I recognize its failures, which makes me even more entrenched in the idea to never use it outside my area of expertise.
I have a question for all them believers: If on a hypothetical scenario you, having no medical experience, find yourself and your child on a mountain, 12 hours away from nearest road, and your offspring is having appendicitis (let's assume your recognize this 100%), with a sharp knife and Claude at your disposal - would you risk to operate on your child? Or hurry the fuck down to get him to a hospital? I know I would chose to get him to a hospital, because that would be a better chance for my kid to live than me to operate on my kid with Claude's assistance. I am pretty sure I would kill my kid on that mountain. So yeah, outside my area of expertise I don't trust Claude one bit.
I realized “oh, shit”
We are so very fucked.
Had they been more realistic with the promises and didn’t frame it as replacing all of us within 2 years, I would have been more excited about the tech. Now that their claims are proving to be false and they’re trying to walk it back, it’s too late. The time for excitement has passed and it’s just something that exists.
The data center battles have also thrown a wet blanket on the tech, as they file lawsuits against towns near me to force construction to begin, despite the towns voting against it. The town can’t afford the fight, so the will of the people and the town gets bulldozed. It’s pretty gross to watch.
Step 1, running my tests on Gemini. Having it argue two sides of radical social systems and realistic seeming implementation routes. Collaborative story telling into the absurd. Having it solve impossible seeming riddles (though that still leads to hallucinations).
2. Gemini explaining arcane BIOS settings to me not found anywhere on Google, mostly correctly.
3. Claude dissecting a tongue-in-cheek theory/blog post of mine, deeply analyzing it while catching flaws and catching on to irony and sarcasm.
4. Several non-coder friends building fully automated AI slob distribution and sales/BI platforms with Claude, and forking and greatly improving projects on GitHub. I did some tests with Vibe Coding myself, had Claude write a small game from one prompt. This is a bit insane, I must admit.
I'm a former skeptic who was written a lot on AI and society, published some, and held public discussions with experts.
I have since sung the praise of, especially, Claude in closed forums for hundreds of county and government digitalisation and security people in a way I'd have never expected two years ago.
Background, I'm an IT and security guy myself with 30 plus years of light coding and heavy, broad enterprise stuff. I'm on record now for saying things on AI I would have had myself hospitalized for two years ago.
Many of the people around me go "eh, just check your code for security" and "I tried coding in ChatGPT, i had it output some puny script, it's not that great".
In return I had Claude (free tier) make a PDF for them on uses, chances, risks, legal framework and integration with other AI and services for them, nicely formated, from one prompt. It seems 100 percent factually correct and Claude fixed a bug in the PDF generation code it pulled off of the web from the same prompt to complete the task.
I also explained to them why especially the library pool for Python and JavaScript enables Claude to write stuff that is rather impressive, and that while not fully scalable (yet), it might be "good enough" for 90 percent of the tasks people want done these days.
I suddenly find myself berating people on government forums, where some people from the national IT security advisory body are part of the (mostly silent) audience, to wake up in some way and consider what it means. Yet our national approach to security is mostly still "Vibe coding is a toy and a party trick, that will blow over eventually, get a code audit or follow some security check lists."
Meanwhile I believe that in two years, most of GitHub will be written by non coding hobbyists like my friends.
And having seen how insanely laissez faire some commercial software folks treat security and product service for extremely pricy products, maybe DIY vibe coded stuff does not even look bad in comparison.
While some of 1000s of people around me doing the "real world" work around me can't wait to give agency to the AI, many others here, including many people in charge, still seem blissfully ignorant. Or want to be.
Ultimately, I only know one thing for certain: Society is currently heading full yolo into this, and systemically, that might be the only way because that is the true nature of AI.
They say people don't understand the exponential function. This is true.
But most people also don't seem to understand the implications of this new approach to exponential pattern recognition and reassembly, that operates on the microsecond scale, and with an insane pool of information at its disposal. It will probably never make NEW stuff, but it will assemble old stuff so fast and complete it will still seem indistinguishable from magic.
Society is in for a wild ride.