- OpenStack: A Plea — critical take on OpenStack, also in this presentation. Notes the proliferation of inefficiency, devops bolted onto the side, and the long feedback cycle. You code differently when you have a pager. (via Sam Ramji)
- What Could Be More Interesting Than How The Mind Works? (Harvard) — the Steven Pinker story. A third ingredient of good teaching is overcoming “the curse of knowledge”: the inability to know what it’s like not to know something that you do know. (via Atul Gawande)
- Some Lecturing Heuristics — Realize further that your mood may be determined by only a few people. A smiling nodder will make you feel good, and you will do better. People reading newspapers will make you feel bad, and you will do worse. Do not permit people to do things that make you feel bad.
- Programming Sucks — every word is true.
ENTRIES TAGGED "devops"
Developers who understand the whole stack are going to build better applications.
Since Facebook’s Carlos Bueno wrote the canonical article about the full stack, there has been no shortage of posts trying to define it. For a time, Facebook allegedly only hired “full-stack developers.” That probably wasn’t quite true, even if they thought it was. And some posts really push “full-stack” developer into Unicorn territory: Laurence Gellert writes that it “goes beyond being a senior engineer,” and details everything he thinks a full-stack developer should be familiar with, most of which doesn’t involve coding. Read more…
Building functionality that really delivers the expected customer value
By now, many of us are aware of the wide adoption of continuous delivery within companies that treat software development as a strategic capability that provides competitive advantage. Amazon is on record as making changes to production every 11.6 seconds on average in May of 2011. Facebook releases to production twice a day. Many Google services see releases multiple times a week, and almost everything in Google is developed on mainline. Still, many managers and executives remain unconvinced as to the benefits, and would like to know more about the economic drivers behind CD.
First, let’s define continuous delivery. Martin Fowler provides a comprehensive definition on his website, but here’s my one sentence version: Continuous delivery is a set of principles and practices to reduce the cost, time, and risk of delivering incremental changes to users.