Skip to main content

Fatherhood Tales

One of the ubiquitous things in our living room, in addition to all the baby changing stuff, is a notebook that we call the "baby book". This notebook contains a record of our babies' lives. We record who ate what, when and how much. We record who was changed when. We record who weighed and measured what when. We record who pooped and when. We record who took what medicine and when.

Why all the note taking? When we first got home, we had all these time-sensitive things we had to keep track of:
  • babies need to eat every 3 hours
  • babies need to poop once a day (or we call the doctor after 2 days)
  • my wife had to take 2 medicines: one every 4 hours and the other every 6 hours

At first, I tried to use the alarm on my cellphone. So basically, I would set the alarm for 3 hours after feeding the babies. That quickly turned out to not be sustainable. So we came up with this simple idea of a notebook with 3 columns:
  • who did it
  • what was done
  • when it was done
Now if I want to know when the babies last ate, I just look it up. If I want to know why Dara is so cranky, the baby book tells me she hasn't pooped in 1.5 days. If I want to know when my wife can take another dose of motrin, I just look it up. If I want to know what Toni weighed at the last doctor's visit, the baby book tells no lies.

Of course, the accuracy of the baby book depends on accurate and timely data entry. So to visitors, it might look like a crazy and perhaps over the top thing to do. But so many times, the baby book has come to our rescue. Without it, keeping track of the little things would have been overwhelming.

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply