David Busch (@HappySlice) header
David Busch (@HappySlice) profile picture

VR developer. These tweets are satire and do not necessarily reflect the opinions of myself.

Austin, TX
Joined March 2009
Photo by David Busch (@HappySlice)Photo by David Busch (@HappySlice)Photo by David Busch (@HappySlice)Photo by David Busch (@HappySlice)Photo by David Busch (@HappySlice)
David Busch retweeted
Hyper Visor HAS OFFICIALLY LAUNCHED! 🕶️ Slip on the shades. 👀See beyond your reality. 💥Blast your way to victory. This new original reality-bending arcade blaster is available now for $1.99 on XREAL Aura and Android XR: tr.ee/o1XH4D
1
8
3
27
3,815
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month. I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
570
1,326
652
13,679
2,045,374
David Busch retweeted
"Hunger beats tenure." Great write-up by Felix on why his team at Anthropic dropped coding interviews: newer engineers are flying past stronger, more tenured coders. Execution isn't expensive anymore. Inside a company, the signal is picking an idea that moves the business and prototyping it. Outside, it's a portfolio of small prototypes. Both should show off your taste and judgment. Claude Code Desktop started as a weekend prototype by two newer engineers.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month. I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
67
26
7
585
40,148
snail from Dungeons of Blood and Dream
10
30
2
497
5,726
David Busch retweeted
When learning shaders most tend to overcomplicate common practices like noise or color corrections. Here are 5 common noob mistakes:
7
95
1
1,079
61,126
David Busch retweeted
Agents write code "much better on average at scale" is right. The "at scale" part comes from verification. Agents make checking cheap. The stuff that made "Good Code" expensive (tests, benchmarks, specs, real e2e runs) is now a cheap thing you can ask an agent for. You can improve the checks. So our work is less "review every line" and more "build loops the agent can run itself". Give the agent a way to verify the work. That loop is where quality comes from. And make taste compound. When the agent gets something wrong, write it down (shared config, a hook, a test) so it doesn't happen twice. A human still owns what ships but now they're reviewing evidence and not just diffs.
codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software. swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go. admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?". well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is: • correct • bug free • fast and cost efficient to run it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start. but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing! agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale. the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree
90
55
17
668
59,546
David Busch retweeted
Art by the legendary French artist Philippe ‘Caza’ Cazaumayou
8
301
5
2,863
38,105
David Busch retweeted
Hot take: good teams have always had this problem. Great teams learn to solve it. Back in the days before AI, I would regularly spend weekends on yolo PRs changing thousands of lines of code. The goal wasn’t to merge. I just wanted to get a feel for what the changes would look like. Tons of reasons for this: - exploring architecture - figuring out blast radius of changes - getting early product feedback - feeling out different flows, APIs etc The key to making this work: assume all PRs will be closed, not merged. The PR you merge can be built differently than the branch you used to explore. It often should be. I’d go as far as to say that all PRs filled by non-maintainers should be closed by default, meant only as references for future humans and agents
Every startup would secretly admit how much of a pain the "slop grenade" problem is. Bold of Tobi to say it out loud. Everyone else is dealing with the same thing: balancing output volume, quality, and confusion about who's responsible for what comes out. Keep holding people accountable for their actual work. The quality vs productivity pressure works itself out when accountability is clear.
84
24
8
1,181
179,417
David Busch retweeted
I used GPT-6 Astra to break an unsolved cipher to one of Napoleon's generals that had gone unread for 217 years. What makes this impressive isn't actually the codebreaking, but that Astra completed the entire multi-modal workflow in ~6 hours from a single image and goal. 1/6🧵
317
1,670
387
11,977
5,417,134
Chase gave a great talk about performance and optimization in Unity at the Austin Unity meetup and it’s always a pleasure to chat with Chase about VR dev and whatever else. He would be a great addition to any team!
Unfortunately I was apart of this layoff and am looking for what's next very soon! Lead / Senior Tech Artist or Senior Unity Developer— remote or Austin. Walkabout Mini Golf was my home for 4 years, now I'm ready for the next set of problems. portfolio → chaseshields.com intros welcome 🙏
1
2
320
David Busch retweeted
Announcing Gemini 4 Argon, our new frontier model. Argon is built to sustain deep reasoning across complex, long-horizon workflows and delivers frontier performance in complex workflows across real-world software engineering, enterprise knowledge work like legal and finance, and cybersecurity defense. We’re also expanding the model’s output token limit to an industry-leading 1M tokens. Argon is currently rolling out to a set of trusted cyber defenders in the Fairwind Program, with broader availability as soon as possible.
565
1,182
742
14,877
1,085,736
Higher effort passion projects are finally making the rounds on X instead of “look at my oneshot” posts. Turns out games are still hard to make and good ones take lots of time and effort.
gamer engineers remixing elden ring into minecraft, call of duty into skate 3, porting melee to pc, putting halo ce in a browser, and unleashing a StarCraft bot named Pluto on Korea has done more positive pr for AI in 2 weeks than the AI labs/industry has for itself in 2 years
1
70
I put the entire of game minecraft into elden ring as mod. its runs on Mac.
1,739
23,589
2,623
307,210
23,784,359
I was hoping Blender MCP would increase access to geo nodes. I’ve made a few throw away ones, but rarely if ever do you see someone post a node setup made via agents, let alone one as close to good as something @MatterCg or @erindale_xyz can cook.
2
26
4,405
David Busch retweeted
why i'm sad about vr (and why there's still hope) youtu.be/QjWgVKV4WKI
48
17
24
291
91,894
David Busch retweeted
One of our MOST REQUESTED modes ever is coming to Dimensional Double Shift! 🎉🤖 Get your first look at Single Player 👇
4
8
4
44
4,304
David Busch retweeted
🎉🎉 BIG NEWS EVERYONE! 🎉🎉 Owlchemy VR Games are COMING TO STEAM FRAME! Get ready to [JOB], [VACATION], school and shift! ☕Job Simulator- Now! 🌴Vacation Simulator - Now! 🌭Dimensional Double Shift - Soon! 💗Cosmonious High - Soon! 🧵⬇️
7
13
1
55
5,508
AI researchers share monthly P(doom) stagger charts, to see who’s serious & who’s an alarmist.
Replying to @PessimistsArc
Right. Dario was already claiming that GPT2 was too dangerous to open source back in 2019. I made fun of them then. Everyone should make fun of them now.
1
83
David Busch retweeted
I hope the proposals by frontier labs to pace AI research stem from a genuine concern for safety and a recognition of the potential risks posed by future models, rather than a strategic effort to consolidate power and permanently solidify the market dominance of a few top players. If these efforts are genuine, then oversight must take a more democratic and accountable form, with both national and international components, similar to the Nuclear Regulatory Commission in the US and the International Atomic Energy Agency internationally. If there is only one organization responsible for safety monitoring, and it happens to be staffed by the same people as the frontier labs, and it is perfectly aligned with them both by incentives and by ideology, then it would be indistinguishable from letting frontier labs self-regulate and self-certify their own safety standards. Two potential warning signs of regulatory capture to watch out for: 1. Calls to ban open-source AI. Open-source development currently serves as the only real counterweight to the dominance of frontier labs. 2. Attempts to hinder non-frontier research. Models that are one or two generations behind the frontier -- whose level of capability has already been deployed at scale -- are empirically known not to pose safety risks. As long as we don't see 1 & 2, and we see real international coordination efforts, then I will optimistically believe that the proposals are benevolent.
118
252
44
1,527
136,329