Hmm, posted directly after my application...I hope I didn't disqualify by rushing my application.
Oh well, we'll see.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Hmm, posted directly after my application...I hope I didn't disqualify by rushing my application.
Oh well, we'll see.
Originally posted by gzav
bug: A defect or difficulty, as in a system or design.
In this particular area of computer science, it is used to describe a defect in the code or routine of a program.
see, i can describe a bug!! so, am i in?
(aaargh, the waiting is killing me, my fingers hurt because im crossing them so much to give me a better chance in getting picked for the beta!!)
In my work, i use this instead of that:
Error: the programmer mispelled something that introduces an error in the program.
Defect: an error that haven't manifest (an error in the code, for example, it is there, but you haven't seen it).
Bug: the defect manifested. (the system hangs for example)
You need to trace the Bug to find the Error, and probably by doing that you will find Defects that you haven't noticed, BUT, you will surelly introduce more Errors.
Last edited:
Well...2º beta aplication form will be there waiting for us
P.S. Johan...any new Eu2 beta for version 1.07?? The last has more CTD's than the previous one.
P.S. Johan...any new Eu2 beta for version 1.07?? The last has more CTD's than the previous one.
hmmm ... i don't think i used complete sentences to describe my reasons/qualifications -- just clauses (at most) seperated by semicolons. ah well ...
Dear lord - I almost missed it - i've been watching this forum since the beginning and I can't believe I nearly missed this - whoo...
anyway, it says it closes the 10th and today is the 10th- so I hope I got my app in under the wire
anyway, it says it closes the 10th and today is the 10th- so I hope I got my app in under the wire
In addition to writing and testing the software our company produces, I also do some tech support since we have a fairly small user base. Most of the calls are along the lines of....
me: What happened?
user: The program shut down
me: Was there an error message?
user: A box came up
me: What did it say?
user: Don't know, I didn't write it down
me: What were you doing at the time?
user: I'd just clicked a button
me: Which button?
user: Not sure, one of the reports. Or it might have been in data editing.
me: OK, start the software up again.
user: Oh, I'm not at the computer. I just thought I'd give you a call in case you knew what was causing the problem. Do you have any idea?
By this time I'm usually ready for a drink
Originally posted by soracia
In addition to writing and testing the software our company produces, I also do some tech support since we have a fairly small user base. Most of the calls are along the lines of....
You too, eh? well.. i don't don tech support any more.. but boy was it ever fun. yeah woohoo, fun. Did that for two years.
about the writing in the explanation or motiviation.. if i had only known! I figured I should keep it short and brief.. considering they would have tons of applications to go through. bah.. i thought i was being considerate! eh well. whatever will be will be.
i did exactly the same...
In every beta I did the same... just briefly explain my interests and why I should be selected...
And it looks like a lot of people did the same, so you are not alone.
Originally posted by Generalisimo
i did exactly the same...
In every beta I did the same... just briefly explain my interests and why I should be selected...
And it looks like a lot of people did the same, so you are not alone.
At least now you guys know what to put in your application the next time the beta for Victoria comes around.
there go's my chance.
maybe its for the best like i said before good luck too all betas.
make sure we get a great game.
Originally posted by Generalisimo
In my work, i use this instead of that:
Error: the programmer mispelled something that introduces an error in the program.
Defect: an error that haven't manifest (an error in the code, for example, it is there, but you haven't seen it).
Bug: the defect manifested. (the system hangs for example)
You need to trace the Bug to find the Error, and probably by doing that you will find Defects that you haven't noticed, BUT, you will surelly introduce more Errors.
That's more than two sentences so you might just be in!
Ahh...well i'm sure i didn't make it...*snif* ....i thought the shorter the better. (*but there is still hope until the email comes )
(*but there is still hope until the email comes )
btw Johan, does blatantly sucking up to you work or would you rather prefer discreet yet insightful remarks about how great you are?
because i can do both!
because i can do both!
Originally posted by gzav
btw Johan, does blatantly sucking up to you work or would you rather prefer discreet yet insightful remarks about how great you are?
because i can do both!
I chose bribery
