Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've got a pet theory here that this is going to be a trend over the next few years. A lot of companies github's age were built on the "we misinterpreted devops as noops" attitude, which works great for a few years, but somewhere in the year 3 - 5 range the entropy and technical debt compound faster than a non existent or small/inexperienced ops team can keep up with.


Ops has been at the core of what GitHub does pretty much since day one. I'm not sure there's a team more celebrated within GitHub as our ops guys, to be honest.


I'm not sure I'd call GitHub a #NoOps shop, nor am I sure that I'd call the team inexperienced. What was your point again?


I've got a fact. 1 != 2. Dedicated Ops [Guru] != no outages (Re: Google outages).

Just because those performing operations tasks are also performing development tasks doesn't mean anything substantial, other than it is more likely the Operations and Development teams are closer to being on the same page and there is less potential for someone getting to sit on their thumbs and spinning.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: