iiinova — where your digital self keeps evolving

It's engineers, and specifically leadership, pushing absurd demands onto Gen AI without any threshold for quality or thinking through how to apply quality to the product under development. 🧵 4/6

100

It isn't going to get fixed though, it'll eventually just get thrown away. Nobody is going to comb throw the pixels with a comb and fix that trash. The other wild truth is, it isn't really the Gen AI writing "bad code". 🧵 3/6

100

It's so wildly error prone, nobody can really manage what is being done, it's just a wild west clusterfuck of code getting shoved into repos. Some people also chuckle and keep saying eventually that's going to cause a boom for people fixing it. 🧵 2/6

100

Gotta admit something. I just kind of got a non-stop low key chuckle at how much teams are integrating Gen AI but then they're just doing the same maddening workflows and pull requests and just trying to do "parts" of it faster. 🧵 1/6

100

What do you think of this site? What would you want added to it (cuz I'm wanting to add things to it) — real-time arrivals, better route/transfer info, service alerts, something else entirely? Lay it on me. www.dashingarrivals.com 🧵 2/2

000

Do you use transit in the Seattle metro area? Tacoma, Everett, Bellevue, Redmond, Kirkland, Bainbridge, Bremerton, Anacortes, etc... Link/Sounder/ST Express, Pierce Transit, Community Transit, King County Metro, Kitsap Transit, washington state ferries, whatever your daily combo looks like. 🧵 1/2

100

Happy to get ya coffee, beer, or whatever beverage of choice you'd like! 🍻 🧵 3/3

000

Would you mind taking ~2-5 minutes to tell me about it? Bonus points if you're in the Seattle or Portland area, secondary bonus points if you're in San Francisco, San Jose or - ya know - the "Bay" area. Special bonus point if you're in Spokane. Hit me up, let's discuss. 🧵 2/3

110

Do you use .NET? Do you have .NET Framework projects of yesteryear that you're still working on? Do you still have VB.NET or VB6 or even COBOL.NET projects? What older, possibly ripe for migration, Microsoft stack developed solutions do you have? 🧵 1/3

100

So do you wait for the market to force their hand, do you route around them and build without their buy-in, or do you keep trying to open a door that was never unlocked from the inside? 🧵 4/4

000

They're not malicious, just blind to their own blind spot, and that's the harder problem to solve. You can't out-argue someone who thinks the debate is already settled in their favor. 🧵 3/4

100

You see it everywhere: the team that still insists on manual spreadsheets while the rest of the industry automates, the exec who dismisses new tools as "just a fad" for the third cycle running, the colleague who confuses skepticism with wisdom and calls it principle. 🧵 2/4

100

Adron @adron.bsky.social · 29/09/2026

When the laggards and luddites don't realize they're the laggards and luddites, and the minds of those laggards and luddites aren't open enough to even learn that they are, what is the path forward with the likes of that resistance? 🧵 1/4

100

Transport Fever 3 released! It has begun!

001

PRs made sense when writing code was the bottleneck. It isn't anymore so maybe let's stop pretending our process should look the same? But hey, throw a proposal this way I'm open to alternate solutions to the current mess. 🧵 7/7

400

Treat code as disposable and regenerable — if an AI wrote it in 10 minutes, the fix is often just regenerating it, not painstakingly patching a diff The goal isn't less rigor, it's rigor that matches the actual speed and nature of how code gets made now. 🧵 6/7

110

Merge to main by default, gate releases instead of commits — ship fast, catch issues at the release boundary with real monitoring 3. Reserve human review for architecture decisions and irreversible changes, not routine feature work 4. 🧵 5/7

200

optimizing for a review ritual, not for actual correctness or safety What to do instead: 1. Replace pre-merge review with continuous, automated verification — tests, type checks, behavior diffs, and LLM-based reviewers that actually read every line (they can, we can't) 2. 🧵 4/7

100

Why it's broken: - Reviewers are rubber-stamping 400-line (or 1600-line) AI diffs because there's no time to actually understand them - The PR queue has become a bottleneck that punishes speed instead of enabling it - "LGTM" now means "I trust the model" not "I read this code" - We're 🧵 3/7

100

Now half our diffs are LLM-generated, shipped in minutes, and iterated on faster than any reviewer can meaningfully read them. We're running 2024 process on 2026 output in a world every month is the equivalent of a decade of the 90s or 00s. 🧵 2/7

100

Quick proposal: it's time to give up pull requests. PRs were built for a world where a human wrote code slowly, thought hard about every line, and needed a review gate before merge. That world's gone. 🧵 1/7

101

Now I'm delving into some other work and studies, all while taking care of errands via transit - and bike! It's a great pairing, love it! Thx Seattle for being awesome like this! 🧵 7/7

100

Then I needed to do some banking, also something that is relative good to do with a quick tether connection for internet access. Boom, got that done too! All that and I was enjoying the beautiful Lake Washington Bridge crossing al the while. 🧵 6/7

100

Super easy, wasn't in anybody's way, done! Then I sat and adjust my shoe clips with the other wrench: one shoe finished and then the next, done! Two tasks done without twiddling about having it consume other activities, I used trip time instead. 🧵 5/7

100

I boarded and then pulled out two specific wrenches. One for my bike seat height, and one of the clips on my shoes. Both needed adjusted. So I put my bike on the rack once I boarded the 2 line to Redmond and adjusted the seat right there on the rack. 🧵 4/7

100

But then, today there was a third thing that reminded me how useful transit can be. Beyond the obvious trip one takes. I needed to do two things and instead of standing around working on them at home, I rode down to Westlake to get on Link. 🧵 3/7

100

bring it along with you, it dramatically increases the distance transit can take you, because then you're not dependent on Uber or walking or whatever other such nonsense when you arrive somewhere. But starting out it gives you more options too. 🧵 2/7

100

Got on the Link to cross the lake today and a few things came up that just reminded me why I love two things: 1. Pairing transit with bikes. 2. Transit. When you pair your bike, i.e. 🧵 1/7

100

Two factory terminologies, one pipeline: sense → interpret → predict → act. Of the two which sounds more enterprisey + businessy + logical to you? 🧵 3/3

200

Vision Cognition Plant (VCP) — the sister facility, converting perception into understanding: seeing not just what is, but what it means and where it's headed. A pivotal way to get your software built with integrity, consistency, speed, and quality. 🧵 2/3

100

Help me out here if you would, I've got a question for you! Prescient Cerebration Mill (PCM) — a factory of foresight, grinding raw signal into forecasts, patterns, and proactive strategy to get your software built with integrity, consistency, speed, and quality. 🧵 1/3

100

He disingenuously leaves out so much information in his “viewpoints” too. It makes me curious what his intent and incentives are. Not that I spend too much time on the thought, cuz for how wrong he is and skewed his viewpoint, it sure seems he’s a bought and paid for shill of some sort.

100

What is this “run over” bit? Were you paying on the pavement? Shouldn’t you stand or walk in it? No way a bicycle ride is going to”over” you unless you’re laying down, and even then it’d still be more of a collision or crash, it’d be unlikely they’d make it “over” you.

010

However his doubling down on being wrong is oddly entertaining from an academic perspective, and odd that anybody continues to listen to him.

000