1,500 karma · joined May 30, 2008
https://shorturl.at/S1awK
Are you confusing Test Unit documentation with 'How/What to test' documentation? I can't think of any documentation required if what you use is a group of asserts.
Test::Unit in a nutshell: `test "should do something"; ...; end` is what gets run in each of the files. `setup` is called before each test. `teardown` is called after each test. use `assert_*` at your discretion.
That's certainly how most of tech-workers are treated. However - should they? Even for non-degree bearers (or those like me transitioned from other fields), it's a highly creative non-mechanical work. The notion of treating tech workers as blue-collar ones is I think stemming from the black-box sophisticated nature of work (and perhaps introversion of many in the business) which the industry bike-shed into previously known moulds.
This is wrong.
- Woman: "It's You! Picasso. Could you please paint me?"
- Picasso: "Here you go Madam!"
- Woman: "Wow! great picture in only few seconds. How much do I owe you?"
- Picasso: "$5,000"
- Woman: "That's outrageous. It only took you few seconds"
- Picasso: "Madame, it took me my entire life!"
Unverified story about value-based pricingRelated: http://www.youtube.com/watch?v=3Ueg7Q7hO7U http://www.youtube.com/watch?v=QwpWaLrDHnU
There was another prank but couldn't find it
Further explanation in this video http://www.youtube.com/watch?v=nFC8uQfJgDo
In this case process overrode rationale; and was cheered as a result on its own.