Skip to main content

Retirement of the baby book

Several months ago, I wrote about the baby book and how it's become ubiquitous in our living room. What's the baby book? Read all about it. Anyway, a few weeks ago we decided to conduct an experiment (I suppose a hazard of having both parents with science background is being subjected to numerous "experiments") to see if we can go a day without using the baby book, keeping the babies alive and managing to remember who's pooped and who hasn't (seems like the first few months of parenthood is consumed with tracking your babies poop schedule. And of course taking photos). Well the experiment turned out to be a success for 3 reasons:
  • the babies are old enough now to convey hunger (the ceaseless crying is a big clue in figuring this out)
  • Toni is super regular with his #2 activities. Every morning after the first meal...let's just say Toni requires 2 diaper changes each morning
  • both babies have started switching from baby formula to craving for finger foods. In fact, Toni's sense of smell is so well developed all you have to do is bring food into the living room and he's on you like white on rice. And of course, where Toni goes, Dara follows. 
Since then we've stopped using the baby book. All in all, we went through about 4.5 notebooks and I am really glad we kept those records. 

Comments

Popular posts from this blog

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 sanityFirst, 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 can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

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 horri…