"Once IT decides to focus on speed, two obstacles get in the way: security and governance." This is important. Manage security without it becoming an impediment.
The Unix philosophy is a noble idea, but even Unix doesn’t follow it too closely. "Write programs that do one thing and do it well." is one point in the philosophy that is especially strained.
Facebook engineer Doug Beaver shares in a W3 mailing post why Facebook endorses SPDY. He highlights cross-browser support as well as the ability to speed up communication between geographically distant web servers.
One I get asked quite a lot is: "How do you configure GlassFish to receive notifications/alerts/messages on important log entries?". Seems to be a good topic to blog about.
There are a number of books that influenced Kief Morris' thinking on Continuous Delivery. Here are his top 7.
We live in a world where we are already expected to know, where competence is assumed, but competence disappeared with craftsmanship to be replaced by production lines. Hierarchical management dug the nail in the coffin as the goal became moving up to the next job rather than getting good at the one you’re in.
At Devopsdays I listened to a lot of smart people saying smart things. And to some people saying things that sounded smart, but really weren’t. It was especially confusing when you heard both of these kinds of things from the same person.
Ten of the best books from the Deathray Research bibliography. Guaranteed to make you smarter about software engineering and the world. Inspired by the book, "This Will Make You Smarter", and my teenage son, who said today “All books are self-help books”. Couldn’t agree more.
At DevOpsDays Mountain View I was lucky enough to get some time with Michael Rembetsy, Director of Engineering and Operations at Etsy, which manages to be PCI-DSS compliant while practicing continuous deployment. In this short interview, he describes how they do it.
I recently ran into the situation in which I couldn’t get PKA to work when SSHing into my Ubuntu server. I hope this article helps somebody out. It was driving me bonkers.
Somewhere along the way our industry shifted this discussion into a tools discussion & now the amount of noise out there about “DevOps tools” is magnitudes higher than any discussion about the real reason DevOps exists – to shift culture.
It is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes. The primary advantage of using phoenix servers is to avoid configuration drift.
In our Enterprise Continuous Delivery Maturity Model we looked at the idea of continuous deployments to production and flagged the process as “Extreme”. It’s just too much for too many teams. A decade ago, I might have said the same thing about continuous integration.
Net Applications updates the Browser Wars stats — currently IE still hanging on strong with 54% of the market share while Chrome is creeping up on Firefox’s 2nd place lead (19% to 20%, respectively).
Its really not that hard; you just need someone to take a breath and plan. The part of monitoring that sucks is the human part, and since your app will not tell people when its up and down, you need a person to think about that for you.
A good discussion came up at DevOps days about whether or not development shops should just eliminate operations if the organization has small-scale IT needs.
Development and Operations are both critical to IS/IT usage in an organization, but developers often look at operations as something alien – from another planet (and operations have the same view on developers). As we'll see, this couldn't be less true.
Apache Mahout is a scalable machine learning framework that can be used to create intelligent applications. In this article we’ll see how Mahout can be used to create personalised recommendations within a Grails application.
Culture is like quality. You don’t build culture, or quality, by talking about it. You build it by doing things, by acting, by making things happen and making things change, and reinforcing these actions patiently and continually over time.
Since several of the commands require having write access to ‘root’ folders we need to run ‘puppet apply’ as a super user using sudo.
Operations teams are tasked with stability and uptime. That means working against change, limiting or slowing it down where possible.
A straightforward, whiteboard presentation of how the DevOps cycle works in the enterprise. Jody Hunt of BMC explains...
These reports are great and it’s easy to configure but you need to make both a dollar investment in the software and an education investment to really understand the metrics and how they relate to code quality. What’s nice about StatSVN is that it’s free and it doesn’t take a lot of thinking to use it.
We wanted to establish a list of some of the best Twitter personalities to follow about DevOps, web performance, and development. So here's a list of 10.
In the software world, development and QA are often organised into two separate teams. Some issues may bounce between the teams multiple times before they reach resolution and the release can ship. As a developer, this has always struck me a hugely inefficient workflow.