![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Tags:
Tags:
In spite of how many hours I've spent on this bloody thing, it feels strange to realize that we're fast-approaching Version 1.0!
I've got contact information for all of my Beta Testers except one.![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
kat_denton, I've sent an email to what I *believe* is your address. Can you please let me know when you get it, so I can be sure I have a way to get the Beta Test package to you?
I've got contact information for all of my Beta Testers except one.
kat_denton, I've sent an email to what I *believe* is your address. Can you please let me know when you get it, so I can be sure I have a way to get the Beta Test package to you?Tags:
Alpha Test phase completed! And 5 days ahead of schedule!
Thank you to my two Alpha testers, RagonDev and Mysteque, and togryphonrhi for looking over the user documentation for me!
( Cut the rest for those of you who don't give a damn ::G:: )
Thank you to my two Alpha testers, RagonDev and Mysteque, and to
gryphonrhi for looking over the user documentation for me!( Cut the rest for those of you who don't give a damn ::G:: )
Tags:
Tags:
Anyone care to submit suggestions for an icon design that can be done in a 16x16 grid, for a program that will help design the curriculum of a martial arts school?
All that I'm really coming up with so far is something like a yin/yang design, or maybe a compass rose.
Any ideas?
All that I'm really coming up with so far is something like a yin/yang design, or maybe a compass rose.
Any ideas?
Tags:
Tags:
Have you ever wondered what Nirvana for a software developer would be like?
Steve Yegge can tell you. ::sigh::
Along the way, he also shoots large gaping holes in such fairy tales as Agile Development, Pair Programming (has anyone ever actually seen this work?), and other myths.
Steve Yegge can tell you. ::sigh::
Along the way, he also shoots large gaping holes in such fairy tales as Agile Development, Pair Programming (has anyone ever actually seen this work?), and other myths.
Tags:
Tags:
With many thanks!
Alpha Testers:
Ragondev, Mysteque. Time frame: Oct 15 - Nov 4
QA Testers:
saxononyx, themouseketeer. Time frame: Nov 5 - Nov 11
Beta Testers:
gryphonrhi, kat_denton, Mysteque. Time frame: Nov 12 - Nov 18
If anyone wants/needs to change their role, or if Life jumps up and smacks you, please just let me know -- it won't be the end of the world. ::S::
Thank you all!
Alpha Testers:
Ragondev, Mysteque. Time frame: Oct 15 - Nov 4
QA Testers:
saxononyx, themouseketeer. Time frame: Nov 5 - Nov 11Beta Testers:
gryphonrhi, kat_denton, Mysteque. Time frame: Nov 12 - Nov 18If anyone wants/needs to change their role, or if Life jumps up and smacks you, please just let me know -- it won't be the end of the world. ::S::
Thank you all!
Tags:
As most of you who read this know, I am a software developer. As you also know, I am in my final semester of school, and am working to create a program for use designing the curriculum for a martial arts school.
Part of the formal process of software development includes testing by people other than the developer(s). This is typically done in three stages: Alpha testing, Beta testing, and QA testing.
As used here, Alpha testing is the early testing of individual pieces to confirm that they function as expected. Beta testing is looking over the proposed finished product as a whole, confirming that all pieces function as expected. QA testing is looking over everything and trying to find ways to break it. ::G::
I currently have one person who has volunteered for Alpha-only testing, one for Beta-only testing, one for both Alpha and Beta (requires separate machines), and one for QA testing. This is enough to get by, but more would be welcomed.
Here is what would be involved for each role:
Alpha tester -- I will send you an executable program and one or more test plans. You run the program, go through the test plan, and send me your results and feedback. Time frame: October 15 - November 4.
QA tester -- I will send you an executable program and documentation. You read through the documentation (and suggest any edits), run the program, and see if there is anything you can do to cause the program to crash or otherwise malfunction. Time frame: November 5 - November 11.
Beta tester -- I will send you an executable program, documentation, and a set of test plans. You read the documentation (and suggest any edits), run the program, go through the test plans, and send me your results and feedback. Time frame: November 12 - November 18.
If you feel like volunteering for any or all of the roles above, please let me know! Once I've gotten a look at how many people are volunteering for which roles, I'll get back with you with confirmation and further details.
Thank you!!!
Part of the formal process of software development includes testing by people other than the developer(s). This is typically done in three stages: Alpha testing, Beta testing, and QA testing.
As used here, Alpha testing is the early testing of individual pieces to confirm that they function as expected. Beta testing is looking over the proposed finished product as a whole, confirming that all pieces function as expected. QA testing is looking over everything and trying to find ways to break it. ::G::
I currently have one person who has volunteered for Alpha-only testing, one for Beta-only testing, one for both Alpha and Beta (requires separate machines), and one for QA testing. This is enough to get by, but more would be welcomed.
Here is what would be involved for each role:
Alpha tester -- I will send you an executable program and one or more test plans. You run the program, go through the test plan, and send me your results and feedback. Time frame: October 15 - November 4.
QA tester -- I will send you an executable program and documentation. You read through the documentation (and suggest any edits), run the program, and see if there is anything you can do to cause the program to crash or otherwise malfunction. Time frame: November 5 - November 11.
Beta tester -- I will send you an executable program, documentation, and a set of test plans. You read the documentation (and suggest any edits), run the program, go through the test plans, and send me your results and feedback. Time frame: November 12 - November 18.
If you feel like volunteering for any or all of the roles above, please let me know! Once I've gotten a look at how many people are volunteering for which roles, I'll get back with you with confirmation and further details.
Thank you!!!
Tags:
Does anyone have information on how to use the two following items in TRS-80 Basic (or similar), circa 1983?
1) EXP(variable name) i.e. LET X = EXP(Y)
2) ! i.e. IF X < 4! THEN PRINT X
I know that the first one is an exponentiation function, but the only thing I can find on using it says, "raise e to the power of Y". Except there is no "e" mentioned!
As for 4!, my brain keeps trying to read that as "4, factorial" but I don't think that's right.
Anyone?
1) EXP(variable name) i.e. LET X = EXP(Y)
2) ! i.e. IF X < 4! THEN PRINT X
I know that the first one is an exponentiation function, but the only thing I can find on using it says, "raise e to the power of Y". Except there is no "e" mentioned!
As for 4!, my brain keeps trying to read that as "4, factorial" but I don't think that's right.
Anyone?
Tags: