Readit News> S-team listened to employees, watched how our teams performed, talked to leaders at other companies, and got together on several occasions to discuss if and how we should adjust our approach.
> I’m also optimistic that this shift will provide a boost for the thousands of businesses located around our urban headquarter locations
> just popping by a teammate’s office later that day with another thought
I love this, return to the office to get your focused work interrupted, spend your hard-earned money around the headquarters, but most importantly because the "S-team" thinks you should.
Andy Jassy probably never worked as an SDE if he truly thinks any of the above is motivating.
> what would best enable us to make customers’ lives better and easier every day
As someone working for AWS, better uptime, lower costs, and higher feature throughput. How about justifying return to office with hard numbers showing that we've fallen short on those points instead of just handwaving that "it's better".
>>> As someone working for AWS, better uptime, lower costs, and higher feature throughput. How about justifying return to office with hard numbers showing that we've fallen short on those points instead of just handwaving that "it's better"
"The man who literally built AWS has no idea how to run a software company because I'm mad about RTO."
Where did the original comment imply this?
Generally speaking, modern database architectures have minimal dynamic memory allocation, no multi-threaded code to speak of, or even buffer overflow issues (everything internally is built for paged memory). Where are these advantages from Rust supposed to come from? It has a lot of disadvantages for databases today, and I say that as someone who has used Rust in this space. People who build this kind of software are pragmatic and Rust doesn’t deliver for database developers currently.