Reshen

Optimism, kindness, art, humor, engineering. Aspiring indie game developer. Ex-Principal Engineer @AWS

[Reshen @Reshen817]

@valigo SGPU is the way! Its so incredibly nice to just use the same struct in both jai and slang shaders, also just placing everything into arenas is superb.

[Erin Catto @erin_catto]

I’m happy to announce the release of a new open source 3D physics engine called Box3D. I’ve been working on this project for a few years now, but it represents over 20 years of experience writing physics engines for games. Read more here: https://t.co/2d9aVuUsxj

[Reshen @Reshen817]

@falconerd I've been using a minimal vulkan library that directly implemeted the ideas in @SebAaltonen's terrific post (No Graphics API) and its been such a joy. It's a radically simple interface yet still retains all of the power+validations provided by vulkan. Did you go fully bindless?

[Reshen @Reshen817]

@topotoylabs Looks awesome! The stacked bar chart in the bottom left showing (pipeline stage costs?) -- is that your own UI or a library? Thanks!

[Reshen @Reshen817]

@rfleury @LubaRaphael tiny cc or zig cc might be worth trying. The built in zig caching system was especially nice at reducing repeated compilations

[Reshen @Reshen817]

@AnalogDreamDev @MrDrElliot You could consider how Jai and Fred editor do it. Closed source, long alpha periods only accessible via private discords. One huge upside is being able to directly speak with users/gather feedback and it let's you manage out the terrible folks.

[Reshen @Reshen817]

@JussiKemppainen Really like how responsive it is, and the zoomed out layout is terrific. Is this another side project of yours / is it available somewhere?

[Ben Visness @its_bvisness]

The venue is just about set up for the Handmade Network Expo tomorrow! I look forward to seeing everyone and showing off lots of cool Handmade software :)

[Reshen @Reshen817]

@valigo Jai video was great! Be funny if you did one calling out all the AI bullshit

[Reshen @Reshen817]

@henningsanden Replaced original game soundtrack is also terrific https://t.co/u672lUHThs

[Mitchell Hashimoto @mitchellh]

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.

[Reshen @Reshen817]

@JanOrszulik Both SFX and vfx are so good, in this post and the previous one.

[Тsфdiиg @tsoding]

It's been almost 5 years. I'm still waiting for the copyright laundering scheme to somehow magically cure cancer.

[Nic Barker @nicbarkeragain]

To be a little less vague, I suspect that we're likely (not certain, but likely) to be entering into a period of unprecedented software degradation, and we're going to be seeing an increasing frequency of outages like this across many high profile products.

But IMO the cause is actually not just the-one-thing-that-everyone-is-always-talking-about, it's a number of things that have all been bubbling away at just below critical levels for a long time. Some of the things off the top of my head:

- Poorly designed / optimised software has been getting a free ride on hardware improvements pretty much since the invention of the computer. That chapter is now coming to an end, and will only be worsened by the enormous industry-wide pivot to producing & innovating on AI specific hardware, rather than general purpose CPUs etc.
- The ZIRP era created a temporary suspension of reality in our industry, and now that it's ended we need to deal with the hangover. Companies that spent years making no profit, paying extravagant compensation to employees / shareholders and giving away server time for free are now pivoting into extraction mode, which is putting further pressure on their low quality software. QA is being laid off, hardware budgets are being reduced, timelines for shipping features are becoming more aggressive, etc.
- The enormous amount of free money incentivised too many new people to join the industry too quickly. This has led to an abundance of poor quality education programs (bootcamps, uncertified colleges etc) and an influx of people into the industry who frankly aren't interested in programming. If you compared the average person in the industry now to 20 years ago, I suspect the difference in motivations would be stark. I'm not saying it's these people's fault necessarily, it's simply an inevitable result of the absurd compensation / performance expectations ratio that our industry has enjoyed for the last 15+ years. Working for a tech company has also become socially prestigious, which further adds to the problem.
- Because computer programming was once an incredibly niche area of interest, many of our fundamental systems are built on trust. We're now starting to see that if systems like open source, public supply chain, discussion spaces, education etc become flooded with bad actors, we have no real mechanisms to deal with them.
- Our hiring / recruitment pipeline has totally misaligned incentives. Even before the AI resume / AI HR-filtering arms race disaster that we're experiencing now, the widespread adoption of the leetcode style interviews IMO selected for a very narrow personality type, and filtered candidates that would have made great contributions to the industry long term.
- The pivot from purchasing long term stable releases of software, to paying a subscription for constantly updating software has done huge damage to software quality as a whole. Companies have lost their incentive to get their software "right" because they can just "fix it later", and for the consumer - you can't just go back to the version of github that still works because the new one has problems.

This was all happening well before AI entered the picture. I won't belabor the point because there has been endless discussion about it. But to me personally, there are two additional and deeply worrying problems with AI code generation.
- It's undeniable at this point that it negatively affects the people who use it. It stops juniors from getting better, and it burns seniors out and makes them hate their jobs. Like it or not, humans are still the core of this industry, and I don't see this ending well.
- It's completely unfit for purpose in the most important, high-stakes situations. One of the reasons that we excuse all the small errors it makes, is because it's low effort to type "do it again and fix this bug". That kind of thing doesn't fly when you only get one attempt because a mistake results in data loss or an outage. The damage is done.

All the above has led to a silent exodus of many of our most experienced and impactful people. There are so many amazing programmers who made enough through stock options / compensation that they didn't need to work anymore, and were only doing it because they enjoyed it. Many of these people have just quit the industry and switched to doing hobby projects in the last 5 years. These are the types of people who have the experience and foresight to prevent the types of outages that we're seeing at github today.

It's very easy to assume that the proverbial straw that broke the camel's back is entirely to blame here. But I think it's a reckoning that has been on the horizon for a very long time.

[Reshen @Reshen817]

@wookash_podcast @rfleury You should invite some surprise guests on so @rfleury can tell them to delete their bad faith nonsense face to face

[Reshen @Reshen817]

@arnie_hacker @SebAaltonen Tracy

[Reshen @Reshen817]

@storopoli @Neovim Worth trying out the built in LSP support too, which got much better with 0.12. https://t.co/FJ0Z8mmiTM

[Cosmic Perspective @considercosmos]

Humanity's next great voyage begins

[David Diebold 🚀 @DavidJDPhotos]

Amaze Amaze Amaze!

[Reshen @Reshen817]

@venus_funds @vishalcseiitg @PtrPomorski https://t.co/cDd57q489i