Test Driven Development is a tried and proven method of software development that helps you validate your work as you code. Previously I’ve talked about the benefits of TDD, and why it is successful. I could continue with an Intro to TDD, but I’ve found other sources that do a great job already of explaining the process. Instead, today I’d like to focus on best practices which lend themselves well to TDD, and if you aren’t following them already, they could make you a better programmer!

Imagine your office is in a rural part of the country, and your base of operations covers over 16,000 miles. It can be challenging to find the workforce that you need. When you’re in the position to look for talent in a competitive field like IT – the struggle is even greater.

Many of the websites we build require some variation of a search feature. Whether the website targets consumers or other businesses, if you have a robust product offering, you want a robust search to match.  

There seems to be a market these days in selling success.  It seems like many LinkedIn users (and to a lesser extent Facebook users) just cannot stop themselves from repeatedly posting about the “Secrets to Success” or the “X Number of Things Super Successful People do Every Day.”  It’s enough to posit the question of whether these people get paid by the number of secrets they publish. 

Let’s say you have a new employee starting. The list to onboard your new hire might include some introductory meetings, a training schedule, and of course setting up their computers or workstations. The time spent setting up a workstation is often considered just another cost of doing business. If you’re a business of about 100 employees or more, it would not uncommon to set up 2 or 3 workstations a month. And if you’ve been in business for a while, the time comes around when you need to make a large purchase to update your machines. The 2-3 hours it takes to prepare each machine adds up quickly.