Post by earlofqb on Sept 20, 2005 22:49:39 GMT
My school has recently introduced a new lunch system, one to which surpasses all in its horrendous coding. Because of this, I've lost money, of which I don't have. To fix this, I plan to re-write the code (for free) and donate it to my school. If you paid 200 usd for broken code, wouldn't you want it fixed for free?
Anyway, this is all very developmental. On Monday, I'm proposing this to the principle, who may or may not pass it on to the school board. Until it is rejected, I plan to go with the idea that it'll be approved.
Anyway, this program must tie in with the database my school has, and it must be done with confirmation of user input. The details will be worked out later.
So, what I need are skilled VB programmers. QB programmers can be accepted, but your code must match up with the VB requirements. I'd rather this project remain entirely in VB, as a mixed language program is difficult, at best, to compile.
If you have any knowledge of VB, you can apply. If you don't know VB, you can apply as a tester. VB-skilled programmers will be devised into teams:
Database management: will work on interfacing the project with the database.
Documentors: will document all code as much as possible. This project needs to be able to be understood by people without VB knowledge, as after I graduate, they'll be the ones maintaining this program.
Debuggers: debug the code before submitting. As teams finish, they'll debug their code, then it'll be stored until a final debugging for the release.
Testers: similar to debuggers, except will handle no code. They will simply test the program until it breaks, or until a week after receiving it, whichever is first. They will receive a compiled code, which will run so long as their copy of Windows has the SDK redistributable.
Project managers: programmers who will interface between teams and convert the code as needed to link it together. Also refered to in the final stages as "compilers", as in the final stages, they'll interlock the code together.
Low-level programmers: commonly referred to as "script kiddies", they will create the backbone of the project. Their job will be to handle input/output, UI, calculations, etc.
Consultants/advisors: programmers who wish to help but indirectly. They will advise the programmers of issues with the code and help in case of any problems.
This project will be designed to be entirely "softcoded", nothing will be set as permanent. That means no constants, no static arrays, etc. Every setting will be stored on the database. Of course, these settings will be encrypted and password-protected. Further, an off-site storage will hold the information in case of a failure in the system. The biggest issue is that this be eternally upgradable. It also needs to be updated off-site (the sys admin can work with the program off-site if need be).
Unfortunately, the SDK for VB.NET requires a windows XP system, so anyone without such a system will have to apply as a tester. Others without XP who wish to help can apply as consultants/advisors, and we'll e-mail the source code as necessary. They'll have to hand-run through it, however they should be able to accomplish their job.
More details await those who join. I plan to have someone create a forum and website for this project, as it will need a massive team effort to get this working. If someone'd like to start on that, it would be most appreciated (I'll obviously need admin privlages on the forum). To apply, e-mail earl71972@yahoo.com and have the subject "VB Lunch Program: I wish to help". Applicants must list their name, e-mail address, preferred position, and years experience with VB. Applicants will receive a list of test programs they are to complete, and a listing of websites that host a free IDE for VB.NET and the SDK required. The results of these programs will determine their position if none is indicated (and possibly if one is and the applicant is very weak in that area).
Thank you, and code well.
Anyway, this is all very developmental. On Monday, I'm proposing this to the principle, who may or may not pass it on to the school board. Until it is rejected, I plan to go with the idea that it'll be approved.
Anyway, this program must tie in with the database my school has, and it must be done with confirmation of user input. The details will be worked out later.
So, what I need are skilled VB programmers. QB programmers can be accepted, but your code must match up with the VB requirements. I'd rather this project remain entirely in VB, as a mixed language program is difficult, at best, to compile.
If you have any knowledge of VB, you can apply. If you don't know VB, you can apply as a tester. VB-skilled programmers will be devised into teams:
Database management: will work on interfacing the project with the database.
Documentors: will document all code as much as possible. This project needs to be able to be understood by people without VB knowledge, as after I graduate, they'll be the ones maintaining this program.
Debuggers: debug the code before submitting. As teams finish, they'll debug their code, then it'll be stored until a final debugging for the release.
Testers: similar to debuggers, except will handle no code. They will simply test the program until it breaks, or until a week after receiving it, whichever is first. They will receive a compiled code, which will run so long as their copy of Windows has the SDK redistributable.
Project managers: programmers who will interface between teams and convert the code as needed to link it together. Also refered to in the final stages as "compilers", as in the final stages, they'll interlock the code together.
Low-level programmers: commonly referred to as "script kiddies", they will create the backbone of the project. Their job will be to handle input/output, UI, calculations, etc.
Consultants/advisors: programmers who wish to help but indirectly. They will advise the programmers of issues with the code and help in case of any problems.
This project will be designed to be entirely "softcoded", nothing will be set as permanent. That means no constants, no static arrays, etc. Every setting will be stored on the database. Of course, these settings will be encrypted and password-protected. Further, an off-site storage will hold the information in case of a failure in the system. The biggest issue is that this be eternally upgradable. It also needs to be updated off-site (the sys admin can work with the program off-site if need be).
Unfortunately, the SDK for VB.NET requires a windows XP system, so anyone without such a system will have to apply as a tester. Others without XP who wish to help can apply as consultants/advisors, and we'll e-mail the source code as necessary. They'll have to hand-run through it, however they should be able to accomplish their job.
More details await those who join. I plan to have someone create a forum and website for this project, as it will need a massive team effort to get this working. If someone'd like to start on that, it would be most appreciated (I'll obviously need admin privlages on the forum). To apply, e-mail earl71972@yahoo.com and have the subject "VB Lunch Program: I wish to help". Applicants must list their name, e-mail address, preferred position, and years experience with VB. Applicants will receive a list of test programs they are to complete, and a listing of websites that host a free IDE for VB.NET and the SDK required. The results of these programs will determine their position if none is indicated (and possibly if one is and the applicant is very weak in that area).
Thank you, and code well.