Software Development Top 30 Mistakes
I have been developing software and web applications for nearly 11
years now. Software development has come a long way since the days ofBinary, Cobol, etc. What still fascinates me about software development is thesame mistakes made before, are still made today. Below are the top 30 Mistakesthat are made within thesoftware development process. It's amazing tosee that none of these have anything to do with the language itself.
*Not understanding the user's needs. Lack of user input, or not even
*Underestimating the size of the project
*Rushing through the planning stage, or avoiding the planning all together. Code first, plan later! BAD!
*Not testing early enough, often, or at all! Make it a habit!
*Choosing the "Cool" methodology at the time, vs. one that has worked in the past. Which leads into my next point
*Not using a methodology
*Letting a software developer run the software development project
*Bored, unmotivated team! You have to motivate your developers! If you can't motivate, don't bother trying to lead. Your team willfall asleep, literally
*Planning on catching up later. You won't... don't even think it !
*Non Source Control! Ouch.. not good people... and no, just installing a software package is not it
*Deciding to switch your development tools when you’re already into the project
*Allowing feature creep. Just say NO! Everyone will be happier in the end
*Omitting necessary tasks to shorten the project plan. Really what's the point of doing this?
*Insufficient management controls in the development project
*Lack of high level business sponsorship
Adding people at the end of the project to "speed things up" You will only slow things down
*No unit testing. Heck if you can do it, use Visual Studio Team Foundation Server and set up some automated testing nightly
*Stressed out software developers. If you have managed to perform even one or two of these software development mistakes, you will have astressed out bunch of programmers to deal with!
*Lack of error handling
"Off by one" errors. These happen a lot during the software development process.. *sigh.
*Typos... Just use option strict and explicit please.. during one software development project, which I was on as a consultant, they weregetting ridiculous amounts of errors everywhere... turned out the developercouldn't spell and would declare variables with incorrect spelling.. no bigdeal, until you use the correct spelling when you're assigning a value to it... and you had option explicit off. Ouch to them...
*No understand the deployment or hardware the software is to be installed on. Ohhhh it's for a Macintosh... lol. Well hopefully not that bad, but you get the point
*No naming style or code conventions. Honestly it doesn't matter what you use... as long as you are consistent with the rest of the team, and hopefully at least yourself
*Using global variables everywhere. These are NOT your friend and hog memory like nothing you have ever seen before!
*Not asking for help at all during the software development process. If you’re stuck, don't fight with it for hours on end! Ask for help!
*Not commenting your code
*Hogging all information to yourself. You think you're more valuable this way? You're actually not and there is a plan brewing to get youkicked off the development project, and possibly out of the company. You mightwant to brush up your sign "Will code for pizza"!
*Performing database operations at the application layer instead of the database layer. Not only is this putting the processing juice onyour application instead of your server, but you have put your database at riskof data integrity issues, and getting bad data! Some of my hipster cool friendsare always saying "It's alllll good", well, if your database can be caughtsaying this... and If everything looks good to your database, then you should be!worried. It is NOT all good
*Not validating your data! Yikes... Yes.. let’s just assume all the data is perfect! NOT!
*No load testing. What.. This is supposed to run on 1,000 user's machines through Citrix? Interesting... Shouldn't be an issue! lol... NOT