|
Gazpacho posted:the packing desks that amazon gives to corporate employees to do their work on are supposed to symbolize frugality and the spirit of construction, like marine recruits assembling their own bunks to sleep on, but really they're an example of the company's indifference to the question of how to make a work environment productive they're not that cheap anymore either, and nobody here builds them anymore. also most people just do an ergo consult and get an adjustable desk, so they might as well just start switching people over to those. also the laptop/desktop situation sucked for years but about 2 or so years back that was finally fixed.
|
#
¿
Jan 28, 2018 01:02
|
|
|
|
| # ¿ May 14, 2024 06:27 |
|
|
Fuzzy Mammal posted:also inside scoop some big changes are coming in staffing and there's gonna be a lot of unhappy people on the next month or two. i'd bet over the next 10 years amazon sheds like 50% of its full time employees. also iirc i find it very weird that i've probably talked with fuzzywife directly.
|
|
#
¿
Jan 28, 2018 01:12
|
|
|
Gazpacho posted:If you work in a newer part of the company, maybe? Like don't work on the 90s legacy shitstack and don't work in a group that produces no direct revenue and therefore is managed exclusvely for cost. Ask what service framework the group uses and if they say "our own" stay away so ive been at amazon for a little over 4 years now. when i joined i was going to be in for two years but i'm planning to be here for the forseeable future. i would ask * are they in aws? are they in ec2? unless you loathe being oncall for a tier-1 service, i've found aws to be better and ec2 in particular. south africans yall. * ask about whether they use common infrastructure vs homegrown stuff. if they use homegrown, why? and how well do they maintain it? * are they using public aws? for what? if they aren't, why not? there's still a bunch of technical blockers to full native aws now for many teams, but make sure they think public aws is the future for development. * like gaz said, ask about everything you care about. every team/org runs super differently, so don't expect what you heard about team X to be true about team Y. my first team i couldn't work from home at all, whereas my current team many people work from home 2-3 days a week. * if you're worried after a month or three that you made a bad decision, you can transfer teams fairly easily nowadays. there's career fairs 3-4 times a year it feels like. as for revenue vs cost, i would ask how the team charges their customers. a lot of older "cost centers" can be treated poorly because they have no way to assign costs to their customers. builder tools got socialism (every N SDEs means 1 builder tools SDE) but they're also making billing for internal infrastructure a thing as well as moving all internal infrastructure towards public aws. its much easier to justify your budget when you can point at how much other teams are spending on your service, as well as selling it to the public for a profit.
|
|
#
¿
Jan 29, 2018 17:42
|
|
|
Gazpacho posted:codigo the only thing more frightening than the existence of codigo services in 2018 is bsf services in 2018 dividertabs posted:Are you saying to reject teams using Coral or to reject teams using a team-specific framework? coral is another one of those things that if amazon open sourced it 8-10 years ago it would've been really cool and good but now very few people would be interested coral is still good though
|
|
#
¿
Jan 30, 2018 03:01
|
|
|
dividertabs posted:Rejecting a team that does otherwise interesting work just because it has some use of internal tools seems too picky to me. Coral in particular is not going to take a lot of time or pain to learn, and doesn't mean you won't get other opportunities to add AWS keywords to your resume. i think one thing to watch out for is that as more and more companies switch to work samples/projects you need to keep your "setup a service in go/javascript/java using common libraries" skills up to date. can't just click a few buttons for an rpc service in the real world, unfortunately  .
|
|
#
¿
Jan 30, 2018 04:49
|
|
|
Coffee Jones posted:I heard there were teams working with Perl and HTML::Mason the perl/mason retail website is like the php monolith that facebook has (had?). its this thing that most sane people have migrated out of but still persists because of the thousands of random one-off pages that are hosted on it that nobody cares to migrate. there's a few teams who are using go, though most of the ones i've talked to are becoming less and less fans of it. rust is becoming more of a thing for a lot of teams who are writing systems code because it lets them get away from the hellscape that is c++ inside of amazon. There Will Be Penalty posted:perl and mason are what php should have been. I WILL DIE ON THIS HILL. perl is poo poo but php is even more poo poo and has a history of godawful baggage. the only good things about php over perl are that it has a grammar and a better object system (though moose is cool). i too enjoy writing concurrent code through shared_vars and 18 prepare methods
|
|
#
¿
Feb 2, 2018 03:36
|
|
|
President Beep posted:from a layperson’s pov (ie, mine), aws seems to make a strange bedfellow with amazon’s more visible role as a retail outlet for physical products and digital content. does this seem kind of odd to anyone else? it was more like "this is a thing that our internal teams benefit from, lets rebuild this in a way that can support external customers". the first ec2 was a dozen or so laptops bought from a pc store in cape town.
|
|
#
¿
Feb 10, 2018 17:42
|
|
|
this thread got pretty weird pretty fast
|
|
#
¿
Feb 14, 2018 00:53
|
|
|
|
| # ¿ May 14, 2024 06:27 |
|
|
why is this the Illuminati thread
|
|
#
¿
Feb 14, 2018 02:48
|
|