StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>Which is more important: writing the code right, or writing the right code?</p> </blockquote> <p>At first glance, this might seem like a "which came first, the chicken or the egg?" question but it isn't. If I absolutely have to compare these two, then I would think "writing the right code" is more important. But what is even more important than these two is this: "Writing the code right, for the right code to be written"</p> <p>Why I think writing the right code is more important? It's because the "writing the right code" decision has to come first, then you can "write the code right" for that. Both of these logically should not conciously happen in the exact same time. Real Example would be: In Sprint Planning the PO decides "what" needs to be done - which is the "right code to be written", and during the Sprint the Team "writes the code right" for the "right code to be written", in the right order of priority.</p> <blockquote> <p>What are your experiences, what balance would you recommend and why?</p> </blockquote> <p>I have also coincidently seen the correct user story being worked on in a bad quality way, but it luckily produced huge gains for the business. And I've also seen really high quality code product being scrapped. This all may be coincidence, but there are certain concepts which may make this observation be seen more often. For eg. a concept/practice called "gold plating" where a development Team spends too much time polishing up the code, to a point where even senior developers think it is unnecessary, when what the Team really should do is, move to the user story next in priority. On the other hand, a team which spends very little time refactoring may produce buggy software quickly and it may even bring profits to the business, but "Technical Debt" would eventually kill them, if not now then a few years later, and the loss due to that may be double of the profit they might have made initially!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload