1. Floorcraft: Blasters 0.6 just shipped on the App Store.
An open-source AR multiplayer game I helped ship through Tomicz Engineering as part of a grant program with @Auki. First real update since 2023.
3. The big engineering unlock this milestone: modern AI tools for state-transition logging.
The bug we spent the most time on was a split-state race condition between UI and gameplay. Manual tracing would have eaten another month.
6. Hobby? The no-math advice will carry you a long way. Pro? Math is the tax you pay, the same way a 3D artist pays for topology and a backend engineer pays for systems thinking. Nobody skips their tax.
4/ I finally wrote the post I have been getting asked about for years.
Unity Events vs C# Actions vs delegates. When to use each. Why the event keyword matters. What += is actually doing.
All in one place: https://t.co/NmI63BCJOh
1/ Unity events are one of those things you do not really get until you have some real experience under your belt.
They look simple. You subscribe, you invoke, you unsubscribe.
The moment you wire them across a real project, something always feels off.
3/ Six months later you have a project where every class hooks up events in its own style.
Knowing what the model is writing, and setting the rules yourself, is the difference between a game that scales and one you rewrite at month ten.
there’s a dude on youtube making a video with a burst blood vessel in his eye. the title is “software developer driven to insanity by 2026 job market” and he’s pointing at his eye as evidence of the stress he’s going through.
garrett’s a rather normal dude and there were no obvious tells as to why this guy has not been able to find a job for 9 months since he was laid off in july.
but there was a hint.
at one point he describes how he went really far in an interview process, and he was absolutely sure he was gonna get the job. they hire someone else and the dude is incredulous. he asks them wtf!? they show him the winning candidate entry.
garrett used 50% ai and 50% manual coding. he was sitting there being thoughtful and deliberate and properly naming functions and variables and designing modular architectures. meanwhile the winning application was a dude who used 100% ai and his app had a shit ton more features. and he delivered it faster.
so, that’s the kind of dude being hired now. garrett didn’t get the job. but someone else did. so the job is there. the job was open. just not for you.
the thing getting you hired in 2019, like obsessing over code quality and maintainability and best practices, will get you fired in 2026.
the market has spoken. if you want to land a dev job, make more slop.
they want more features done faster at a lower cost.
your job is not to argue. it is to provide the thing they are seeking.
pick 3 companies you really wanna work for, then build their entire app in a weekend as your cover letter. applying to doordash? build their 3-sided market place in 2 hours. applying to google? build your own search engine that does a 2-hour web crawl.
reading code is a dead thing. no one reads their own code anymore, let alone yours. they will run your app. and they’ll judge you off that.
build more slop. build a slop empire. imagine more slop. be the slop. slop slop slop.
get the job. make money. give your boss the slop he wants. don’t argue. slop is peace. slop is strength. inhale the slop. exhale it.
oh you wanna be an artist? cute. go code on a city street like a bucket drummer. you code by hand for tips now. otherwise, off to the slop factory.
enjoy it! enjoy the sloppagaden! make a little money!