I've always *preferred* the taste of UHT milk, especially on breakfast cereals. None of my friends will drink tea at my house, because I never buy pasteurised.
You've hit the nail on the head there. It's also partially because I'd probably have to do significantly more job hunting than I'm prepared to (and probably even relocate) to find one of those semi-mythical employers who value programmers who take the time to do things properly. So I'm fully aware that I bear my share of blame for the situation I'm in.
Wow. I'm in exactly that situation now. I joined a small startup a few years ago where all the code had been written by one of the company founders whose plan all along was to work on it until they'd built up a strong enough business to take on an actual programmer.
Whenever he gives me a job to work on, he's already done all the time scheduling and promising to customers, and instead of asking me how long it'll take, he tells me when it's got to be finished, adding "can you get it done in that time?". If I try to say no, he argues me down, saying he could do it easily in that time. And, just as you said, he probably could, but it would be an almost completely unmaintainable mess.
It's made worse by the fact that I'm having to estimate how long it's going to take *me* to modify *his* code, and he just doesn't seem to understand why it'll take me longer than him to do it! Picture a single file project, 20,000 lines of Microchip PIC assembly code, no function header comments, not even any vertical spacing to hint at which labels mark the starts of functions and which labels are internal to functions; chunks of code processing arrays copied and pasted for each array element instead of put in a loop (he seems to go to great lengths to avoid writing loops); lots of copies of functions differing slightly from each other where he didn't seem to realize he could have parametrized one function; functions with names like "CALC_MAIN1", "CALC_MAIN2", "CALC_MAIN3" etc.; and, on top of all that, no specification document.
Reading this back, I'm shaking my head at myself, wondering why I'm even still working here.
Haha, yeah. Just like the "holographic" Liam Neeson in Jeff Wayne's War of the Worlds stage show.
Over 9000.
You are Jim Lahey and I claim my £5.
So what have you done with the real Lord Apathy?
I agree entirely.
... and, of course, Slashdot bloody well goes and replaces the carriage return I put between "singular" and "phenomena" with a space.
Phenomenon: singular phenomena: plural
I've always *preferred* the taste of UHT milk, especially on breakfast cereals. None of my friends will drink tea at my house, because I never buy pasteurised.
Back in the 80s, Peter Murphy broke the sound barrier in an armchair just by listening to Maxell audio cassettes.
You've hit the nail on the head there. It's also partially because I'd probably have to do significantly more job hunting than I'm prepared to (and probably even relocate) to find one of those semi-mythical employers who value programmers who take the time to do things properly. So I'm fully aware that I bear my share of blame for the situation I'm in.
Wow. I'm in exactly that situation now. I joined a small startup a few years ago where all the code had been written by one of the company founders whose plan all along was to work on it until they'd built up a strong enough business to take on an actual programmer.
Whenever he gives me a job to work on, he's already done all the time scheduling and promising to customers, and instead of asking me how long it'll take, he tells me when it's got to be finished, adding "can you get it done in that time?". If I try to say no, he argues me down, saying he could do it easily in that time. And, just as you said, he probably could, but it would be an almost completely unmaintainable mess.
It's made worse by the fact that I'm having to estimate how long it's going to take *me* to modify *his* code, and he just doesn't seem to understand why it'll take me longer than him to do it! Picture a single file project, 20,000 lines of Microchip PIC assembly code, no function header comments, not even any vertical spacing to hint at which labels mark the starts of functions and which labels are internal to functions; chunks of code processing arrays copied and pasted for each array element instead of put in a loop (he seems to go to great lengths to avoid writing loops); lots of copies of functions differing slightly from each other where he didn't seem to realize he could have parametrized one function; functions with names like "CALC_MAIN1", "CALC_MAIN2", "CALC_MAIN3" etc.; and, on top of all that, no specification document.
Reading this back, I'm shaking my head at myself, wondering why I'm even still working here.
In AD 2101, war was beginning....
What does "mnemetic" mean?
Why not use the entirety of Wikipedia rather than a random sample? Surely a modern PC wouldn't take long to spellcheck the whole lot?
*I* didn't know that! Wow, live CDs are even more useful than I thought they were.
Why take two bottles into the shower when you can just Wash & Go?
-15 karma points for using the (non-)word "irregardless".
Submitter, type out 500 times: 'I will not type "then" when I mean "than"'
It's the part just after the encoded 2D bitmap of a circle.
I don't believe you - that pun surely *was* intended!
*BOOOM* adequately describes what my head did while trying to parse your post!
Toilet paper lasts much longer when there are no women living in the house.
But surely that's just another way of saying "It's impossible to create free Higgs Bosons".
And, of course, 'its' in my above post should contain an apostrophe.
You don't need to add an 's' to media to make it plural - its already plural.