Conversion Update

By on December 12, 2012 in

Tags: ,

Conversion has run in to a couple of snags… and has taken longer than expected. It’s a frustrating world where a “curly quote” can messup a database import script. But here is a little teaser shot.


How nice to be able to browse the archives by month!

As I mentioned in the first diary there will be some things to re-learn and figure out but we will be better off in the long run.

About Mike Hoefer

Mike has been an active member of Blue Hampshire from the early days, and currently serves as the managing editor.
View all posts by Mike Hoefer →

,

  • cblodg

    Much appreciated and your hard work will pay dividends!

  • TimothyHorrigan

    In my information technology management class at USC School of Buiness, I learned a useful rule of thumb for estimating how long a project like this will take.  You figure how long it should take if everything goes according to plan,  and then you go up to the next unit of time and multiply by 2, and that’s how long it actually will take (on the average.)  For example, if it should take 30 minutes, it will take 60 hours.  If it should take a week, it will take 2 months.  If it should take 3 months, it will take 6 years. This is not quite as bleak as it sounds: the next unit of time up from the year is the decade, not the century.

    • GreyMike

      hold true on a daily (or weekly, monthly, yearly)  basis in practical operation in the field.

      I can also report that in 100% of cases, project delays caused by events outside my control continue to be my responsibility.