News for hackers. Stuff that matters.
Re:Embrace technical debt by apinstein on Wednesday July 29, 2009 @12:27PM (#730306)
Interesting article. I think using viscosity to compare languages or frameworks is counterproductive, but the general idea is useful when talking about software architecture and development.

For instance, I used to manage some poorly architected Java apps where even trivial changes incurred painful re-architecting because the app was poorly written. And I've managed PHP apps that are extremely well-organized and are very simple to add functionality to.

The other thing I'd mention is I like your idea about hitting the wall where improvement freezes b/c the implementation time is so great. I think it's a good fit for the technical drag model -- that is the point of terminal velocity!

It's another good-fit for the metaphor; eventually you can only drive forward a product by making the team bigger because your project hits its terminal velocity (or top speed) for the given "engine" size (the team).

Re:Embrace technical debt by swombat on Wednesday July 29, 2009 @12:33PM (#730331)
One problem with that concept of adding developers as increasing the size of the engine - I don't think it works like that. When development freezes, good developers end up losing interest eventually, so in reality what probably happens is that your productivity decreases - so in fact you probably start regressing, if you let yourself hit that point.
Re:Embrace technical debt by apinstein on Wednesday July 29, 2009 @12:48PM (#730371)
Agreed. I didn't say adding developers proportionally affects output, and this is true with engines as well.

A particular engine architecture scales proportionally up to a point, but then gets harder to get a little bit bigger. Same is true with dev teams...