Pinned Tweet
Available for hire. 🤓
Not going to list ten buzzwords or claim I'm passionate about synergy.
I ❤️ building things & have a long history of shipping working software = building teams.
node/web/full stack. Remote or hybrid. DMs are open.
Please. I beg you. Don't be a meat proxy.
If you find yourself just copying what your agent said/asked and dumping it without critical thought into Slack, Teams, or whatever.... get help.
Jim Cowart retweeted
You can’t claim “the models are good enough that I don’t have to read the code”. Because if you’re not reading the code, then you can’t possibly know how much slop is getting in. We go live to @0xblacklight and @vaibcode for the scoop
New Term: Finite Slop Machine
It's a kind of 'implicit' state machine that emerges across enough clanker output. It "looks" formal b/c of type defs and convincing markdown walls of text.
But it's one state version conflict away from silently dropping a critical op.
On one hand my agent is indispensably helping me w/ researching complex OTA hotel interactions at a rate impossible for me before...
On the other, I'm learning new languages and tools without generative assistance until I hit decent proficiency...
Feels like a sweet spot.
So help me…if I hear “that’s Kubernetes for a cron job” one more time…some agent is gonna feel the blast radius 🤪
It's been an insanely rough couple of weeks with agents. I've lost tons of time preventing them from making entire messes of multiple code bases this week alone.
Then I open my timeline and see a bunch of "I grabbed a beer while chatting w/my agent, and by the time I put the kids to bed, this impossible app that would've taken me weeks was done!".
SMH
Claude: "No /bro skill installed, but I can compile to bro natively"
...cringe-fest ensues...
Me: "look in your skill folder and try again"
Claude: "Ah. So /bro means 'talk like a person,' not 'talk like Point Break.' My bad"
🤦♂️
The long tail of AI: a short story.
Two days ago my agent (Opus) completed part 4 of a 7-step refactor of a travel shopping cart system. It reported a bug in one of our deps & explained how it had worked around the issue. it gave me a concise, portable summary of the issue.
I could've said "sure, whatever" & rubber-stamped the first Opus concern. Or I could've sensed the rabbit hole with Fable and said "Fine, do your suggestion". Either would have resulted in a weakened foundation for any future change.




