10 ms·
On the contrary, the way Amazon treats their employees does harm them substantially, they just haven't paid the price visibly to the public (or quite as hard as
by potatolicious 15y ago
On the contrary, the way Amazon treats their employees does harm them substantially, they just haven't paid the price visibly to the public (or quite as hard as they will, eventually).
Attrition at Amazon is at horrific rates. I know the actual number, though I'm pretty sure that'd violate my NDA to reveal. It's high. It's really high. Guess a really truly terrible number. It's probably higher than that.
The stream of people leaving the company isn't a trickle as it is a well-managed places. It isn't even a modest stream. It's an outright deluge, particularly in this market where everyone else is desperate and willing to pay (protip: Amazon, as a rule, is not).
This is starting to show itself in many places in the company. In a lot of places there are no longer any senior engineers left who know how the system works. In their place are fresh-faced college grads struggling to contend with a system they neither have the experience nor the documentation to maintain, much less extend. The average tenure of the Amazon engineer is embarrassingly short, and coupled with the company's notorious lack of documentation, it means that technical debt is accumulating at an alarming rate.
There are constantly projects to completely revamp/redesign some portion of Amazon's systems. In my observation this is less about an honest improvement over the old system (sometimes there IS no improvement) but rather because nobody knows how the fuck the old thing works. The truly sad thing is, they have trouble keeping engineers around long enough to even see that redesign through.
If you know where to look on Amazon's site, you would see lots of evidence of this already. Extremely deep integration into systems that literally no one still with the company understands. Tons of mission critical code whose original author is long gone, no documentation exists, and in fact the code isn't owned by any team. I've seen many hacks to work around these problems, though I doubt they'd be super apparent to the common Amazon shopper.
The problem here, like many other companies in a similar stage, is that very little of Amazon's management has a technical background at this point. Bezos certainly does, and I still think he's one of the best CEOs in the industry right now, but many of his underlings... not so much. A lot of management do not see this accumulation of technical debt. Difficulties working with said debt is perceived as either "natural" difficulties of working with technology, or worse, incompetence. Amazon's internal existence is a depressing cycle of: hire people, people spend eons learning how the previous guys did it, people write code, people get fed up and leave, hire more people, people spend eons learning how the previous guys did it...
If any Amazonian management is reading, I have one thing I really want to drive home: stop being so fucking "frugal" with equipment. It is a travesty that my development desktop was a Celeron worth $300 on eBay. Not because I like having the newest shiny, because I couldn't even run multiple dev environments on it, like I had to for my JOB, and building my code took 12 full minutes, instead of, say, 3. Stop shitting on your devs with dinky 5 year-old monitors and give them some screen real estate. There are plenty of studies that outright prove the productivity boost that comes with bigger monitors.
- davedx 15y agoHaha it's so sad when companies can't even buy decent equipment for an employee they're spending 30-50x that much on per year. I'm currently spending half my time at this job developing enterprise Java in a VirtualBox instance on an old Windows XP machine with 2GB of RAM. I'm just hoping they pay for the JRebel license before my demo license expires.
- cphang 15y agoYou can try to use https://social.jrebel.com https://social.jrebel.com
- nirvana 15y agoI still periodically try out some of the regression tests that I'd done back when I worked there... there are bugs that have been in the site for about 4 years now. I think when my team was reduced by %90 from people leaving, they just disbanded it and nobodies doing that work now. Certainly the major initiatives haven't moved forward. I don't think Bezos has a technical background... I thought he was a hedge fund guy before moving out to Seattle. But I agree with everything else you said. The funny thing was, when I got hired I was told that they were going to let people use Macs and that it would be a few months. I had my own laptop I was willing to bring in and use, and though they were trailing macs with a few people, I was told I'd be fired if I used my personal mac for work. So, I had to use a piece of crap HP laptop. The thing was always in the shop. There were many days when I basically lost an entire days worth of work because it would break. They replaced it several times. (and I was babying it.. .it lived on my desk for the most part.) So, not only could they have had zero costs by letting me use my own machine, but they lost more than the cost of the laptop several times over in lost productivity by me not being able to work when the machine they made me use was in the shop. And when I left, they still hadn't approved macs (or maybe the IT department decided they were "too insecure" or some BS.) While I was there, they were constantly starting initiatives and then abandoning them. Like the restaurant menus. The movie schedules. The scanning of mail order catalogs!? They'd start some project, do a press release, then disband the team and never advance the code again... it would just sit there and rot. I think one of the reasons that most of management there is not technical is that non-technical people are threatened by technical people in that role. Technical people have quite an edge when managing programmers. I think engineers who express an interest in moving to a management role are often perceived as a threat.