Twitter
Software Development Do’s and Dont’s by Michael Ceranski focuses on the points to consider and the pitfalls to avoid during software development.
Never write code with the intention that you will fix it later. This is true especially when we set out to write using a prototyping model. The prototype that we create often tends to get used when in fact it was supposed to be a throw away. What happens next is that since it was a prototype to begin with, it starts suffering the symptoms of improper design, coding, etc.
Think large write small. It takes a truly experienced software developer to anticipate the scalability and extensibility of a software project.
Don’t over design. Often we tend to get lost in the jungle of trying to create a truly abstract piece of design considering all the possible changes that the software project will tend to undergo. This might mislead us to over design a system, which creates so much complexity that it beats the original purpose of abstraction. Keep the software design as simple as possible so that it performs it’s job correctly with minimal code.
Code is not self commenting. I kind of argue with this point considering that a lot of good code actually does tend to be self commenting. Writing good code minimizes the need to write documentation to explain it.
Software is never finished, it is only abandoned. Any software project can always be improved upon with new features, fixing of bugs, optimization or refactoring.
Related Posts:
Tags: today's read
Hi, just visited your blog first time, and found it quite interesting. Nice post indeed. Thanks for sharing it to all
Regards
Rama
Software Development Company Luck now
[Reply]