5 ms·
Or, in the small company case, you never hire any dedicated ops people to begin with. You have developers fighting fires all day, getting interrupted constantly
by icedchai 12y ago
Or, in the small company case, you never hire any dedicated ops people to begin with. You have developers fighting fires all day, getting interrupted constantly, causing them to hate their jobs.
- gibsonje 12y agoSmall company. We don't have many problems. We have a couple pain points but we fix them over time. When hosts die, it generally doesn't mean anything. There's redundancy in all things. I don't find myself interrupted often. Previous job had a "Systems" team and a "Database" team. Both were just teams of obstructionists. "Oh you need something today? Well, if you get a jira ticket made I could look into getting the requirements written up sometime in the next 2 weeks, to get the work assigned out next month." Not saying that's the norm, but damn I hope I never experience that again.
- gknoy 12y agoBoth were just teams of obstructionists. "Oh you need something today? ... get a jira ticket made ... work assigned out next month." It is possible that you might have a different opinion of the situation if viewed from their perspective. It's likely not deliberate obstructionism, but rather them trying to triage the requests so that they can be most effective across all customers. (It's possible that your ops team did not adequately communicate this to you.) In my current job, I am the sole developer responsible for maintaining a certain set of our codebase. I have multiple internal customers, each of whom have separate (external) customer-facing needs. I have enough tickets created for three people working full time, so I am constantly having to triage which are the most important. Part of the solution to this was to have a proposed plan for when to work on things -- I can then say, "Thank you for this well thought out ticket. I will be able to work on that in June." The most important thing is that my users' opinion about the criticality of things does not always match the overall picture, and I am always having to choose which tickets to postpone.
- ploxiln 12y agoThis is a good point, but it's a sign of dysfunction. I've seen the case when 50% of the issues are "P1 highest priority" (and most of them forgotten in a week or two). People making requests need to get some idea about what development effort (and maintenance!) costs. I don't know a good way to do this, except to be in a very small company.
- smackfu 12y agoTickets at least require things to be documented, which is the biggest problem with ad hoc devops.
- smiler 12y agoSounds good. Does your company hire remote? :)
- marktangotango 12y agoIf you were the guy getting hit from 20 different people, each with their own emergency, has to be done now, $4 million deal counts on it BS task, I wager you'd be singing a different tune. Oh and come to find out, that $4 million dollar deal? It had fallen through the previous month only no one had communicated it to the person makeing the request. My favorite was the marketing manager who thought an email, with a full size image attachment, and note saying 'this needs to go on the marketing site' was sufficient requirements. Requirements and prioritization are not a bad thing. Excessive bureaucracy is.
- digi_owl 12y agoAs an outsider i feel that the whole devops thing has come from a few web people spinning up some slapdash service using AWS etc and call it a day. Then something breaks and it is firefighting from that day onwards. I wonder if one can draw parallels to the BYOD thing. In both senses it seems to boil down to someone bypassing the IT admins because their manager wants to see results ASAP, and IT is going "sorry, budget and/or regulations says we can't at this time".
- mugsie 12y agoI actually look at from another perspective: It seems to have stemmed from Ops teams saying "What can we do let dev teams build what they want, but in a way we can support it" e.g. - a system needs an entry in the /etc/hosts file (a bad example I know, but a nice simple one for the basic use case) old method: Dev files a Jira ticket, and the Ops team make it part of their golden images for production. new method: Dev makes a change in the Config Management DB. Gets reviewed by a member of Ops, who either approves, or makes a suggestion to change it. Change gets tested against staging, then merged, and the system gets updated. Ops know what the system needs, Dev knows how long it will take, and has an understanding of how it is deployed in real life.
- icedchai 12y agoActual new method: dev logs in to production server, changes something live as part of a emergency / hot fix. It never gets documented anywhere.
- toomuchtodo 12y agoI wouldn't go that far. Its documented on the system when it gets hot imaged and the image is never rebuilt from the config mgmt tool again /s
- dreamfactory2 12y agoso not code as infrastructure and therefore precisely not devops
- kyllo 12y agoYeah I can see an argument for having development engineers and production engineers so that the devs writing new features can focus on that without getting distracted by production issues. The production engineers do monitoring, config management, and bug fixes for prod issues. The problem is in most orgs, the roles for people who fight fires in production tend to be demoted to a lowly "support" title, and paid/hired for accordingly, which is really not commensurate with the value they provide to the organization.
- amyjess 12y agoI had several reasons for leaving my last company, but this was one of them. We had no QA, no IT, no ops. We just had devs doing everything. It might not even have been that bad if we were fairly compensated, but we were all making 3/4 market value in terms of pure salary, no insurance, and no equity to make up for it. We were understaffed, underfunded, and underpaid.
- pjscott 12y agoI was in that situation once, in a previous job. It sucked, so instead of fighting fires all the time, we fixed it. We sought out and exterminated bugs, we set up better monitoring, we wrote automated fixes for the things that could be automatically fixed, and so on. Pretty soon things quieted down for good.