Visual bloody bollocks basic.
Aug. 14th, 2008 06:52 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sobriqueToday has been VBS day.
Been a bit grumpy, as when I'm concentrating on code, when I say "just a minute" that means – I acknowledge you want attention, but I’'m right in the middle of thinking about something, and will lose my train of thought if I stop right now, so please stand by.
Not "carry on talking at me, and asking me to respond meaningfully when I’m concentrating".
However this annoyance pails into insignificance:
"On Error Resume Next"
I’m modifying some code.
I have found some MONKEY has put this in, and … well, hadn't given it much thought.
It’s a great VBS hack. What it means, is if you right crap code, then the program should just BODGE ON ANYWAY.
Yeah. So … if I typo in my loop, such that it’s a runtime error (like for example, using "sleep(60000) rather than "wscript.sleep 60000") it just … skips that loop, and carrys on, neatly jumping over my "while" loops, singing "lalalaalala, no you don’t want to do that bit, I'll ignore it".
Which moron, designed a programming langage where this was EVEN POSSIBLE.
It is acceptable to have runtime errors, not crashing a program. It is acceptable when I write some error handling code, that explicitly defines the behaviour when I do this. So I can … try running a command, and if it’s not there _do something else, defined_ not just arbitrarily continue and pretend it never happened.
GAAH.
Been a bit grumpy, as when I'm concentrating on code, when I say "just a minute" that means – I acknowledge you want attention, but I’'m right in the middle of thinking about something, and will lose my train of thought if I stop right now, so please stand by.
Not "carry on talking at me, and asking me to respond meaningfully when I’m concentrating".
However this annoyance pails into insignificance:
"On Error Resume Next"
I’m modifying some code.
I have found some MONKEY has put this in, and … well, hadn't given it much thought.
It’s a great VBS hack. What it means, is if you right crap code, then the program should just BODGE ON ANYWAY.
Yeah. So … if I typo in my loop, such that it’s a runtime error (like for example, using "sleep(60000) rather than "wscript.sleep 60000") it just … skips that loop, and carrys on, neatly jumping over my "while" loops, singing "lalalaalala, no you don’t want to do that bit, I'll ignore it".
Which moron, designed a programming langage where this was EVEN POSSIBLE.
It is acceptable to have runtime errors, not crashing a program. It is acceptable when I write some error handling code, that explicitly defines the behaviour when I do this. So I can … try running a command, and if it’s not there _do something else, defined_ not just arbitrarily continue and pretend it never happened.
GAAH.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2008-08-14 06:08 pm (UTC)The problem is not it being possible; there are limited number of circumstances where one might wish to do it in a limited area of tested functionality.
The problem is that the code you are working on was written by an idiot.
no subject
Date: 2008-08-14 06:51 pm (UTC)Total gobshite. However, in the grand scheme, it's those little trinkets, love 'em or hate 'em, that allow "people" (meaning, people that ought not to write code) to "get the job done" (meaning, it compiles without errors, ship it!) on time and under budget.
Sucks. It's IT.
...oh wait isn't that a tad redundant, what I just said there?
no subject
Date: 2008-08-15 10:21 pm (UTC)However, I spend so much of my time in meetings, wrangling with IS, and doing systems/data analysis the Dev team should be doing that I can't remember the last time I wrote any substantial vba. On the basis it's the nearest thing to a proper Dev Tool we have, I miss it : (
no subject
Date: 2008-08-16 08:35 am (UTC)