Below are a few resources I've found useful when doing TDD in iOS.
Rather than planning work out into projects or breaking work into time-boxed Sprints, Facebook developers do most of their work in independent, small changes that are released frequently. Facebook says that they follow Continuous Deployment, but it’s not Continuous Deployment.
What I really need are two things: A definition of software quality and a definition of a software defect. I think I’m starting to approach workable definitions of both.
Docker turned 0.6 over the weekend and is heading full speed toward a production-grade container platform. So here is my guide to get Docker 0.6.1 running on the DigitalOcean VM. Five minutes starts now!
If you are working as a middleware administrator or application support individual, you may have realized by now how crucial it is to have proper knowledge of the JVM along with a good understanding of the Java concurrency principles
In Maven, we have different lifecycles. By default, using Maven will help us to achieve test automation, but Maven phases help us to achieve the various stages, too.
In this screencast we’ll deploy a very simple Node.js web application to Heroku continuously with the help of the Codeship.
That Azure and GitHub work together like a charm … wow, this just blows my mind. All Microsoft services should be as easy to integrate with as this scenario makes it.
Last week, PuppetConf took place at the Fairmont in San Francisco, gathering Puppet users and enthusiasts from all over the world for five days of training, development and sessions.
This is the first in a series of articles about IT security. Part I highlights the importance of considering security during the whole software development lifecycle and enumerates and explains common security goals.
One of my tasks for this quarter is to deliver a draft of an update to the Eclipse Development Process (EDP) to the Eclipse Architecture Council for their review. The process that we follow is to open bugs against Community/Architecture Council (prefixed with [EDP]), discuss them, and then incorporate the discussion into the new version of the EDP.
Managing or prioritizing the backlog, re-prioritizing works in progress — these activities make up the most of a product owner’s work. That’s not breaking news, obviously.
For a programmer, anyone consuming his/her software is a customer. It's not wise to discount customers, as they are the life line of any product. Without them, even the most innovative concepts will fail.
GitHub stands to revolutionize the revision and management of writing something other than code: books.
As with any migration, this one has its challenges. Below you can find more about them and how to overcome some of them:
Kevin Dishman is ThoughWorks’ QA lead for a client I “rolled off” a few days ago. He prefers a different style of Java and Page-Objects for Selenium2 / WebDriver codebases.
What follows is a checklist of action items that we’ve found imperative for successfully taking your application to production. For the experienced, we hope you can use this guide as a refresher on best practices. For the newer folks, this is a must-read on how to ready your database for the big move.
Obviously, anyone interested in learning about continuous delivery could learn a lot from Netflix. Luckily, Netflix's own engineering manager Ben Schmaus recently wrote an article titled "Deploying the Netflix API" on the Netflix Tech Blog.
Anything that takes longer than ten minutes is not refactoring. That is a redesign.
I’ve been playing around with the Unix tar command a bit this week and realized that I’d memorized some of the flag combinations but didn’t actually know what each of them meant.
After playing around with calculating the eigenvector centrality of a sub graph I learned that this algorithm can also be used in ranking systems. This is applicable for network-based ranking systems as we can build up a matrix of teams, store a value representing their performance against each other, and then calculate an ordered ranking based on eigenvector centrality.
A great discussion on the DevOps Google Group yesterday posed the question "What is a 'DevOps Engineer' anyway?" The OP pondered this question after poring over job listings for "DevOps Engineers" or developer jobs with some form of DevOps in the requirements for the position.
Maciej Zawadzki, co-founder of UrbanCode, talks through a risk calculus that demonstrates that shrinking release batch size lowers risk.
It’s a lot harder to fix application security vulnerabilities than it should be. If you can make the case that there are serious security problems that need to be taken care of, where do you start?
I recently saw a great presentation by Joe Armstrong called “Systems that Run Forever Self-heal and Scale”. The talk is well worth watching, but here’s a few quick notes for a busy reader or my future self.