1,013 karma · joined April 4, 2010
> The amount you're talking about is the one commonly used by body builders who are using steroids
Sorry what? Those of us who lift and are trying to grow muscle take more protein, but don't just lump us in with steroid users. https://examine.com/nutrition/how-much-protein-do-you-need/ is an evidence based review on the subject.
Source?
How do you feel about just starting with tests that are actually more of a specification? For example, I'm starting to feel that unit tests aren't something we should be writing, but are something we should be generating. We should be writing things like QuickCheck specifications. So the first test I'd probably write is:
given x. y. add(x, y) == x + y
This is a specification that is essentially tested against a "model" (native addition, in this case).
If you want an analogy, consider this like studying jazz or something. Sure, you could just notice a II V I progression and call it done, but if you pick away at each individual note, you can find a whole lot more going on behinds the scenes.
Basically, I don't really consider what's happening in the blog post a bad thing. It just has a time and a place, and you need to be aware when it's the wrong time.
That said, I'd read some of Edwin Brady's research, as he is actively trying to find the intersection of "business programming" and dependent types: https://edwinb.wordpress.com/publications/
But that doesn't mean we took the best path. There is always an alternative future if x hadn't happened at all. If x hadn't happened, we might be in a better place, rather than accepting it and doing the best we can.