Jim Cowart (@ifandelse) header
Jim Cowart (@ifandelse) profile picture

https://teapaw.org/t.co/qGrCURk66h | Author of machina & postal | Powerfully dumb | Planning next moves...

Chattanooga, TN
Joined July 2009
Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)Photo by Jim Cowart (@ifandelse)
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this" if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
184
362
76
3,733
167,457
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
11
7
5
62
9,909
Jim Cowart retweeted
you have to hand it to the GitHub team this is incredible
48
51
30
1,277
91,039
People who are serious about building software train their own brains.
5
1
35
1,632
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.
499
1,887
394
15,222
1,625,117
Jim Cowart retweeted
There's no way we get out of 2026 without OpenAI making similar moves to Anthro today. You simply cannot have extremely limited compute + effectively unlimited demand and expect tokens to stay subsidized, no matter how valuable it is to have the affinity of the once subsidized.
9
1
25
4,703
Jim Cowart retweeted
Replying to @IntCyberDigest
POV: you are downloading packages in 2026
4
98
8
1,000
82,876
don’t fall for the trap of waterfall development - our industry learned this lesson two decades ago. you can’t know and plan everything upfront - neither can agents.
9
31
10
335
102,443
You know another name for Agents? Workers.
7
4
1
113
10,843
Jim Cowart retweeted
this is so accurate 😂
256
2,355
224
22,738
1,029,795
Jim Cowart retweeted
AI bois be like:
120
525
61
7,314
298,666
Jim Cowart retweeted
The core idea of Lord of the Rings is kinda hilarious. You're a 23 year old junior dev in some Ohio suburb. There's a little npm package in your grandpa's node_modules with a hardcoded admin token that has root access to every server on the internet. Now it's on you to SSH into the only air-gapped machine in the world in Arizona before AWS finds the token, force-pushes to main, and takes down your whole company.
2
10
93
18,628
Society “you’re too old” Artemis 2 Crew: “hold my beer”
481
8,424
600
57,501
1,401,442
This is Algebrica. A mathematical knowledge base I’ve been building for 2.5 years. 215+ entries, carefully written and structured. 400k+ views over this time. Not much in absolute terms, but meaningful to me. No ads. No courses to sell. No gamification. No distractions. Just essential pages, aiming to explain mathematics as clearly as possible, for a university-level audience. Built simply for the pleasure of sharing knowledge. Content licensed under Creative Commons (BY-NC). Best experienced on desktop. If it helps even a few people understand something better, it’s worth it.
182
770
57
5,363
232,056
I'm so nervous!! 🌔 #ArtemisII #NASA #Moon
234
24,508
1,232
118,925
1,506,215
Jim Cowart retweeted
The Artemis II crew named a lunar crater after Commander Reid Wiseman's late wife, Carroll. What a beautiful and touching moment. I'm not crying, you're crying 🤧
395
6,147
1,026
41,223
2,792,752
Replying to @atmoio
AI won’t take jobs, it’ll reshape how jobs are done. It’s an assembly line.
1
1
2
186
Literally the perfect meme
JUST IN: Artemis II crew experiences issues with Microsoft Outlook on their way to the Moon, asks ground crew for assistance.
29
2,196
18
22,925
420,476
Jim Cowart retweeted
Socket is free for open source maintainers. We're launching the @SocketSecurity for Open Source program -- any open source maintainer can get a free Team plan to protect their project from supply chain attacks. Open source is critical infrastructure. Millions of companies depend on packages maintained by small teams and volunteers. These maintainers are high-value targets but rarely have access to enterprise security tooling. That's wrong. We want to fix it. What you get: ✅ Full dependency scanning across your project ✅ Real-time alerts for malicious packages in your dependency tree ✅ Check every PR to make sure no malicious dependencies are added -- including PRs from outside contributors If you maintain an open source project, send an email to support[at]socket[dot]dev and we'll get you set up!
15
33
6
126
24,360
Jim Cowart retweeted
This is the shot you can’t get from the press site. This camera was sitting a few football fields from the SLS rocket at Pad 39B for days before launch, baking in the Florida sun, surviving rain, humidity, and whatever else the Cape threw at it. No photographer behind the viewfinder. Just a camera, a sound trigger, and a bet. The way pad remotes work: you set your camera up days in advance, dial in your composition, lock everything down, and walk away. You don’t touch it again until after the launch. The shutter fires on sound activation with a @MiopsTrigger smart+ trigger. With SLS, the four RS-25 engines ignite six seconds before the solid rocket boosters, so the camera is already firing before the vehicle even leaves the pad. You get home, pull the card, and find out if you nailed it or if a bird landed on your lens two days ago and left your a present and you got 400 photos of soemthing crappy. There’s no formula for protecting your gear this close. Some photographers build wooden boxes with doors that pop open. Some use plastic bags and tape. Some do plastic or metal barn door rigs on hinges. I tend to leave mine open just in plastic rain covers because boxes limit my composition and setup time, but that means your cameras are more exposed to the elements and whatever energy and debris comes off the pad. You’re basically gambling a camera body every time you set one. That’s what I love about this genre. There’s no playbook. You make it up as you go. Every time is an adventure. 📸 credit: me for @SuperclusterHQ - Artemis II pad remote | ~1,000 ft from Pad 39B | Kennedy Space Center
738
5,465
350
46,758
1,208,091