News for hackers. Stuff that matters.
Re:The Number One Trait of a Great Developer by brador on Tuesday September 03, 2013 @09:09AM (#6320672)
Maybe we should be asking why the things we make need to be maintainable. Why can't I just make program module x to input a and output b and never touch it again.

I believe modular code is the future and the sooner we get there the better.

Re:The Number One Trait of a Great Developer by sanderjd on Tuesday September 03, 2013 @09:44AM (#6320876)
Here's how I read your comment: why do we worry so much about making things maintainable - why don't we just make things maintainable? Building a system out of small modules is what makes it maintainable.
Re:The Number One Trait of a Great Developer by dangerlibrary on Tuesday September 03, 2013 @09:14AM (#6320702)
Because at some point f(a)->b will need to be very slightly different, and it won't make sense to write f(b)->b' for performance reasons.
Re:The Number One Trait of a Great Developer by rodly on Tuesday September 03, 2013 @10:54AM (#6321299)
Because x(a) -> b might need to be understood by everyone working with your module at some point. What if you leave the company and someone inherits your module? What if they decide to change their codebase and need to rewrite your module?

Writing modular code doesn't magically give you maintainable code either. It needs documentation, proper use of design patterns, and needs to be readable.

Re:The Number One Trait of a Great Developer by __--__ on Tuesday September 03, 2013 @10:02AM (#6320983)
What do you do when bugs show up in that module? rewrite it from scratch, introducing god knows how many new bugs? Or only address bugs when a rewrite of the entire module is necessary?