I recently had the honour of speaking at QCon New York in Dave Farley’s Continuous Delivery track, and was excited to find a real appetite for Continuous Delivery in New York.
I’ve been playing around with Vagrant a bit again lately and having installed it on a new machine was running into the following exception when I tried to run ‘vagrant up’ on a new virtual machine...
This talk by Daniel Schneller deals with man in the middle attacks against SSL and what you as an application developer can do about it.
How many bugs are reported by users, tester or devs after QA have finished their job? That’s a very interesting indicator that will keep your QA team in shape. After all, you pay money to find and fix bugs but not imitate testing. A huge number of reworks is an alarm bell. Your developers may end up fixing own bugs after QA checks, instead of developing new features.
This is a very basic example of using Spring MVC, REST and Spring Test Framework using Spring’s Java configuration.
Sirix is an open source XML storage system which is capable of storing and querying hierarchical data efficiently. It is especially well suited for flash disks (SSDs), taking into account fast random reads and log-structured sequential writes
Let's say you decide that the budget for "everything" is two point five kajillion dollars. Clearly, you don't want to just fork that money over to a roomful of developers and wait a year for something to happen.
Current monitoring tools are clearly reaching the limit of their capabilities. That’s because they are making some fundamental assumptions that are no longer true.
One of the challenges with the Jenkins job was that most of the fields on its deployment page were text fields, allowing users to free form text which was prone to errors.
Several testing tools have been developed in the bid to enhance software quality and reduce software development time. In the past testing was done manually using simple CLI (Command Line Interpreters) based tools.
Episode 22 sports a special treat: in case you weren’t able to attend DevOpsDays Silicon Valley 2013, we join forces with the Food Fight Show(again!) and the DevOps Cafe for the first ever “Food Ship Cafe!” We convene a group of DevOps household names (including the “fairy godmother” of DevOps himself!)
Explore the highlights of the new 1.8.0 version of Apache Subversion, which delivers a collection of features and enhancements designed to facilitate administration and deliver enterprise-class functionality without adding complexity.
The way we build distributed systems and platforms is changing through the the last 10 years. Recently, I was thinking myself about different technological options I used so far and came for some conclusions.
As the buzzword “devops” has been out in the market for quite some time now, there are a “jungle of tools” built and tagged under the DevOps category. But these tools can be differentiated from the way they function and at what point in time they can be leveraged in a software execution cycle.
"I've got this idea for game-changing software idea, what technology should I use?" These questions have disturbing expectations. There's a Gordian Knot of dependencies that's sometimes baffling.
Today’s example is about what happens when a login page is loaded securely, albeit embedded within an insecure page. This is a common security anti-pattern and you’ll see it on many sites.
From my statistics I know that 80% of my subscribed readers are using Google Reader. It used to be 90% before Google announced that they would kill Reader.
After reading this post I decided to see what my top ten shell commands are...
With DevOps bringing source control to configuration files and publishing to production servers being automated – bringing both code and configuration over on the same time, the difference between code and config has become less than ever (if it even exists).
You know it's a bad day when you experience all of these.
If releases are traditionally major events which require heroic efforts and present real business risk, reasonable people will try to do them less often. But with many business processes this instinct is exactly the wrong thing.
As a DevOps team, we’re trying to maintain our systems in an ideal state, using a whole bunch of tools that affect the state of our systems, sometimes in unpredictable ways. Let’s take a look at a closed loop diagram...
Good intentions can go awry quickly in the world of software development. Imagine this common scenario: there are multiple teams building related projects at the same company. At some point, someone realizes that these teams tend to generate a lot of duplicate code; why not create a common library?
Two colleagues of mine ask a very similar question for interviews, something that as a developer or as ops guys you might find yourself needing to do. Given a log file of a particular format, how many times does something occur in that log file?
Autonomy, mastery, and purpose are some key aspects of motivation at the workplace. What else motivates software engineers?