Warning: This post is outdated. It is here for reference purposes only.

This is the first of what will likely be a few posts about developing BCS Group's automated backup and restore system for all the websites we manage, which is currently around 30 Joomla! sites. This initial post will cover the overview of this massive project; the next posts in the series will likely cover these general topics:

• Setup Your Dev VM (Part 1) - Initial Install of Debian
• Setup Your Dev VM (Part 2) - Network, sudo, and SSH
• Setup Your Dev VM (Part 3) - Install packages
• My site backup process
• Overview of SSH and asymetric encryption (as I understand it, I'm no expert!)
• Example setups of Jenkins CI jobs
• Unit Testing, and why you should do it
• Maybe some more as I think of it...

Continue Reading

Many people are familiar with the CASE statement in SQL Server but I do not see examples of using it like I do so commonly for some of my reporting tasks. This post assumes the reader has a working knowledge of CASE statements.

Continue Reading

Warning: This post is outdated. It is here for reference purposes only.

Continue Reading

If you are writing code I would assume that you're always writing it for a purpose. Sometimes the purpose is only to experiment or learn but you always have a purpose. You are creating something, solving a problem, or doing something fun. More importantly, your code should have a purpose and a reason to need to be written in the first place.

The first thing you [should] ask is "How will I know that I have solved the problem?" If you don't, how do you know when you're done? Also, what if The Problem was solved but you (or someone else!) just made a change elsewhere in your code base and now your code broke. How would you know? More importantly, WHEN will you know? Will you find the bug before your code goes out the door, or will you have a customer complaint about a bug that should have been discovered months ago?

Continue Reading

My dad taught me as a young child that there are different tools that are appropriate for different jobs. Don't use that flat-head on a Philips head screw. Is that a nail? No? Then why the heck are you using a hammer?

As a programmer I find that more than ever, the right tool for the right job is vital for productivity. About two years ago I switched to a MacBook Pro as my main machine and I couldn't be happier. For me, that's one of my "right tools", I love it and I have no plans on switching back. There are occasions where I feel the difference in trying to find a cheap/free tool to get something done where a slew of options are available for PC users, but I can't say it has affected me too much. Throughout a given day I will likely use a huge assortment of tools, below is my list of frequent tools that I use pretty much every single week for various tasks as a programmer.

• NetBeans IDE
• Notepad++
• SourceTree
• Git
• BitBucket
• Microsoft SQL Server Management Studio (SSMS)
• VirtualBox
• Firefox
• Firebug
• Chrome
• Internet Explorer
• Filezilla
• Mantis Bug Tracker
• Trello
• Jenkins
• Phing
• Kompozer
• MySQLWorkbench

Phew, that's 18 different tools, and only a couple (such as Kompozer) don't get used every week. Sure, 3 of them are browsers and it doesn't include iOS Safari, but I have tasks I can only do in IE (shudder), I prefer to use Firefox for web development, and I use Chrome as my searching browser to keep Firefox from having 30 open tabs. This is just a quick list of what I happen to be using at this time, I'm open to suggestions to try as well!

What are your favorite tools for the trade?

Continue Reading