3 ms·
> All that build infrastructure or coding standards or documentation or monitoring systems that you took for granted at Google or Facebook? None of it exists. N
by scarejunba 7y ago
> All that build infrastructure or coding standards or documentation or monitoring systems that you took for granted at Google or Facebook? None of it exists. Not only that - you won't be rewarded for building it, instead you'll be asked why the next person to come behind you got their work done faster than you did.
Not necessarily like that, but yes, almost. For instance, if someone sat down and spent a month writing documentation for shit we might pivot from in two, I must fire myself for having let it happen. Just wasting money and (perhaps more importantly) time.
I've definitely seen what you're saying happen, though. Lots of FAANG engineers not experienced in how things come to be.
- "Why don't we have blue/green deploys?"
- "Great idea. What will it help us with and how can we make it happen?"
That's likely to happen. Someone else speccing out a deploy system for you with canaries or b/g or whatever so you can go write some code isn't going to. You're hopefully independent enough to make the case, build the thing fast enough that it's worth it to the business, and have it running.
- ehnto 7y agoIt can get a bit cumbersome. Especially for people coming fresh into an agency environment. You are going to have to learn a dozen different build pipelines and tech stacks by the time you are done at the agency. We are absolutely aware of blue green deploys or whatever it may be, in fact client X had it, they are gone now though and our most recent inherited code base uses cloud formation to spin up feature specific environments instead, have fun learning that and then never using it again. We work hard to normalize tech stacks and deploys as they come in, but it is always a cost/benefit tradeoff and very often "leave it alone" is the clients choice.