(no subject)
Jun. 18th, 2002 12:55 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ravencallscrowsBleh. Lunch break during training classes. Don't really have anything i want to eat, so i'll probably just continue checking mail and doing the odd bit here and there on the web.
Grumble of the moment about test training sessions like this one: Don't just define and illustrate what something is, tell me where to look for it and why it's a bad thing. If i hear one more person define "buffer overrun" today without giving a practical clue as to where to look for one in a product (not in something written specifically to contain one, so that it can easily be shown off) i think i'm going to throw things. Yes, they're bad. I understand in theory how they can be exploited, but if i'm supposed to spend the next three weeks looking for them all over the place, show me at least one place to look for them in a full fledged application instead in a text-based app that runs from the command line.
As with most things specifically designed for testers, this seems to be long on theory and short on practicality.
I don't know. Maybe it's different from the perspective of the individual application teams, since they deal with the components on a more intimate level than Setup does. Or maybe it's just that I'm too jaded with the whole thing to really be able to see anything beyond the most basic applications for what we're being taught.
Grumble of the moment about test training sessions like this one: Don't just define and illustrate what something is, tell me where to look for it and why it's a bad thing. If i hear one more person define "buffer overrun" today without giving a practical clue as to where to look for one in a product (not in something written specifically to contain one, so that it can easily be shown off) i think i'm going to throw things. Yes, they're bad. I understand in theory how they can be exploited, but if i'm supposed to spend the next three weeks looking for them all over the place, show me at least one place to look for them in a full fledged application instead in a text-based app that runs from the command line.
As with most things specifically designed for testers, this seems to be long on theory and short on practicality.
I don't know. Maybe it's different from the perspective of the individual application teams, since they deal with the components on a more intimate level than Setup does. Or maybe it's just that I'm too jaded with the whole thing to really be able to see anything beyond the most basic applications for what we're being taught.
