“I will NOT sacrifice the Oxford comma. We've made too many compromises already; too many retreats. They assimilate the em dash and we fall back. They capture ‘not just X but y’ and we fall back. Not again. The line must be drawn here! This far, no further!”
Game workers do not receive any residuals/royalties on shipped titles and shipping bonuses are increasingly rare. There's also no guarantee that your name will even be in the credits if you leave before ship, and studios will use this to keep you compliant.
I expect the real win here is probably that they're gluing together the existing functionality, rather than writing big bespoke BPs to get the exact functionality they want. Still surprising to me that they would actually do that, though
Before I moved into my current place, I used to walk past a house with several cats on my way to the train every morning. I never had treats or catnip or any sort of food, yet all of them were very friendly with me and one of them even liked to climb up and sit on my shoulder and groom my hair.
Reminds me of the time I once (mistakenly, the website was confusing) ordered a pizza online with NO sauce at all. The pizza place literally called me in sheer confusion to ask me WTF I was doing and what I *really* meant
I've been running gdcparties.com for a few years now. Some shitty company BlueberryAI decided they'd just take all the source code for the work I've done and reskin it, advertising it as their own. Jokes on them...it was still linked to my events spreadsheet, and now their website looks like this 😉
Never mind *folding* the fitted sheets, can we talk about trying to get them to dry without rolling themselves up into a bundle and not actually getting dry?
I think reading SF and fantasy with a lot of upfront worldbuilding may be good prep for learning new code quickly. It accustoms you to being in a place where you know the language, but there are so many nouns, new or being used in ways you don't recognize, that the first chapter is incomprehensible
(mind you, "frontend" and "backend" ARE terms I've seen used in gamedev, but I don't think their usage quite lines up with how a web or cloud dev would use them, and when I hear this question it's usually someone familiar with one of those other two fields asking it)
What are people expecting a gamedev to say when someone asks them if they're a "frontend" or "backend" or "fullstack" developer? In my mind that distinction is barely even meaningful for us. What do I even call the "backend" of a video game? Is that everything but the graphics/audio/UI code?
Every time I code something new it often doesn't take long but what takes longer is thinking of all the edge cases and ways it could break, listing and testing/fixing those.
Also if I modify existing code I always think "what could this have broken" and retest stuff.
I listened to this on repeat for THREE DAYS after I first heard it and figured out what it was. And then I read the lyrics and decided I didn't care that it wasn't about the sort of yearning I thought it was.