Does working with good code make you a better developer or does it make you soft and reluctant to work with anything less than quality code?
Tell me more
×
Programmers Stack Exchange is a question and answer site for
professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
|
|
||||
|
|
|
I would consider a natural reluctance to work with bad code to be an asset. If you have that, it probably means:
Soft is probably a bad word. Frustrated might be a better description. |
|||
|
|
|
Better. It puts the good code ways in your subconscious, thereby influencing your future coding. The way the Treasure department trains its agents to find bad money, is to have them study good money. Then it's easy for them to spot anything different. |
|||
|
|
Is a very good thing and not soft at all in fact it's exactly the opposite. The soft or easy option is being satisfied with poor code. The hard option is always striving for quality code. Being exposed to good code can only be beneficial. |
|||
|
|
|
From my own experience, working with a good code lets you learn things, extend the existing good code with your own and feel happy. Working with a bad code may make you feel anger, frustration and apathy. If it's not, think again whether you consider yourself a good programmer... |
|||
|
|
|
The more you work with good code, the more it will rub off on you. Therefore, causing you to be a more efficient programmer. |
|||
|
|
|
Isn't it in the human race to strive for excellence? To push the boundaries? To settle for nothing less but the very best? Why should code be any different? |
|||
|
|
How long can you keep the code good? If you can maintain quality over a significant period of time, including changes to functionality, by frequent refactoring, you must certainly have developed a high level of skill. |
|||
|
|
