Skip to main content

What a Difference an Hour Makes

I was at a meeting recently where employees of a company were told that the billable rate was based on them working a 42 hour work week.  There's the expectation that a 40 hour work-week is the minimum hours required to work, below standard.  Working the 42 hours will ensure the company is making the correct amount of money on the employee.

Didn't sound like such a big deal, it's only 2 hours a week, right?

Then I began thinking about it some more.

2 hours over 52 weeks (yes, there are 52 weeks in a year) works out to 104 hours.  In more simple terms, that's about 2 1/2 extra weeks of work, more than half a month.

I was reminded of something I used to do quite often.  I'd say that the care has a whole bunch of time little problems all piled up and around each-other (in other words, it's majorly broken).  Little things can add up to huge things in very little time (maybe that's why I love square roots, they're a constant reminder of this fact).

So, I've only mentioned bad things that can come from this strategy, what about the good ones, right?

Think about those two extra hours.  If you're performing a job you really love and recognize as making a difference, what's a few more hours?

2 hours a week could be two meals shared.  It could be a phone call to everyone in your immediate family to catch up.  2 hours is all it takes to prepare and hand out sandwiches to the homeless.

In short, two hours can change lives.



Cindy said…
When I find I have a spare hour, I spend it catching up with friends by calling them or writing email. I call people at very random times because I don't want them to have to listen to a screaming child in the background. Which is why most people get emails.

I've thought about volunteering when Alex gets a little older. To show him how great it can be. All I would need is an hour here or there.

It's crazy when you think about how much time you might "waste" doing nothing. I'd really love to read more, but I just don't seem to have a nice chunk of time to be able to sit and just read.

Will there ever be 30 hours in the day? Either that, or I should start getting up at 5am so I can have a few hours to get stuff done.

Popular posts from this blog

Advantages and Disadvantages of Using Microsoft Access

I've answered this question in some form or another far more times than I care to count.  Most often it's a question of "why do I need a fancy Web application when I can just build this myself in two days in Access.  I mean, the data's already in Excel."  So I figured I'd post out what I threw together, I know I've missed some points. Overview Microsoft Access is an ideal solution for relatively small datasets and a limited number of users. From the Microsoft Web site: “As a desktop database, Access is well suited for small, departmental applications. These applications may start as one user’s project. For example, an employee realizes that productivity can be increased if a paper-based process is automated with an Access application. Other users in the department recognize that they can take advantage of the application if additional features are added. As more features are added, more employees run the application. As time goes by, more and more Access

Beryllium Spheres

I'm sitting here at home watching The Shadow , easily one of the best movies made based on one of the best old time radio shows.  I hadn't picked up on this earlier, but the weapon used to destroy the city is none other than the same power source used to power the NSEA Protector in Galaxy Quest . I never knew Beryllium was so cool.  Now I want a sphere of my own. Anyone know of other places Beryllium Spheres are mentioned? Peace, +Tom

Red-Gate SQL Compare

Every now and then I come across a program that becomes so ingrained in my daily work that I hardly know how I'd get by without it.  I'll probably break down a couple over the next few days, but for database work, I have never found anything as good as Red Gate's SQL Compare and SQL Data Compare .  Essentially these tools let you compare two SQL Server databases (all objects, users, permissions, functions, diagrams, anything) and update changes to whichever database you want.  This is amazingly useful for deploying database changes to a test or production environment (do it to production with ridiculous care, even though it will generate a SQL Script for you and run all updates in one transaction), and making sure everything is synchronized. For releases we can just generate the compare script, confirm that the changes match the updates we want to go out, and store it all in one place with the release details.  This is true for both the structure and the data, to