Profile_bird

Hey there! KentBeck is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving KentBeck's updates.

Already using Twitter
from your phone? Click here.

KentBeck

  1. @bigallan seems weird to me too. it's a form of insurance. i'm just wondering if it meets an existing need.
  2. @marick you don't follow talks, brian, they precede yours. fortunately this doesn't freak *everyone* out :-)
  3. @southda correct.
  4. @elharo my take: checked exceptions force me to say things i'm not sure about and that i don't care about in the intervening methods.
  5. sorry my earlier question was unclear. if someone was worried about the authenticity of junit, could i sell them the md5 hash?
  6. Michael Nielsen on learning learning http://bit.ly/qFCEN applies nicely to software development teams
  7. does anyone give away software but sell the digital signature for it?
  8. @mark_menard right, and my point is that it's best to reach that moment as cheaply as possible
  9. @southda put in the quality that increases feedback. defer the rest. that's what satisfies the business needs of release 0.
  10. good @wingedpig quote: "the technology can be duplicated but your users can't"
  11. @dbrock the purpose needs to be clear but usage can be clunky in release 0 & you (the product developer) will still get valuable feedback.
  12. release 0 needs to be clear but not necessarily easy. if users aren't eager enough to figure it out, you don't have the seed of a product.
  13. i still overengineer release 0.0.0. feedback trumps sustainability as the probability of the code living until tomorrow approaches zero.
  14. @aerabati exactly. and all those hardwired values give you a nice to-do list to make the code real.
  15. if i just can't get a test to run, i'd best hardcode absolutely everything and then replace constants with expressions one at a time
  16. just sludged a big batch of chevre. turns out temperatures in cheese recipes are *not* suggestions. bacteria don't respond to negotiation.
  17. NanoHTTPD to the rescue! my test now runs with a minimal of hassle. tx Jarno Elonen
  18. the fundamental principle behind kanban--if you have too much too do, you get less done.
  19. @philoUK congratulations!
  20. @aldosolis de nada.