Comments on: Reading code Vs searching code http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/ A reluctant foray into the world of blogging. Thu, 17 May 2012 02:38:18 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Tom http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/comment-page-1/#comment-12690 Tom Thu, 01 Sep 2011 11:58:16 +0000 http://watchitlater.com/blog/?p=67#comment-12690 Easier to navigate but I'm not sure about managing structure, unless you actually view the structure after navigating to the class/code/file. Easier to navigate but I’m not sure about managing structure, unless you actually view the structure after navigating to the class/code/file.

]]> By: Sana Jeffries http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/comment-page-1/#comment-12658 Sana Jeffries Mon, 29 Aug 2011 16:44:13 +0000 http://watchitlater.com/blog/?p=67#comment-12658 It might have a dark side, but it is much easier to navigate and manage the structure. Sana Jeffries Webmaster www.bulbamerica.com <a href="http://www.bulbamerica.com/philips" rel="nofollow">Philips Bulbs</a> It might have a dark side, but it is much easier to navigate and manage the structure.

Sana Jeffries
Webmaster http://www.bulbamerica.com
Philips Bulbs

]]> By: Tom http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/comment-page-1/#comment-5220 Tom Wed, 25 Nov 2009 11:59:07 +0000 http://watchitlater.com/blog/?p=67#comment-5220 Hey Graham, I forgot about reckless debt, though I have been trying to attribute some of this behaviour to value fetishism (had to use that in a sentence). Some teams are now quite good at red-green-red-green software delivery, and can turn out code like a machine. However its supposed to be red-green-refactor (or at least red-green-reflect), but that seems to get lost in the rush to deliver "value". Unfortunately that leaves teams accumulating tech debt that may not ever be addressed, or actually using tech debt as a passive-aggressive mechanism of not actually dealing with an issue that is 'too hard". Hey Graham, I forgot about reckless debt, though I have been trying to attribute some of this behaviour to value fetishism (had to use that in a sentence). Some teams are now quite good at red-green-red-green software delivery, and can turn out code like a machine. However its supposed to be red-green-refactor (or at least red-green-reflect), but that seems to get lost in the rush to deliver “value”. Unfortunately that leaves teams accumulating tech debt that may not ever be addressed, or actually using tech debt as a passive-aggressive mechanism of not actually dealing with an issue that is ‘too hard”.

]]>