The last few days have been rough on the d.trio blog. Those of you who were watching, and I know some of you were because you emailed or called (Hi, Les, thanks), know that sometime early Monday this blog, well, imploded.
I’ve been working with web files and sites and blogs for a long time now and I know that sometimes things just go sideways. Technology is usually my friend, I’m usually pretty smart about it, but there are days, yes, there are days where things go so badly wrong that the only thing you can do is start over. So, that was Monday. I discovered that our website and blog were both down at 11:11 a.m. and so began a very long day. If you are reading this, we have obviously recovered. Mostly.
Sometimes disaster brings the opportunity to make some changes, so I’ve implemented a new look for this blog and done some general cleaning up. It’ll be an ongoing process so please excuse our dust for a little while. The major thing you’ll notice is that not all of the images are back in place. This will take me a couple of days, but they will return, I have every confidence. All of the content is still here (ALWAYS BACK UP YOUR DATABASE BEFORE YOU MAKE ANY CHANGES) but things work a little differently, if you notice anything about the new blog layout that you hate, please let us know.
Thanks for your patience and for letting me vent a little bit here. In the mean time here’s what I’ve learned:
1. At least one person reads this blog regularly
2. Always back up your database
3. Every time you make a major update, something will break, new technology will require you to do something in an entirely different way than you used to. Expect it.
4. The best way to get my coworkers to leave me alone is to stare intensely at code on my screen. Or maybe it was the whimpering.
5. Backup more often than you think is strictly necessary.
6. Tech support people don’t want to talk to you just as much as you don’t want to be talking to them.
7. The opportunity to change everything should always be taken advantage of.