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. Mon, 06 Sep 2010 11:01:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 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”.

]]> By: GrahamBrooks http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/comment-page-1/#comment-5214 GrahamBrooks Tue, 24 Nov 2009 19:12:53 +0000 http://watchitlater.com/blog/?p=67#comment-5214 Mr T ;), I see this effect as part of a general lack of zooming of perspective during development. Quite often teams are under pressure to deliver functionality as quickly as possible and a possible instance of Reckless debt (http://martinfowler.com/bliki/TechnicalDebtQuadrant.html). A symptom of not thinking there is enough time to mould the code back into a consistent architecture. Graham Mr T ;) ,

I see this effect as part of a general lack of zooming of perspective during development. Quite often teams are under pressure to deliver functionality as quickly as possible and a possible instance of Reckless debt (http://martinfowler.com/bliki/TechnicalDebtQuadrant.html). A symptom of not thinking there is enough time to mould the code back into a consistent architecture.

Graham

]]> By: Jim Barritt http://watchitlater.com/blog/2009/10/reading-code-vs-searching-code/comment-page-1/#comment-4993 Jim Barritt Mon, 26 Oct 2009 14:18:42 +0000 http://watchitlater.com/blog/?p=67#comment-4993 Hi Tom, I have also observed this and, also wondered about its dark side, with very similar set of concerns that you mention here. I would actually say that Eclipse positively encourages a "flat" package hierarchy because its flattens package structure and "hides" classes in the navigator view by showing them inside source files. You might aswell have one massive package! This is one of the reasons I favour intellij, the package view is much cleaner and makes me want to explore it rather than trying to hide it away and use CTRL-T all the time. So +1 from me at least. Jim Hi Tom,

I have also observed this and, also wondered about its dark side, with very similar set of concerns that you mention here.

I would actually say that Eclipse positively encourages a “flat” package hierarchy because its flattens package structure and “hides” classes in the navigator view by showing them inside source files. You might aswell have one massive package!

This is one of the reasons I favour intellij, the package view is much cleaner and makes me want to explore it rather than trying to hide it away and use CTRL-T all the time.

So +1 from me at least.

Jim

]]>