Archive for the 'Methodology' Category
How to suck at software development (Part 1)
1. Don’t create prototypes
Clients do not know what they want. Managers do not know what they want. When you prototype, you learn about the constraints you are going to face and your audience learns what they can have and what is impossible. NOTE: Try not to use your prototypes for production code, they are meant to be prototypes. Learn from them and don’t just….
2. Copy the code
When you copy code one of these scenarios is likely to occur: either you don’t fully understand what it does or you may know but don’t think about refactoring it to be better because you expect it to just work. I know many of you out there see this all day long: someone copies code because they are lazy and don’t correctly create an abstraction, and they end up violating the DRY (Don’t Repeat Yourself) principle. Now when rules change, you have multiple pieces of code to change. Unfortunately, it seems that people who copy code also tend to believe that they should…
Popularity: 1% [?]
6 comments
