AWS Lumberyard (better known as "the AWS service that had a Terms of Service callout for zombie apocalypses") has had a bunch of its code open sourced and hurled over to the Linux Foundation to effectively make it their problem now.
This is a delightful way to wind up cloud advocates, open source fanatics, and the wonderful denizens of gaming culture all in one go.
Obviously "you're doing it wrong" is basically the only thing upon which those constituencies agree.
It appears that they're gradually sunsetting Lumberyard while supporting existing customers, but the future is the awkwardly-named O3DE expression of the technology, which I refuse to even attempt to pronounce.
I'm... cautiously optimistic here? Amazon has long struggled to make headway in the games space. A bunch of big names are on board with the new effort, so we're going to find out.
*IF* it works, this becomes a tentpole of AWS's "we're a friend to open source" messaging.
I'd really like to see this succeed; if it doesn't the fallout will be Unpleasant.
The challenge here is that we're not likely to know if it succeeds for years yet; large-scale AAA titles take time to build and release.
I freely admit I don't know enough about the sector to have a deep level of insight into what the next steps look like.
I'd be more interested to see what folks like @thevowel have to say about it, personally.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
In hindsight, the recurrent failing that my managers always had was that they failed to explain just exactly WTF their job was. It turns out that 'managing me while catering to my every whim' was absolutely not it.
From where I sit, the hard truth is partially that having employees isn't the manager's job; having employees is simply their current approach to getting the actual responsibility handled.
"Build a better mousetrap and the world will beat a path to your door" is a lie presumably spread by mice. Your door must feature a cash register because the mousetrap will not sell itself.
Take what we do at the @DuckbillGroup as an example. "Consulting projects that pay for themselves many times over before they're complete" sounds super compelling and easy to sell.
There is no such thing as an easy sale to a sophisticated business customer. Thus we hire salespeople to drive the sale and thus keep our Spite Budget topped up. Their primary job is helping a buyer sell the project internally.
Oh ho ho I just saw this. With @gaberivera's begrudging permission and significant trepidation I will be tackling the mini-essay questions in a tweet thread. Let's begin!
I'm seeing a lot of crappy takes about Amazon's leadership principles (amazon.jobs/en/principles) today, and I want to break character for a minute to give my sincere thoughts on them.
Culture is hard. Maintaining that culture across a massively scaled company is virtually impossible. How do you avoid the problem of not having a corporate culture but rather 2000 different ones?
Amazon's answer to this comes in the form of the 16 Leadership Principles. They're easy to snark on, but in the almost five years I've been studying @awscloud I've gone from skeptic to believer.
Many of the big tech companies are forcing staff to go back to the office. I think this is shortsighted; you should make the company beg you to go back to working remote. A thread of advice from some of the worst colleagues I ever had:
Cherry MX blue switches in keyboards are noisy, but buckling springs are louder. You'll get used to them more quickly if you hum along to the sound of your keystrokes.
What's for lunch today? Your leftover fish from last night's dinner. Throw it in the microwave and reheat it. Ten minutes oughta do it.