In time for the holidays, I've added some books I've been excited by recently to my recommended reading list:https://meaningness.com/further-reading
-
-
1. Precisely defining the scope of work takes more effort than doing the work. 2. Asking customers what they want in a new product is as accurate as examining pig entrails. 3. Thus building and iterating is by far the most efficient approach
-
4. But if you are building and iterating, then customers are in a perpetual state of only partial satisfication and partial frustration, while engineers in a perpetual state of changing requirements.
- 2 more replies
New conversation -
-
-
You optimize what you measure. Engineering faults (crash, leak, ...) are measurable. Incorrect (or not useful) behavior are not. Very obvious in, eg, Apple, esp since mass telemetry. Few actual crashes in Apple code, but lots of "behaves incorrectly/stupidly"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hiring ethnomethodologists, to study clients as they use software and later help with respecification sounds like an interesting idea.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.