The comment I replied to stated that only WoW and Overwatch had unionized. Every game team has unionized at Blizzard, along with some of the support teams.
Diablo also unionized and there's some representation in non-game teams like Battle.net. But I also know (I'm in games and in OC myself, loads of friends at local studios from SD, to OC, and LA counties) that they had a demonstration last Thursday, at 2PM Pacific Time they walked out. They claim that leadership is not negotiating in good faith.
I started doing this in the mid-2010s, too. Used to grab throwaway hardware from a former employer and piece whatever still worked together. I've since moved on to a different employer. How do you procure throwaway hardware?
Have you tried Lisp Flavored Erlang [0]? I never got around to trying it out. I used Elixir for a couple of years, building web backends, and I truly loved the experience. I remember wanting to try out LFE but never got around to it before moving on to a different employer/stack.
I just got back from a 12 mile trail run. I'd love to be on the trails more often. And I'd love to explore more trails that are further away. But I have to work all week and that leaves me with my weekends. I also like to read, write, garden, hike, bike, strength train, I have other hobbies like woodworking that I'd love to get back into, homebrewing, I bake bread, and on and on. I love spending time with my wife and my kids and my/our friends. And I have to ration my time heavily because I've got ~50+ hours every single week that's wrapped up in making my staggeringly massive corporation employer more money than it knows what to reasonably do with.
I live nearby, I'm hosting some family at my home who have been evacuated. A fireman friend who has been to the site said the same. That it'll either explode or spill and they're banking on it spilling.
I use coding agents and LLMs at work where I'm more or less to some degree required to. At home, I write code the old fashioned way. Not katas, etc., necessarily, but I've decided that if we live in a world where code is cheap (or cheaply generated) that I'll hone my Lisp skills. I haven't used a Lisp in a few years and it's brought a lot of the joy of programming back for me, at least at home.
> I still have a lot of usage for AI: Exploration, Double-checking me, teaching me.
I'm ready to give up on having it even review my code at this point. It's been so frustrating. It hallucinates bugs, especially in places where "best practices" are at odds with reality.
Recently it informed me of a bug where it suggested the line of code in question couldn't possibly do anything because on Linux the specific stdlib behaved in X ways, but it was obvious from the line of code that it was running on Windows which doesn't have this problem at all. Of course, it doesn't actually mention that this is an issue on Linux, just that there is a bug here. It vomits up a paragraph of $WORDS explaining why this was a high-priority bug that absolutely needed to be fixed because it was failing in subtle ways. Yet the line of code in question has been running in production, producing exactly the results it is expected to, for ~3 years.
And this is just one simple example, of the many dozens+ of times it has failed this task this year. In that same review run, the agent suggested 3 additional "bugs" or other issues that should be addressed that were all flatly wrong or subjective. I'm at a point of absolute exhaustion with this sort of shit. It's worse than a junior half of the time because of how strongly opinionated it is. And the solution to this sort of problem is an endless amount of configuration and customization that will be forgotten about by all of us over time, leading to who knows what sort of knock-on effects (especially as we migrate from one model to the next). We have a guy on our team who has ~17,000 words in his agent and instructions files, yet he sees nothing wrong with this. I guess he just really loves YAML and Markdown.
Yeah I write prompts asking it to misspell a few words, break a few grammar rules, forget to capitalize once in a while, miss some punctuation once in a while. No one will ever catch on.