Tuesday, September 18, 2007
Tuesday, September 11, 2007
In Memory
For the first time in my life reality surpassed anything my imagination could think of. Thoughts of car crashes, sickness where totally erased by complete shock. I collapsed half way down the stairs and just sat there in shock. After that I don't remember a single word of the conversation. I know we consoled each other. I remember turning on the tv in disbelief and watching the pictures play. I remember my mother-in-law calling in a panic because my sister-in-law took the subway under the towers every morning. I remember finally reaching my sister-in-law hours later and finally breathing a sigh of relief.
Today is in memory of those who perished and those who's lives were touched. Today I think of my friend who didn't celebrate his birthday that year. Of my step mother-in-law who had to run from the cloud of dust as the towers collapsed. Of my grandfather who's retirement party was at the restaurant on top of the tower and who's heart was broken that day. Of skies that were eerily quiet. Of the shock when the first plane flew over my head again. Mostly I think of all those we lost and send them and their loved ones a prayer of support.
Monday, September 10, 2007
Monday Organizing
- Business - Work on the Ruby on Rails tutorial 1/2 hour day this week.
- Home - Get both cars emissions tested ASAP! (One is about to be overdue!)
- Personal - Do at least one thing relaxing just for me. Maybe reading in a nice bubble bath.
- Family - Pick out and order Claire's new bed & bedding so we can transition from the crib before she realizes she's tall enough to climb out. (ACK!)
- Family & Friends - Finish the photo book birthday gifts. Work on them 1/2 hour day. (Also very very late.)
For more organizing I'm going to start working on a set rotating menu schedule so I don't have to think so much about what's for dinner. It will be based on flexible categories so I can fill in the details based on what's available at the farmers market and store. I'm starting with breakfast:
- Monday - Hot cereal & Fruit
- Tuesday - Cold cereal, Yogurt & Fruit (Busy AM)
- Wednesday - Waffle or Pancakes & Fruit (Make or frozen)
- Thursday - Cold cereal, Yogurt & Fruit (Busy AM)
- Friday - Hot cereal & Fruit
- Saturday - Cold cereal, Yogurt & Fruit (Farmers Market Morning)
- Sunday - Something fancy, baked yogurt, dutch apple pancake, etc
Finally I'm going to start rebuilding my routines for dealing with stuff around the house. If you need help with household routines my favorite site by a million miles is Fly Lady. I admit that I protested against a lot of the stuff on her site at first but wow she knows her stuff. It's the first organizing system that has had a chance of working for me. For my daily routine I will:
- Get up showered and dressed first thing
- Wipe down the bathroom surfaces every morning
- Spend 15 minutes clean one cluttered are of the house
- Do one full load of laundry every day
- Pick up the toys right after my daughter goes to bed
- Finish kitchen clean up (dishes, sink, counters) before relaxing for the evening
For a weekly routine I've started to put tasks on some days:
- Monday - Errands (Supplement farmers market food from the co-op, dry cleaning, etc)
- Tuesday & Thursday - Work AM if Claire likes daycare again (Now that's another post), Garden & Play outside with Claire in the afternoon
- Saturday - Farmers Market Shopping AM, Family Time in the Afternoon
- Sunday - Relax, Check Calendar for the Week, Think about new goals
Ok, off to take that shower that should have been first. In my defense I was up most of the night with a sick child. There was no way I was risking a shower right next to her room waking her until she was ready!
Thursday, September 6, 2007
If your computer crashed right now...
So what should you do in case your system dies?
- Back up everything you care about, frequently. It should be to a separate medium not attached to your computer. Preferably in a separate building or even a separate state. Mandatory if you live somewhere prone to natural disasters.
- Use source control for development. If you've never used it source control will keep track of your changes to a document over time. Every time you check in your changes it will save a snapshot of the documents current state. If you your computer crashes, you accidentally delete your document, or just decide you hate your latest changes you can revert back to an earlier version. If you set up your source control on a different computer then you have a backup of what ever project you are working on. This is useful for programming, web design, or any project where you will be making a lot of changes over time. I'm currently using cvs since it's free and I can store the main source repository on a computer I share with friends.
- Create a system restore kit. If your system is dead the last thing you want to be doing is tearing through your office closet looking for your OS install disk. You should have collected in one spot everything you need to completely reinstall your system at a moments notice. In a best case scenario you have fancy (expensive) backup equipment that lets you take a complete snapshot of your system. System dies you take your last snapshot and restore it to working order. Since most of us can't afford corporate backup systems the next best thing is keeping all your install cds in one place. Create a backup cd of any software you downloaded off the net. You never know when the version you downloaded two years ago will no longer be available. Include your latest backup of data and finally write a list of all the steps you need to take for a full system restore. If you're not sure write as much as you can. Better to struggle with it now, then when you are trying to recover from a crisis.
- Use VMware and its snapshot features. Do you wish you had the fancy corporate backup tools I just mentioned, the ability to restore a system by simply saying restore? How about a few extra test servers without paying for them? Does it sound to good to be true? Not with VMware Workstation. It's a program that creates virtual machines on an existing machine. At anytime you can create a snapshot of the virtual system and save it as an instant backup. I'm typing this blog on a windows box while my virtual linux machine is downloading updates in the background, one piece of hardware with two operating systems. I reinstalled it by restoring an old snapshot. If I'd had a recent one I wouldn't even need to download the updates. However there is a cost. The systems are sharing the same resources. My system is a few years old so it slows to a crawl if I start Outlook at the same time. I probably couldn't run more then one virtual machine at a time. However one is better then the 0 test systems I had before.
- Follow Through! This is where I should follow my own advice. A backup is useless if you don't do two things. First, test your backup. I can remember at least one case of a fancy corporate backup system that recorded a whole bunch of nothing. This was discovered the first time someone needed the data. Second, keep your backup up to date. Let me repeat so I remember myself. Keep your backup up to date. Maybe I should make myself write that 20 times on a blackboard. Now excuse me while I go spend the next couple hours rebuilding a system that I could already have up and running.
Tuesday, September 4, 2007
One Step Forward, Twenty Steps Back
Me: "Oh, I'll look but I just finished creating the user management system. I don't want to start from scratch again."
Friend: "This is going to sound insane, but Rails is so much better at that that it may very well actually be worth rewriting."
This particular friend is fairly practical. He's not the type to suggest rewriting just for the fad of the day. If he suggests it there's a reason so I decided to check it out. I did a quick scan of a tutorial. Oh my goodness! It's beautiful. It takes out all the mundane, annoying parts of web programming and makes them just happen while leaving you free to do the creative side of things. If it's as good as it looks I can throw away everything I've done except the database design and still save time in the long run. I just wish I'd listened to the first person who mentioned it to me. Starting tomorrow it's time to back up and restart. However I think I can make up most of the time in a week or two at most if it's as good as it looks!