News for hackers. Stuff that matters.
Re:What I Wish I Had Known Before Scaling Uber [video] by asimuvPR on Wednesday September 28, 2016 @09:39AM (#12597495)
I've come to question releasing often as a result.
Re:What I Wish I Had Known Before Scaling Uber [video] by jon-wood on Wednesday September 28, 2016 @09:45AM (#12597545)
I can see the argument that if releasing causes things to break then don't release so frequently, but in practice the end result of that is lots of things breaking at once and having to unpick everything. Debugging is much easier if you're debugging a single change fresh in your mind.
Re:What I Wish I Had Known Before Scaling Uber [video] by bryanlarsen on Wednesday September 28, 2016 @09:58AM (#12597635)
Yeah, debugging 2 bugs that are shadowing each other often takes several orders of magnitude longer to debug than just a single issue.
Re:What I Wish I Had Known Before Scaling Uber [video] by asimuvPR on Wednesday September 28, 2016 @01:44PM (#12599682)
You are right. Making small changes that can be isolated for debugging purposes is a good approach. What I mean is that we should always question "best" practices and how we apply them to our development process. These days there is a tendency to drink the kool-aid (guilty of this as well). DevOps is something that we are still learning and developing as a profession.
Re:What I Wish I Had Known Before Scaling Uber [video] by dozzie on Thursday September 29, 2016 @04:47AM (#12604027)
> DevOps is something that we are still learning and developing as a profession.

Not really. DevOps is simply a modernish label for system administration that we have for dozens years already.

Re:What I Wish I Had Known Before Scaling Uber [video] by the_other on Thursday September 29, 2016 @07:17AM (#12604423)
Isn't that just "Ops"?
Re:What I Wish I Had Known Before Scaling Uber [video] by dozzie on Thursday September 29, 2016 @08:01AM (#12604590)
My point exactly.
Re:What I Wish I Had Known Before Scaling Uber [video] by aurelianito on Thursday September 29, 2016 @01:19PM (#12607034)
Yes, but now we actually try to automate in a systematic way; as opposed to a single admin hacking some custom shell scripts. That's what the dev in devop mean. And that's new, at least it was not a common activity in the XX century.
Re:What I Wish I Had Known Before Scaling Uber [video] by dozzie on Thursday September 29, 2016 @03:01PM (#12607917)
If by "systematic way" you mean a group of programmers clueless about system administration hacking together some custom Ansible scripts, then I wouldn't call it progress.

Sysadmins have tools to automate their work for a long, long time (cfengine, bcfg2, even Puppet and Chef predates DevOps hype). DevOps didn't bring anything new to the table.

Re:What I Wish I Had Known Before Scaling Uber [video] by aurelianito on Thursday September 29, 2016 @05:42PM (#12609004)
Is not about doing it right or wrong. Is about the automation that is reused cross-project and the fact that a lot of things that used to require a sysadmin now we automated its job away. If developers implement it correctly or poorly is a different issue.

It is also not about hype (or not). I do agree that the name is posterior to the beginning of the practice, but it is the name that we have.

Re:What I Wish I Had Known Before Scaling Uber [video] by dozzie on Thursday September 29, 2016 @06:01PM (#12609146)
Being a sysadmin was always about automation. DevOps brought nothing to the table about that. Neither tools nor paradigm. And the name is just another one for "administering systems", if we keep what you seem to mean by DevOps.

It's still no progress, hacky scripts written by sysadmins or similarly hacky scripts written by programmers, and systematic way of automating tasks was available to sysadmins and was used by them for a long time. DevOps brought nothing new to the table.

Re:What I Wish I Had Known Before Scaling Uber [video] by asimuvPR on Thursday September 29, 2016 @10:06PM (#12610127)
I've always had the imoression that a sysadmin ( a position I deeply respect) was more comprehensive than DevOps. DevOps mostly focuses on automating the infrastructure of software development. A sysadmin does that and more.
Re:What I Wish I Had Known Before Scaling Uber [video] by Thrillington on Wednesday September 28, 2016 @10:10AM (#12597702)
While having tooling for tight debugging loops allows short release cycles, it leaves that decision up to the business
Re:What I Wish I Had Known Before Scaling Uber [video] by zaroth on Wednesday September 28, 2016 @09:53AM (#12597596)
It seems like so many "best practices" are really thinly veiled attempts at exploding complexity with only tenuous potential business advantages.

We create ourselves so many of the problems we are paid to solve.

Re:What I Wish I Had Known Before Scaling Uber [video] by thomaslee on Wednesday September 28, 2016 @03:48PM (#12600716)
> It seems like so many "best practices" are really thinly veiled attempts at exploding complexity

I'll bite. :D

It's a bit more nuanced than that IMO, the "deploy often" mantra is only as good as the process around release + deploy. If you half-ass testing and push to production without without a process for verification -- or if, say, your deploy process is half-baked, or your staging environment is worthless -- you can probably expect "interesting" production deploys on a pretty regular basis.

As much as we'd like to pretend we're all good engineers, this happens more often than you'd expect -- even with good engineers: at some point a company transitions from scrappy startup to a shambling beast, and the things that used to work for a scrappy startup (like skimping on testing and dealing with failures in production) are insufficient when you've got more eyes on the product. Further, the engineering culture remains stuck in "scrappy startup" mode long after the shambling has begun.

And all that's ignoring the fact that less frequent deploys with more changes have their own set of problems. We actually got to a point with deploys of a certain distributed system such that we were terrified if we had more than a few days worth of changes queued up. So many things that could go wrong! :)

> We create ourselves so many of the problems we are paid to solve.

This, on the other hand, I completely 100% agree with: if not us, then who? :)

EDIT: minor formatting change

Re:What I Wish I Had Known Before Scaling Uber [video] by mLuby on Wednesday September 28, 2016 @02:32PM (#12600080)
"We create ourselves so many of the problems we are paid to solve"

Sounds lucrative ;)

Re:What I Wish I Had Known Before Scaling Uber [video] by jessaustin on Wednesday September 28, 2016 @05:13PM (#12601409)
It works for doctors and lawyers; why shouldn't software developers try it?
Re:What I Wish I Had Known Before Scaling Uber [video] by cortesoft on Wednesday September 28, 2016 @10:56AM (#12598120)
The breakage rate per new feature is fairly constant; if you release 7 new features once a week or 1 new feature once a day, you will have the same number of issues. The question then is; is it easier to deal with all the issues at once, or a smaller number of issues every day?
Re:What I Wish I Had Known Before Scaling Uber [video] by danek on Wednesday September 28, 2016 @11:48AM (#12598618)
In addition to that, I would also worry about interactions between issues. I tend to lean towards spreading out the issues over time to make the eventual diagnosis easier.

Occasionally we'll have a problem where we cannot deploy to production for several days (normally it's once a day). A massive inventory of ready-to-deploy features builds up. When we do finally deploy, this deluge of features and fixes creates new issues that force a rollback, delaying the deploy even longer...

Re:What I Wish I Had Known Before Scaling Uber [video] by cortesoft on Wednesday September 28, 2016 @04:21PM (#12601008)
Absolutely. Confounding issues are the biggest problem, even more so than sheer volume in a small time frame.
Re:What I Wish I Had Known Before Scaling Uber [video] by pc86 on Wednesday September 28, 2016 @01:35PM (#12599602)
Sounds like a testing/UAT issue.
Re:What I Wish I Had Known Before Scaling Uber [video] by awj on Wednesday September 28, 2016 @07:40PM (#12602229)
Funny, I've taken it as justification for releasing often. If I have a hard time changing one thing without breaking the service, it's nearly impossible to change a hundred things without breaking something. Since it's a given that I will have to change things, I'll try to stick to a scope where I stand a chance of doing so successfully.
Re:What I Wish I Had Known Before Scaling Uber [video] by msoad on Wednesday September 28, 2016 @01:18PM (#12599467)
You can roll back a small release that broke the world. A
Re:What I Wish I Had Known Before Scaling Uber [video] by AYBABTME on Wednesday September 28, 2016 @03:29PM (#12600547)
Or the opposite: embrace failure, practice resiliency, work with it instead of against it!