Most software need saving data. Sometimes that data is predicted to be small and hundreds or thousands of transactions on it will not be needed at the same time.
I was at the Web Directions South conference the other day and you know what really struck me? There is a lot of very cool, very connected stuff either here now or coming very soon. Hackable stuff!
I’ve been wondering for a few years now, why it’s so hard to get companies to prioritize the work that I feel is important. I mean, I’m telling you how to do it and you aren’t listening - don’t you want to build quality software?
When I started following along the devops movement often times the phrase “delivering value” would appear in conversation. That made me ponder even harder on a question that had haunted me for quite a while already: who, as an ops person, am I delivering value to?
Kris Buytaert gives us an in-depth rundown of forthcoming DevOps events around the world.
If you managed to read my last blog you'll remember that I demonstrated a simple script for creating a new tomcat installation on a server by splitting the tomcat binaries from the conf files, storing the binaries on a FTP server and the conf files in version control, with a script recombining the two parts.
"Whoever defined nano as the default crontab editor for Ubuntu deserves a whipping with a rusty chain."
Rubytune has put together a reference sheet of DevOps-y command-line tips dealing with process basics, memory, disk/files, network, and more.
In my role as a software developer, Iʼm often asked to automate existing business processes and transform them into computer systems.
At JavaZone, Jevgeni Kabanov talks about building a full clustered environment and a deployment pipeline -- so that commits to the trunk update a live chat server.
Let's continue our serie of interviews with people who had and continue having major influence on the definition of technical debt and its implementation in software development projects. Philippe KRUCHTEN, software engineering professor at UBC, who directed the development of the RUP (Rational Unified Process), explains his vision of technical debt and how to manage it, in order to take right decisions at the right time.
This JavaZone session provides an object lesson in using continuous delivery for build, test, and deployment.
In his new book, Antifragile, Nassim Taleb discusses the behaviour of complex systems and distinguishes three kinds: those that are fragile, those that are robust or resilient, and those that are antifragile.
I was running in to a problem with a Java project that occured only in IntelliJ Idea, but not on the command line, when running specific test classes in Maven. The exception stack trace had the following in it...
Lots of VMs, even Linux, all ready to be Azured...
This fast-paced video session from JavaZone functions as an introduction to networking fundamentals for programmers.
A colleague, Logan McGrath, has a blog series that scotch-tapes Perforce, Sinatra and AngularJS into a functional app. Another Colleague, Addison Lee, wrote a quick client polling example for it in Java.
Parsing script or function options and non-option arguments is easy in Bash with getopts but there are some catches, such as the need to reset OPTIND. We will se how to do it using getopts, shift, and case.
In real-time operational contexts, it’s important to monitor system metrics for major swings in value. Such swings, whether upward (“pops”) or downward (“drops”), often indicate a problem either on the horizon or else in progress.
Mat Schaffer continues his series of tutorials on Chef Server...
Seeing that my Linux box is running low on free space I decided to remove all unused Linux kernel images on my Ubuntu 10.04 system.
On the recommendation of J.B. Rainsberger I’ve been reading ‘Reality is Broken‘ – a book which talks about how we can apply some of the things games designers have learned about getting people engaged to real life.
Following up on his tutorial on getting started with Chef Solo, DevOpsCast's Mat Schaffer helps you install your Chef Server.
The traditional app delivery process has many drawbacks: outdated infrastructure, lack of tools, etc. The app delivery process is severely constrained by those drawbacks and ultimately it can negatively impact business.
Jacob Orshalick has a nice article up at TechWell asking “How lean is your development platform?”