4 ms·
Because they're "conservative" and don't change their entire stack to use the latest cool-kid technology every 6 months? Because they recognise that devops mea
by stephenr 12y ago
Because they're "conservative" and don't change their entire stack to use the latest cool-kid technology every 6 months?
Because they recognise that devops means something other than "we let our developers run wild in prod"?
- fsk 12y agoAt one place I worked, they let developers use whatever tools they wanted. The result was that their website was dependent on 50 Javascript packages that took forever to load. They had parts of their system written in Javascript, PHP, Ruby, Python, and .NET. That's how you get job ads that say "Candidate must have 2+ years experience in Python, PHP, Ruby, C#, and Javascript." Imagine putting a big effort into Angular 1.0, only to discover a year later that it's no longer going to be supported. Is it so bad for Etsy to be avoiding problems like that?
- stephenr 12y agoOh I believe it - I've worked on projects where a single developer adds a dozen JS libraries/jquery plugins/whatever because there is no concept of how maintainable it is long term. I don't even really like to call this "conservative". To me, "conservative" would be no XHR, no custom fonts, etc - the sort of stuff you know will work on IE5. I would consider the approach Etsy uses simply as "sane".
- makeitsuckless 12y agoThe problem in this scenario is not letting the developers use whatever they wanted. The problem is hiring the wrong developers, ones that use that freedom irresponsibly. Keeping developers on a short leash doesn't solve that problem, it just covers it up. And it becomes a self-fulfilling prophecy, because any developer capable of making their own decisions won't work there, so what you end up with is people that need that level of micromanagement. (Yes, this is a form of micromanagement.) And that's what I read in the whole article: an inexperienced CTO who has shaped his policy based on his own limited experience, not acknowledging that that vision is heavily influenced by his own weaknesses. He is projecting his own attitude as a developer on all developers, and extrapolates from there.
- stephenr 12y agoI've met far more developers who would add some extra tech to the stack without a lot of deep thought about the actual consequences of doing so, than those who would either not do that, or discuss it with peers/senior devs/mentors etc. If you give developers carte blanche permission to add whatever they feel is necessary, you're using your business success/failure to teach them. That is wrong. As the CTO, the author's primary responsibility is to make sure the right tech decisions/solutions are made. It sounds to me like he's doing exactly that. If an experienced, "responsible" developer thinks they can make good use of tech X, surely he/she will understand that there is a standard process to have this new thing approved for use, and then it can benefit the entire company. If you can't identify to someone else why you think tech X should be used, what problem it solves, what process it makes more efficient, etc, then you're probably the wrong person to be making a decision about adding new software to the stack. Any "engineer" (I really bet actual engineers love how software developers have co-opted that term) who is "responsible" as you put it, and wants to add software to the stack, will surely discuss that plan with at least someone, right? Or maybe not. Maybe you think every developer should be allowed to make grand architectural changes to a platform worked on by 200+ other staff at their own discretion? If so I suspect somehow, that your reply is just a knee-jerk reaction to a place that expressly prevents cowboy-developer antics before they begin.
- makeitsuckless 12y agoYes, I've also met far more irresponsible, unprofessional developers than responsible, professional ones. As the CTO, my first responsibility is to hire the people that make the "right" decisions/solutions. Of course they discuss those decisions with their coworkers and me. That's just common sense. Sure, I'll make the odd hiring mistake, but that's no excuse to create and entire culture around the assumption that every developer I hire has the maturity and professionality of a teenage sociopath. My reaction is a knee-jerk reaction to a culture of distrust, bureaucracy and micromanagement. The alternative to letting the inmates running the asylum is not to lobotomise the inmates, it's to not turn the place into in asylum in the first place.
- fsk 12y ago
- overgard 12y agoNope. Because they place little value on the expertise of their engineering staff, as evidenced by the comical restrictions they inflict on intelligent professionals.
- stephenr 12y agoIt says quite clearly, they have a process for adding new tech to the stack, and that developers have more freedom for their own environment than for things going into prod. Just because you have to convince someone to agree with and approve your use of shiny-new-thing v0.0.0.1alpha doesn't mean they have "comical restrictions".
- overgard 12y agoI should clarify: my opinion doesn't have anything to do with the use of shiny new tech. I think using tried-and-true tech stacks is perfectly sensible. My commentary has to do with the impression that engineers there are not trusted to make those decisions.
- stephenr 12y agoIf 230 "engineers" all make choices about tech in use, you end up with a fucking nightmare mess of every imaginable tech stack mixed and matched. It says very clearly they will use new things when the benefit can be shown. So it still just sounds like you don't like that you would need to prove why you're changing something on a whim, because "oh this is better" doesn't cut it Edit: fixed weirdest typo/autocorrect weirdness ever.
- overgard 12y agoWell, trust is a very important part of a working relationship. I don't change things willy nilly for fun because I wouldn't want to betray my employers trust in me. I've been in high-freedom situations in companies with lots of engineers, and you know what? Chaos did not ensue. Professional pride, interest in being able to collaborate with others, etc tended to reign things in just fine. The article, to my perspective, suggests a situation in which there is very little trust towards their employees. Having seen both ends of the spectrum, I wouldn't want to work in an environment like that.