Book review: Accelerate

Book review of Accelerate: The Science Behind DevOps – Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD, Jez Humble, and Gene Kim.

If you have been at any programming or agile related conference within the last 8 months or so, you will probably have heard people recommend Accelerate. One of the reasons it is often recommended is that it explains the importance of DevOps for high performing tech organizations. This is not really anything new, but what Accelerate does, is base it on actual science, and not just anecdotes and opinions – something we see all too often in the tech field.

The findings of Accelerate is based upon the survey data collected through the yearly survey “State of DevOps” in the years 2014-2017. Those data clearly demonstrated that a high performing organization performed much better than a low performing organization, but they could also be used to explain what caused this differences in performance.

The book is split into 3 parts, a conclusion, and some appendixes. The first part explains the findings, the second part, the science used, and the third part is a case study contributed by Steve Bell and Karen Whitley Bell. I will go through each part separately below.

The first part of the book is called “What we found”, and what they found is certainly noteworthy. They looked at some key indicators of software delivery performance, and found that a high performance organization had the following performance compared to low performance organizations:

  • 46 times more frequent deployments
  • 440 faster lead time from commit to deploy
  • 170 times faster mean time to recover from downtime
  • 5 times lower change failure rate

These numbers are from page 10 of the book, and show a much greater difference than most would expect, no matter how big a proponent of DevOps.

The rest of the first part of the book goes through their other findings, which identifies “24 key capabilities that drive improvement in software delivery performance, and, in turn, organizational performance”. According to the authors, “[t]hese capabilities are easy to define, measure, and improve”.

I won’t include the list here, but many of them relate to DevOps practices and lean management practices, though there are a couple related other things, such as architecture. One thing I will mention, is that the findings indicate that while culture has an influence on the use of DevOps techniques, the use of DevOps techniques also have an influence on culture, which changes as a result of that.

None of the mentioned capabilities are new, but here we have, for the first time, evidence that they actually work, and help improve performance.

The second part of the book, “The Research”, goes into how the research was conducted, and why survey data was suitable for the research. It doesn’t include the actual data, which would have been nice, but I can understand why that isn’t the case (breach of confidentiality etc).

I can’t recall seeing a similar chapter in any other book on programming/systems development, and I highly applaud it. I also think it was a smart move to put it in the second part, rather than the first part, as most people will be more interested in the findings, rather than the methods behind finding them.

The third part of the book, the case study contributed by Steve Bell and Karen Whitley Bell, is called “Transformation”. They takes us to Ing Netherlands, a world-wide bank, where they have been involved in a cultural change, started and lead by the IT manager, enabling the organization to become high-performance.

To be honest, I find this part to be the weakest part of the book, both in content and in presentation, but it does provide a nice overview of practices on the team, management, and leadership level (it can be found online here).

All in all, the findings of the book should not be shocking to people who has worked with agile, DevOps etc., but it is nice to have a list of proven capabilities to focus on. It is also a useful tool when debating with management about these subjects.

I highly recommend the book to people working in any aspect of software engineering – be it as a programmer, a project manager, in a leadership position, or in any other capacity.

RIP Joe Armstrong, the author of Erlang

Sad news from the world of programming, Joe Armstrong, one of the authors of the Erlang language has died

I never worked much with Erlang, and have never met Joe Armstrong, but from everything I hear, he was a genuinely nice man.

If you want to know more about Erlang, and how it was used, you can watch Erlang the Movie.

To be honest, I highly doubt anyone outside the world of programming will get much out of that clip, but it is interesting to watch, since it shows what type of problems Erlang was developed to solve. It gives a view into the early days of digitizing telephony, which wasn’t that long ago, considered how long telephones and other forms of telecommunication has been around.

Reporting on the Mueller Report

The redacted Mueller Report came out yesterday, and there is already some great reporting on it, Let’s just say, that unlike what the Trump administration tried to spin it as, the report is pretty bad for Trump.

You can find a searchable version of the report here.

Lawfare has been busy with writing their first thoughts in What Mueller Found on Russia and on Obstruction: A First Analysis

“Really the best day since he got elected,” said Kellyanne Conway, the president’s counselor, about a day on which 400 pages dropped into the public’s lap describing relentless presidential misconduct and serial engagements between his campaign and a foreign actor. The weeks-long lag between Attorney General William Barr’s announcement of Robert Mueller’s top-line findings and the release of the Mueller report itself created space for an alternate reality in which the document released today might give rise to such a statement. But the cries of vindication do not survive even the most cursory examination of the document itself.

No, Mueller did not find a criminal conspiracy between the Trump campaign and Russia, and no, he did not conclude that President Trump had obstructed justice. But Mueller emphatically did not find that there had been “no collusion” either. Indeed, he described in page after damning page a dramatic pattern of Russian outreach to figures close to the president, including to Trump’s campaign and his business; Mueller described receptivity to this outreach on the part of those figures; he described a positive eagerness on the part of the Trump campaign to benefit from illegal Russian activity and that of its cutouts; he described serial lies about it all. And he describes as well a pattern of behavior on the part of the president in his interactions with law enforcement that is simply incompatible with the president’s duty to “take care” that the laws are “faithfully executed”—a pattern Mueller explicitly declined to conclude did not obstruct justice.

The Mueller report is a document this country will be absorbing for months to come. Below is a first crack at analyzing the features that are most salient to us.

Politico has made a an annotated guide to the redacted Mueller report

The Justice Department on Thursday released a redacted version of special counsel Robert Mueller’s report on whether Donald Trump’s campaign colluded with Russian officials and whether the president obstructed justice.

While the investigation did not find hard evidence of collusion, the report detailed numerous instances in which Trump tried to interfere with the probe.

We’re annotating the document in real time, pulling out the excerpts we find most interesting, and giving you the analysis you need to understand Mueller’s findings.

Andrew Torrez does a great job at looking at the Barr report summary, and how it holds up to the actual report over at Opening Arguments in the episode OA271: Dis-Barred (?) – The Mueller Report

Facebook takes a step in the right direction

It is no secret that social platforms have played a major part in the spread of right-wing ideology.

The social media companies are generally slow in doing anyting against this spreading, some times to such a degree that some people claim that they help spreaad right-wing stuff.
Now, Facebook have taken a step in the right direction.

Facebook said the decision was taken because it bans users who “proclaim a violent or hateful mission or are engaged in acts of hate or violence”.

“Individuals and organisations who spread hate, or attack or call for the exclusion of others on the basis of who they are, have no place on Facebook. Under our dangerous individuals and organisations policy, we ban those who proclaim a violent or hateful mission or are engaged in acts of hate or violence,” Facebook said in a statement.

“The individuals and organisations we have banned today violate this policy, and they will no longer be allowed a presence on Facebook or Instagram. Posts and other content which expresses praise or support for these figures and groups will also be banned. Our work against organised hate is ongoing and we will continue to review individuals, organisations, pages, groups and content against our community standards.”

It is a move that has been slow in comming, but it is good that Facebook has finally taken it. Now, we just need for them to react to all the other far right-winged individuals and groups, and for the other social media, like Twitter, to do it as well.

Edit: I had forgotten to write “far” in front of right-winged in the last paragraph, making it seem like I was calling for a more extreme stance than I did.

Ola Bini arrested in Ecuador

Gizmodo reports on the arrest of programmer superstar Ola Bini by the Ecuadorean government:

Police in Ecuador have arrested Swedish programmer and digital privacy activist Ola Bini for allegedly trying to destabilize the Ecuadorian government by “collaborating” with WikiLeaks. Bini was arrested at Quito Airport in Ecuador on his way to Japan.

Ola Bini is a Swedish programmer with a truly impressive resume, and a frequent speaker at conferences. According to his own website, he has choose to focus on “privacy enhanching technologies”.

So far, it doesn’t seem like Ola Bini has been charged with anything, but the claims made by the Ecuadorian government are very serious.

The EFF has come out in defense of Ola Bini: The Ecuadorean Authorities Have No Reason to Detain Free Software Developer Ola Bini

I am entirely on the side of the EFF on this. I have met Ola Bini, and find it very doubtful that he would do anything like the things claimed by the Ecuadorian government. And even if he had, he should still be allowed proper due process, unlike how he has been treated so far, according to his lawyers.

There is a petition to get Ola Bini released, which you can sign here