As part of my role at a new company I’ve been asked to provide feedback about structuring Dev & Ops as well as what sorts of things work and don’t.
The essence of software engineering, in my opinion, can be captured in two words: managing complexity.
Test Driven Development, Behaviour Driven Development, Extreme Programming and many other new-age hippie methodologies have spread through the dev world like wildfire. I believe there's room for one more.
On Friday Nathan and I were setting up a new virtual machine and we needed a firewall rule to be created to allow us to connect to another machine which had some JAR files we wanted to download.
At deployment time, we’re worried about a new set of dependencies. That web application probably depends on other components in order to function properly.
Everything in getting my personal site setup went fairly smoothly, including updating my registrar’s DNS records to point my domain name at my hosting provider.
I make a lot of jokes at work about code review karma. Here's the idea: each time a person volunteers to review others' code, that person build their code review karma.
As IT systems become an important competitive element in many industries, technology assets are influencing more and more parts of any organization.
Eric Minick from urbancode supplies a slideshare on managing build time dependencies.
In our Fabric code we make use of Boto to connect to the EC2 API and pull back various bits of information and the first time anyone tries to use it they end up with the following stack trace.
As I write this, I’m sitting in a half-empty office in London. It’s half empty, you see, because it’s snowing outside, and when it snows in London, chaos ensues.
Earlier in the week, I presented a webinar on managing build time dependencies which is now available as a recording.
I have a client who is very firm on the idea that the user should know what went wrong when exceptions are thrown.
Etsy Labs' fantastic Code as Craft series explores Etsy's strategies for moving fast at scale.
Some of the ugliest things that happen to code don’t have anything to do with technical debt. They’re the result of conscious and well-intentioned design changes.
I’ve just published the first version (consider it a beta) of my logging library to the official nuget server(s).
You’ve probably heard of Gene Kim, Kevin Behr and George Spafford before. They are the three amigos responsible for The Visible Ops Handbook, which can be found in the book pile of every good IT operator.
We wanted to tail one of the log files simultaneously on 12 servers this afternoon to try and see if a particular event was being logged and rather than opening 12 SSH sessions decided to get Fabric to help us out.
We had our scrum of scrum meetings last Wednesday where all scrum masters meet up with our line manager to discuss issues, bottlenecks and success stories of our previous sprint.
"Here's a five minute video demonstrating how some fun features of my Maven VirtualBox plugin, such as creating a box from some configuration, provisioning it and running integration tests against it."
A Garbage Collection analysis of a PCGen - a large Java swing desktop application that supports character generation for role-playing games like Dungeons and Dragons.
London Stansted Airport, early afternoon – a huge crowd at the railway station. No trains – only people, and a lot of confusion and anger.
Today I updated mac ports and a new error started to show up at the command line saying that the __git_ps1 command is not found.
You're using Postgres.app on a Mac for local development but are getting SQL errors from your application. You're seeing an error message.
We now have the logs coming from CloudFront, Web/App and Search tier to the centralized log storage in Amazon S3. In this final post of this series, let's now see what are the options at storage level from cost point of view and what to do with mountains of logs.