2 ms·

This feels apt to my years at $large_cloud_provider, where the current cohort of folks manage some of the largest web services, but would not be able to develop

This feels apt to my years at $large_cloud_provider, where the current cohort of folks manage some of the largest web services, but would not be able to develop them from the ground up today. The brain drain from these orgs, the shift to maintenance / KTLO, and the focus on sales/AI "features" rather makes this feel spot on.

neilv 1y ago
A couple years ago, when I was interested in working at a huge cloud provider (and, in less-humble moments, imagine myself as one of the people who could've helped build that up from scratch)... I was recruited directly by a manager(!), and to work on a relatively small new piece that I thought my systems programming skills would be up to... but then the big company required me to do a corporate grunt screening in Python, as well as memorize some behavioral corporate drone interview answers. I decided this would be a litmus test for whether the manager would be able to insulate me well enough from megacorp drone BS, and from some of the more aggressive org chart culture that the company was said to have. Nope, it turns out, the huge cloud provider really does insist that I do the corporate drone screening first. I could've passed the screen with a day of memory refreshing prep on Python. (The last time I used it at that point, I had been switching back and forth each day between it and Swift, and had to look up details like how to get the length of a string. Yet I built something in Python with perfect uptime, over a year, in a critical production line, despite tricky complicating factors. And other comparable track record.) Though I think I could've passed the nonsense screening, I decided that I already had enough negative signal, to bow out of the tempting cloud provider job. (I had a very positive impression of the manager. I was only scared of corporate culture outside of the team. If you're going to be a corporate drone, and jump through nonsense hoops, you should do it at a company widely regarded as treating its employees well.)

neilv 1y ago

A couple years ago, when I was interested in working at a huge cloud provider (and, in less-humble moments, imagine myself as one of the people who could've helped build that up from scratch)... I was recruited directly by a manager(!), and to work on a relatively small new piece that I thought my systems programming skills would be up to... but then the big company required me to do a corporate grunt screening in Python, as well as memorize some behavioral corporate drone interview answers. I decided this would be a litmus test for whether the manager would be able to insulate me well enough from megacorp drone BS, and from some of the more aggressive org chart culture that the company was said to have. Nope, it turns out, the huge cloud provider really does insist that I do the corporate drone screening first. I could've passed the screen with a day of memory refreshing prep on Python. (The last time I used it at that point, I had been switching back and forth each day between it and Swift, and had to look up details like how to get the length of a string. Yet I built something in Python with perfect uptime, over a year, in a critical production line, despite tricky complicating factors. And other comparable track record.) Though I think I could've passed the nonsense screening, I decided that I already had enough negative signal, to bow out of the tempting cloud provider job. (I had a very positive impression of the manager. I was only scared of corporate culture outside of the team. If you're going to be a corporate drone, and jump through nonsense hoops, you should do it at a company widely regarded as treating its employees well.)