Long Road - Setup Your Dev VM (Part 1)
Warning: This post is outdated. It is here for reference purposes only.
This is the second of many posts about developing BCS Group's automated backup and restore system, but is also the first of three posts that go over how I setup my development virtual machines. If you haven't read the first post, go ahead and check it out if you like! I'll wait.... That post also contains direct links to all the other posts in this series.
Long Road to the Right Solution
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...
Using SUM and CASE together
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.
New Blog Site!
Warning: This post is outdated. It is here for reference purposes only.
How Will I Know When it Works?
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?
Mastodon