We learned the hard way that baby could be colic (with increased crying during evening hours) due to intolerance to cow’s milk/soy (via mother’s milk). It took us couple of months to get there (first stopped milk products and subsequently soy) and I wish we had known earlier. I’ve been meaning to write a blog post with the hope to help someone run through these possible causes as part of diagnosing the colic crying early on.
>Though it would seem to follow that consuming less fat would lead to being less fat, that’s not quite what the science says, at least when it comes to dairy—even if whole milk is more caloric than skim.
It mentions about some scientific reason for it but then talks about bunch of high level case studies and that's all.
On a side note, I find most of these case studies a scam, where they exaggerate and manipulate numbers to make it sound scary or utterly interesting for reader's attention.
I think programmer tried to be defensive by ignoring an edge case. He either was lazy in searching for its documentation (<= 1999 you know) and tried to be over-smart to avoid "Out of Range" exception in test/production. Or he didn't consider looking at documentation like some of us do.
He may have given it a shot by running it several times to see if it actually generates the number provided as an argument.
Sharing explicitly versus gaining access to your data are completely separate things. Moreover, how about pushing your professional data to these sites? I don't want to use separate tools for ideas which I'm fine if someone steals them and which not..
This looks like a great tool.. but for these kind of sites, I always feel uncomfortable to signup and then store my personal information in their databases. I could easily end up giving them my personal ideas and my professional work related stuff.. We really don't know who is looking at our data on other side and what kinda security measures(if any) they are taking to secure the same. Your thoughts?