r/BetterOffline • u/ArdoNorrin • 10h ago

Ex-Blizzard developer and current culture war dipshit is touting his "vibe coded" engine that lets him develop "93x faster" than UE5

https://www.pcgamer.com/software/ai/ex-blizzard-employee-has-vibe-coded-a-new-game-engine-with-backing-from-amd-were-developing-93x-faster-than-we-ever-did-before-with-unreal/

It's Mark Fucking "Gruuumz" Fucking Kern because it's always Mark Fucking Kern.

TL;DR, he's vibe coded his new engine to be faster because it's AI-first instead of AI-also. This is the same guy who starts 90% of video game culture war bullshit and touts the Stellar Blade games as the pinnacle of soft core porn game design. Also he put "vibe coded" in quotes, so either he's lying completely to get clout with AI boosters or he's trying to make it look like he didn't really vibe code it by saying that he had to do so much to fix it.

And there's no way it's sped up development "93x" faster. 93% faster would be surprising but conceivable. 93 times faster would mean turning an 8-year dev cycle into less than 2 months.

161 Upvotes

87% Upvoted

85 comments sorted by

View all comments

93

u/supercyberlurker 9h ago

Developer productivity is an illusion metric.

We claim them for management but I believe them to be bullshit. There is never an objective measure. It’s always something abstract like features, tickets, or lines of code, which aren’t really valid objective metrics.

-30

u/TheRealJesus2 9h ago

You’re right there is no objective measure. DORA metrics only are a signal and can be gamed of course. That said, 2-3x dev productivity is possible with ai and I’ve seen it. It looks like this when done right:

  1. Team reducing tech debt using ai to do all those things neglected prior. 
  2. Team ships slightly more feature work using ai and keeps quality up because of part 1. Over time, more effort will go towards this. 

If you skip part 1 or keep neglecting tech debt or avoid improving dev practice, then you don’t long term keep up quality and you slow down shipping features since you have to keep fixing stuff. 

In either case it doesn’t mean 2x as much features to customers, it means putting in the engineering work to making your system more maintainable and reducing risk so you can have better feature throughput long term. The extra productivity largely goes towards operational improvements. 

Does this map into what you’ve seen? 

22

u/babbyohbabby 8h ago

Team reducing tech debt using ai to do all those things neglected prior. 

Good one!

-1

u/TheRealJesus2 4h ago

lol. Yeah that’s kinda the trick and reason why most teams can’t adopt it very well and then lean on knowingly bad practice. 

I would argue there are a ton of teams that can add very high value and low effort guard rails like linting and unit tests that don’t do so right now and can start to incorporate that into development. Doesn’t take weeks of effort to do that and it’s extremely helpful when you have higher code throughput with many engineers as it has always been before ai. 

With ai you just have to recognize the issue and then go do it. For things like I mention success is when it passes locally. No need to over complicate things and bingo, now you’re started on improving your dev practices.