3 ms·

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 aga

• dangerlibrary 13y ago
  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.
• blindhippo 13y ago
  You can believe all you want, but please develop code with your head in the present. What you said is akin to saying: "sure, the code we wrote is slow, but we can fix this with hardware in a month - Moore's Law!". That doesn't help anyone - it's just wishful thinking. Apply a bit of brain power and make your code simple and straight forward so that your customer doesn't waste time and effort maintaining it (or more likely in the "Rockstar" case, replacing it entirely).
• sanderjd 13y ago
  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.
• __--__ 13y ago
  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?
• rodly 13y ago
  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.