4 ms·
> Isn't a core tenant of DevOps that your developers are the ones doing the Ops too? Im sure it means that to a lot of developers, and definitely some managers
by stephenr 11y ago
> Isn't a core tenant of DevOps that your developers are the ones doing the Ops too?
Im sure it means that to a lot of developers, and definitely some managers.
The developers see it as "no more ops telling me that I need to use a TLS connection to the database because it's over a WAN", or "no more ops telling me I can't use the 0.0.0.1-pre-pre-alpha version of <insert runtime/framework/daemon> in production".
The managers particularly see it as "we don't need those pesky ops people, so we've just saved ourselves $X per year". They don't tend to factor in the lack of relevant skills by their remaining developers, which tends to result in less efficiency (i.e. taking longer to do shit) and greatly increased risk.
And then the developer says "hey we'll just use AWS because thats what HN all suggest and it's cheap" and you end up paying a heap of extra cash each month because they just run 10 on-demand EC2 instances 24x7 and a host of assorted services to deal with the lack of persistence on EC2 instances, when previously you needed just two servers in failover setup, with capacity to spare.
I've seen what happens when developers "do ops", as I was leaving a company. When you're asked by someone "can you help, I'm trying to install this SSL cert on a server (for a soon to be production system) but I don't really understand how any of this SSL stuff works", there is just one realistic response. Run. Then run some more, hide, change your email and don't answer your phone. Because that shit is about to go down like the titanic.
- UK-AL 11y agoBut web developers should know how SSL works anyway. Otherwise your probably not a great developer. I defiantly learned about SSL, and pki infrastructure through developer knowledge.
- nickpsecurity 11y agoIf library is done well, then you shouldn't have to know much about SSL to be able to use it. Just an abstract idea of it plus how to use the library. SSL from an ops perspective is quite different. That's why it's better to have pro's in each working together on it.
- UK-AL 11y agoI would want a developer who knows the best practice keeping the ciphersuite up to date and understands stuff like client side certificates if they going to work on any security conscious application.
- nickpsecurity 11y agoI'd prefer it but one you mention can be done upstream by library developer with secure defaults. Think NaCl. Client-side certificates might come with best practices or checklists that show proper use with optional data on the way. Neither issue requires understanding SSL in common deployments. Note that I say this while agreeing with you that I prefer someone who knows what they're doing. Especially as SSL support isn't usually at the usability standard I'm describing. Yet, it's not intrinsic to the problem: just crap UX.
- mgkimsal 11y ago> And then the developer says "hey we'll just use AWS because thats what HN all suggest and it's cheap" Never understood this, except from developers who've never actually had to pay for anything out of their own pocket. AWS is nice, and has a place. And I do hear it from people, a lot. It's cheap compared to buying your own hardware and dedicated staff, yes. But for a lot of the standard webapp stuff you might want to do starting out, it's not as cheap as just getting a dedicated VPS someplace. I've been independent/self-employed for a long time, and while I use various AWS services (including EC2 for some projects), it's rarely ever cost which is the driving factor when AWS is chosen. But it's because the $ is coming, directly or indirectly, from me.
- UK-AL 11y agoRunning your own stuff becomes more expensive when you want monitoring, Load Balancers, HA, VPN's into your corporate network and constant database backups. And then making it really robust. Hiring all the staff for that can be expensive. Problem is there are lot of developers who think setting up a virtual machine putting a db on it, and then a webserver on another without thinking about all the other stuff that can go wrong.
- toomuchtodo 11y ago> Hiring all the staff for that can be expensive. Competent, experienced staff to run the core of your business has a cost. You can replace ops with managed services no more than I can replace devs with cheap, untrained labor in Asia.
- UK-AL 11y agoI never said replace, just augment. You may need fewer, but you still need people to monitor, deploy and orchestrate these different services. At the end of the day the extra cost is going toward hiring engineers at the hosters side for managed services but benefiting from their scale. Either way your going to have to pay for skilled operational engineers.
- mgkimsal 11y ago
- nickpsecurity 11y ago"when previously you needed just two servers in failover setup, with capacity to spare." I don't know if you were there but I said the same shit to people here on HN in a hosting discussion. Some company had downtime on AWS and/or a bunch of servers. I said something along lines of how hard can it be to buy four servers at $1-2k each, set them up as HA pairs of pairs, send two to a colo, and manage that? And optionally send another pair to a third, geographical area if one wants more uptime? It's not that hard given we've been doing it since friggin' VMS clusters on refrigerator-sized VAXen. Just dirt cheap now for basic solution. OSS tools are even good enough for homebrewing it with little risk now. Nah, though, let's pay for a bunch of VM's we have to manage anyway that we don't even control on sites with less uptime. (rolls eyes) "but I don't really understand how any of this SSL stuff works", there is just one realistic response. Run. Then run some more, hide, change your email and don't answer your phone. Because that shit is about to go down like the titanic." LOL. That's great. Someone with a meme generator needs to make an image out of this: "DevOps: Replaces Admins, Can't Deploy SSL." I can imagine quite a few more in capacity and disaster planning. Now what image would go with that...?
- siddhant 11y agoTo me this sounds like the developers weren't tested for ops skills before being brought on to a team while everyone knew that developers are required to do ops. Of course, specialisation helps. But the most pleasant work experience I've had was at companies where there was no distinction between dev and ops.
- stephenr 11y agoI worked for the company ostensibly as a developer, but my formal qualifications are in network engineering, and ops (we used to call it infrastructure) is what I did before I jumped to web work. When none of the developers are particularly experienced with ops, how do they know whats required to do ops? Im not saying someone *can't& be skilled at dev and ops. I'm saying the 'normal' result I see, is that management (and some developers) assume any developer can do anything an experienced ops can do, and write that fancy javascript widget too!