Skip to main content

Diaper Review

Since we had the babies, we've used 4 brands of diapers: Pampers, Huggies, Costco and a white label brand. If I had to rank them in order of effectiveness, Pampers comes first. Costco is second followed by the white label diaper. Huggies are the absolute worst. Now I haven't tried Luvs but it'll have to really suck to be worse than Huggies. Fortunately, all the huggies diapers we've used were received as gifts. The rate of failure of the adhesive (in the size 1 version) was higher than that of the white label brand. The absorbency of the diaper itself left much to be desired. I'll say about 75% of the time the baby's butt was wet (which means the pee was not being absorbed completely by the diaper). So regardless of price and value, I will not be buying huggies. Each time we receive huggies as a gift, I am tempted to throw them out. That's how bad our experience with huggies has been.

The babies were started on Pampers Swaddlers from the hospital. And I have to confess they are the very best in disposable diapers. The material is very very soft and the absorbent crystals work exceedingly well. The diapers absorb so well that sometimes it's hard to tell whether or not the diaper is wet. The rate of failure of the adhesive is 0% (works all the time) and some of the diapers even have an indicator strip that tells you when the baby is wet. Sounds like a minor deal but it helps eliminate one potential cause when a baby is wailing.

In terms of price, Pampers was the most expensive. However it wasn't that much more expensive than the Costco brand. The difference was about 6 cents. That doesn't sound like a lot but when you calculate how many diapers a baby goes through in a single day, that 6 cents difference adds up to $175 per baby (8 diapers a day * 365 days). Multiple that by 2 (twins) and that's $350 each year!

The white label brand was by far the cheapest but it left a lot to be desired in terms of softness and fit.

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…