I am a software developer, I can give you a fake scenario:

let's say you make a program that saves where wifi networks are located on a map interface. You set on a map some pinpoints, and it will remember what wifi network to choose when you are near those pin points. It gets your location based off your GPS.

lets say when you are at the home location, always try to connect to the wifi network called "MyNet".

OK. you are the developer, and you write this little app, and guess what? it works great!!! you are so excited that you quickyl throw it on to the extras-devel so that everyone can enjoy the app you made!

suddenly emails come flooding in:
when the wifi network is down, it doesn't stop trying. you forgot to add code to only try X amount of times.

when the password is wrong, it doesn't stop trying, it hammers the network and won't pause long enough for you to change the password.

turns out that one of the files that it needs comes from one of the extra packages you installed separately (QT 4.6 or whatever) and your program doesn't 1. Tell people that this dependency is needed or 2. Prevent people from installing unless this is installed

If you are in range of 2 wifi network locations at the same time, it will disconnect one, then go to the other, then disconnect that one, then connect back to the other in a constant back / forth untill youare out of range of both.

When you are typing in your wifi network encryption, you totally forgot to add WEP encryption,and you only programmed WPA. I guesswhen you developed it, your network used WPA so you never even considered WEP.

You never included a manual override to turn it off, the only way to turn it off is to un install the app!!

When you programmed the uninstall, you tell the program to delete all the files that were in use, however this accidentally includes the QT 4.6 dependencies!! now other apps dont work!!


the possibilities are endless. As a programmer, you need to think of all of these, but hey we're all human, and sometimes there are scenarios (known in the programming work as "use cases") that were either never considered, or not thought of as possible.

You made the app for you, and it worked for you. Iron out all the bugs from extras devel first.

I personally feel once its out of there and into extras-testing, the program should be safe, because it means most, or all of the major problems are taken care of, and small glitches may exist here or there.

hope this helps.