- Not understanding the user's needs. Lack of user input, or not even asking.
- 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 will fall 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 a stressed 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 were getting ridiculous amounts of errors everywhere... turned out the developer couldn't spell and would declare variables with incorrect spelling.. no big deal, 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 you kicked off the development project, and possibly out of the company. You might want 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 on your application instead of your server, but you have put your database at risk of data integrity issues, and getting bad data! Some of my hipster cool friends are always saying "It's alllll good", well, if your database can be caught saying 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.
Extract - Software Development Top 30 Mistakes
2008.07.13. 20:38 takacsot
Szólj hozzá!
Ajánlott bejegyzések:
A bejegyzés trackback címe:
https://takacsot.blog.hu/api/trackback/id/tr21776116
Kommentek:
A hozzászólások a vonatkozó jogszabályok értelmében felhasználói tartalomnak minősülnek, értük a szolgáltatás technikai üzemeltetője semmilyen felelősséget nem vállal, azokat nem ellenőrzi. Kifogás esetén forduljon a blog szerkesztőjéhez. Részletek a Felhasználási feltételekben és az adatvédelmi tájékoztatóban.
Nincsenek hozzászólások.
