41–50 of 151 posts
I’ve been hearing Amazon is going to run out of bodies for years now and yet they keep chugging along.
The economy sucks, and they do pay decently for software engineers. Especially now that the rest of FAANG aren't massively over-paying for college hires, I doubt the supply of bright young minds will ever entirely dry up.
I'm also an AWS alumni from many years back now, and truthfully, the organizational problems really took off when Jassy moved to being CEO of amazon as a whole and major leaders left the company (Charlie Bell, et al.). There were always other problems too, pressure on the company in both directions across many different product lines on both cost (any number of cheaper baremetal providers who are much faster at provi…
Unrelated to your main point, but it's "alumnus" in the singular form. For bonus language nerd points, you would use "alumna" to refer to a woman, or "alumnae" to refer to multiple women. Not sure how Latin handles mixed gender groups, though I would guess it's "alumni".
I was enjoying the article and then he makes some of the most bizarre claims about what cloud did and how we had to provision servers If any of you young'uns read this, that is not how we had to do provisioning before cloud. VMs already existed before AWS came out. You could already provision a new server usually in minutes and rent it month to month. In fact, all the existing VM server companies had to start calling…
AWS was launched around 2006 (2002 internally at Amazon I think). Where could you rent VMs in 2006? IIRC there were two ways to run stuff, get your own server or get an account on a big shared computer.
And they were cheaper than renting AWS. MUCH cheaper. They still are.
The original point of AWS is that could scale according to demand. Have 10 VMs running at lunchtime and 1 VM running at midnight.
But using a cloud VM also required less server admin experience. It was a bit easier and came.pre-configured with things like firewalls.
And THAT is what ended up being the USP of cloud hosting. Especially when they started rolling out all the SQL as a service, redis as a service, etc.
You didn't need to really understand servers to run a server, and it turned out almost all developers really didn't want to understand servers. TBH, I don't, server admin sucks. Right now I'm working somewhere where I have to think about SSL certs occasionally and I consider it a complete waste of my life.
Digital Ocean came out like 5 years after AWS, what was revolutionary about that wasn't that you could spin up VMs quickly, it was the price. VMs went from $20-30 p/m to $5.
For developers who weren't SV rich, that meant you could run a side project without it being a significant cost.
I was enjoying the article and then he makes some of the most bizarre claims about what cloud did and how we had to provision servers If any of you young'uns read this, that is not how we had to do provisioning before cloud. VMs already existed before AWS came out. You could already provision a new server usually in minutes and rent it month to month. In fact, all the existing VM server companies had to start calling…
AWS was launched around 2006 (2002 internally at Amazon I think). Where could you rent VMs in 2006? IIRC there were two ways to run stuff, get your own server or get an account on a big shared computer.
Linode definitely had something along those lines.
Amazon won on APIs and overall integration but VMs were around already.
I remember the story really well as this is when i joined the workforce as a young GNU/Linux fan.
Our company also requires everyone to use more AI-related tools, and I don't think there's anything wrong with that. But the quality of work produced using these tools really depends on the individual's ability. Some people don't put in much effort, and the results they produce are really sloppy, which bothers me a lot.
Over the last month I contacted Support for the first time in many years. This was for a question about how billing works. It went like this; 1. Case created. 2. Unassigned for seven days. 3. Open real-time chat, talk for 25 or so minutes where I guide a first-line Indian chap who plainly doesn't know about the subject in hand and who is as we talk reading the AWS docs I've already read. At the end, just as I couldn'…
Over the last month I contacted Support for the first time in many years. This was for a question about how billing works. It went like this; 1. Case created. 2. Unassigned for seven days. 3. Open real-time chat, talk for 25 or so minutes where I guide a first-line Indian chap who plainly doesn't know about the subject in hand and who is as we talk reading the AWS docs I've already read. At the end, just as I couldn'…
[flagged]