…maintain real code in real world, according the engineering principles it's very very hard. Not impossible, but difficult.

You are completely right but not because code or engineering is hard. You are right because doing a good job at anything is hard. Being a good teacher? Good God, it’s Sisyphean. Being a good musician? 6+ hours a day for years. The code world is special perhaps in that it’s still so wide open. It’s been talked and written about at length; managing code processes can make things worse, some hackers are geometrically more productive than others and it’s hard to see why, adding manpower to a code project can dramatically slow it down.

Anyway, you said nothing controversial. Being good at anything is difficult. It’s why so few things in life are nearly as good as they could be. And why, back to musical examples, some makers can churn out musical instruments that won’t last a year in real use while others makers can and have created instruments that have already lasted hundreds.

I commend this to you as an exploration of some of the governing issues: Thinking about Thinking.

In reply to Re: Good programming practices and changes in requirements: how to maintain good code by Your Mother
in thread Good programming practices and changes in requirements: how to maintain good code by DanBev

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.