
Founder, Investor, Engineer @RoushTech | Building @RaptifyApp (and a ton others). Software, virtualization, storage, networking, VOIP & more.
Soddy Daisy, TN
Joined October 2011
- Tweets3.1K
- Following174
- Followers213
- Likes3.1K
Look, I agree developers hand-wrote a lot of slop before, but them being slow was a massive fucking feature.
I've written up a stupid amount of incidents in the past 12 months, not from "oh we're being hacked" but "engineers are writing code beyond their own knowledge, and violating regulations or creating undue liability"
On one hand, it's good money, on the other, I wouldn't be surprised if within the next 12 months a platform I touch is going to cause a catastrophic business-ending issue over the lack of due diligence (which isn't good money when they stop paying us).
And with more people learning less, this gap is just going to widen.
13
Watched the industry feel this was about TOTP, until the wave of lost devices and lock-in came in.
Security shouldn't be able being locked in with the vendor, and there being a base level of responsibility, and the entire industry shouldn't have to suffer to protect those that are going to be the most reckless.
Passkeys should NOT be exportable.
It defeats half their purpose.
How long until we see malicious sites that trick people into entering commands that dump and steal all their passkeys?
18
I'm appreciating that managers using Claude has resulted in things I typically wouldn't propose because instead of a 30m task it's going to be like 6-12 hours getting approved because "Claude said we can do it this way"
Yes, and I have to go deploy a whole new stack of services to support that....
But hey you recommended it. 🫡 Billable hours goes brrrrrrr
13
I don't even know how to estimate work anymore
There are some tasks that with an llm I can have done in short order and be good to go
There are some other tasks randomly not derived from their difficulty or the complexity of the code required or the quality of the documentation that will require a significant amount more of my attention
In pre-AI programming a significant amount of our labor was spent with the actual implementation and so a smaller percentage of the work fell into this unknown category
Now since implementation and prototyping is extraordinarily rapid and can be done concurrently with other work the costs come from issues that are harder to estimate
The kicker is at the llms are part of the problem, if I ask Claude the estimate work I will take that number and cut it in half and still likely be significantly under budget like 80 to 90% of the time which is good from a financial standpoint but I want my estimates accurate
2
1
24
I just spent the past like 30 minutes begging Fable 5.2 High to not clobber the fuck out of a feature and make it 10x worse.
Procyon has a support portal, it's very new, it's been working pretty decently but has a lot of little rough edges as we've used it. I've wanted to revisit it because too much of the design revolves around how the core system works (basically the issue Jira had with Service Desk).
Let's start back from the basics
And then I've been like "no Claude that's not how that works"
The most appalling one to me was me correcting it on how the security model works, yikes! It was going to suggest a massive fucking mess of data because it somehow got the security model wrong and wanted every customer to have its own support project (!!!!) ughhh
I'll be using it more tomorrow, but meh.
3
109
As someone that has had to deal with fixing, or using a significant number of vibe coded apps:
Holy hell this is one of the stupidest fucking takes in AI.
The struggle isn't even that apps are vibe coded, is that vibe coders *really* don't want to be tied down to maintaining their apps for the next 5-10 years. All the sudden all the bugs and issues you find, they're nowhere to be seen and if you're lucky it's open source and you can start to unfuck it (but it's easier to just build your own generally to a better level of quality)
They want to shit out 20 apps a month, then get upset when they're expect to not, and actually maintain shit.
52
"You only hate it because you know it's AI"
Man that "having knowledge affects your capital decisions to vote with your wallet" part of capitalism really sucks doesn't it?
Nah fam, that's their prerogative as consumers, they're not wrong, that's how capitalism works, deal.
19
Nuanced opinion time:
I get people not wanting AI in game development, this usually means a developer, with practically no creative bone in their body, is vibbing a bunch of shit and wants to sell their game full-priced.
This sucks because it eliminates the person who's specialty is to do creative artistic work, a lot of the time the design suffers from it and we're expected to pretend the game took just as much effort (don't @ me)
At the same time, I'm fine with creatives using AI to do work, to put care into things, to do better things than they can achieve themselves through the amount of labor required -- exactly where we see AI in software being useful, make *better* products using the same labor, not cut corners and be cheap (yeah big ask in a shitty late-stage capitalist hellscape that forgot the social contract that made capitalism at least work better).
The reason why the AI tools suck for creatives right now is they were built by tech bros who have a chip on their shoulder for the very existence of creatives. It left a sour taste in the mouths of many and rightfully so, and I'll never fault them for that -- it's been massive bullshit the whole way.
I want to see more AI tools build for creatives, by creatives, and I want to see where that takes us. I want to see a creative say "this would enable me to do this big thing I've always wanted to do", not someone that never picked up a pencil saying he's God's gift to art, he just couldn't get around that pesky step of learning a goddamned thing about it.
With programming we've learned (generally) that someone who doesn't know shit vibe-coding is a nightmare, causes tons of issues and produces a significantly inferior result, art and assets are the same.
Does this mean we shouldn't use AI at all? No, we should use it carefully, thoughtfully and with earnest care.
And the slop, rightfully so, should be shunned.
I think the Big Walk is in a good spot here, it gave us a less buggy game, and they had a dedicated staff already putting love and care into it.
That's all I ask.
Big Walk used AI in 'the final stretch' of development, kicking off intense awards debate:
aftermath.site/big-walk-ai-i…
Readers added context they thought people might want to know
House House used LLMs sparingly near the end of Big Walk's development, mainly to fix bugs in third-party code. They estimate well under 0.1% of the game's code was affected, and they didn't use generative AI elsewhere.
bigwalk.game/faq/#ai
pcgamer.com/games/puzzle/b…
49
Microsoft, I beg of you, ship a fucking improvement for once.
Here's your first look at Microsoft's new WinUI 3 Registry Editor, but it's a developer sample preview, so it may not ship on Windows 11 anytime soon.
Windows Latest found the app inside Microsoft's open-source Reactor repository, and I built it myself on Windows 11.
It keeps the familiar two-pane layout but replaces the cramped Windows 95-era interface with native WinUI 3 controls, a dark-mode-ready design, and smoother animations.
It can read, create, rename, and delete registry keys, edit values, and search the registry. It even uses Mica, with no Electron or WebView2 involved.
There are still unfinished features, and Microsoft hasn't announced plans to replace regedit.exe.
This is a developer sample made by Microsoft, not an official Windows 11 replacement.
1
99
If I block everyone with an .ai domain I bet you I'll stop seeing people going "instead of running my business I'm replacing Zoom to save $19/mo"
29
I like how I'm on like week 6 of "guy doesn't need our help he's vibe coding now" and I'm 6 weeks into getting daily alerts he has malware on his server from his provider.
JFC.
3
2
191
Meat proxy devs go right into the garbage at my company.
I've been endlessly fixing meat proxy mistakes, critical ones, corrupted data, crashes, downtime, breaking UX, security violations.
If I have to do all the heavy lifting of preventing that from shipping, I don't need an engineer, I can save a salary.
It's stressful and miserable.
A hot take: jobs where you're just chatting with Claude or Codex to do your work may feel very comfortable right now and that's the trap, I'd not stay in that place if it was me, we're likely living a temporary phase where engineers are paid to act like a meat proxy and it will soon not being possible anymore
Very bad time for extremely introverted ppl that don't wanna talk to users or upskill in product
2
135
Because I just watched it corrupt a NextCloud install doing stupid shit by blindly firing PHP to do basic tasks the CLI supports
Because I watched it take down a SaaS doing a heavy lift migration at fucking boot time
Because I watched it break a 10m process into a 40 HOUR long process because it effectively wrote a query backwards.
Because while it can do some amazing things, it'll do the WORST FUCKING THINGS EVER if not kept an eye on.
4
204
I mean this is how business has always been though, 5 years ago your app sucked because you couldn't bring a product to market with uber 1337 skills engineering alone, and you got beat out by some team with some VC funding fucking around and slopping it together.
Product development is about a ton more than just nerding yourself todeath in a closet on a laptop.
Imagine spending 15 years becoming an exceptional software engineer.
Then some guy with zero programming experience builds an app that makes more money than your annual salary using Claude.
And people tell you to stop being bitter.
23


















