Fear and aversion are caused by sheer ignorance. When you gain knowledge on a competing framework, fear can turn in two directions.
If you ask most developers, they will tell you that working in maintenance sucks. Understanding and fixing somebody else’s lousy code is hard. It’s tedious. And it’s frustrating – because you know you would do a better job if you were given the chance to do it over and do it right.
Did the test fail due to an application bug or is it the environment? Once again, the dreaded chant of “it works locally” is taken up. What most people fail to understand is that the failing test is the first sign of a communication breakdown between developers and sysadmins.
Even if you think you’ve done a good job of explaining something, the receiver of the communication decides whether or not that’s the case.
Here's a node.js https module used to make a remote call to a remote server using https and BASIC authentication.
Automation testing plays a vital role in agile application development which is our topic of discussion in this article.
Sometimes you want things to escalate quickly and a storm of errors on your production system is definitely one of them.
Kohsuke Kawaguchi, creator of the Jenkins CI server, is attempting to get other open source projects and developers on board with him to drop support for Java 5.
Lately the proxy configuration of my network has been changed, and moved from a transparent proxy, that required no configuration, to a “standard” proxy which requires a configuration script. Unfortunately NPM doesn’t pick up the proxy configuration of Windows...
Languages like C# and Java enforce the everything-is-an-object paradigm. You can’t just write a function; you have to write member functions of an object.
A recent survey asked more than two hundred I.T. project managers a simple question: what is the greatest threat facing software-development projects today? Over ninety per cent of those polled replied with a single-word answer: zombies.
Last week I spent a couple of hours setting up a new service, dubbed BitSyncHub, that will accept POST requests from Bitbucket and synchronize a (Mercurial) repository with it's Github mirror.
You've probably read about those big name dotcoms that deploy new features to production up to tens of times a day. For most startups bringing features to production is still a manual, at best semi-manual process.
There was a new release of Juju this week, 1.11.3, that brought a “small feature” with a big impact on your AWS bill. You are now able to deploy multiple services on one cloud server instantly. Before Juju started a new server per service which resulted in a potentially high AWS bill.
How can developers and security people get along with each other better than what they tend to at present?
A couple of days ago, Synology released the open beta of DSM 4.3. Somewhere hidden in the release notes there was mentioned that the NAS now officially supports the hosting of GIT repositories. This is great news for all programmers.
Quality and productivity are, of course, important things. I certainly wouldn’t continue to practice Test-Driven Development if it added defects or took a significantly longer time to create functionality. But that’s not why I practice TDD.
A common feature in software systems is to allow users to define their own fields in data structures. Consider an address book - there's a host of things that you might want to add. With new social networks popping up every day, users might want to add a new field for a Bunglr id to their contacts.
For all Ruby applications you can use the cucumber gem. In the screencast we walk you through creating a basic Ruby project and installing cucumber using bundler.
My former colleague Anne Simmons recently wrote an interesting post in which she describes some of the reasons that she finds herself not wanting to write about technical topics.
If you are an administrator looking for an automated way to deploy Couchbase at scale, look no further - Chef is a great platform solution. Once setup, it is a very clean solution that can work across any number of physical, virtual, or cloud servers, no matter what the size of the infrastructure.
Until I started working on the uSwitch energy website around 8 months ago I had not really done any support of a production system so I learnt some interesting lessons in my time there.
So, you applied for your dream developer job, got an interview and thought it went well, but all you have to show for your effort is a rejection letter? Here are a few reasons why...
To demonstrate some of Scertify's features we performed such refactoring on a sub-project of Alfresco community edition, an open-source enterprise content management system. Doing so, we were able to suppress 25% of technical debt (11 days).
Working in an office surrounded by other developers -- each of us trying to solve the same problem independently -- feels like madness, so what stops us working together?