(no subject)

[telophase]

Salon.com article on a super-repo man - the sort that repos Learjets and fleets of helicopters. (There's a series of action-adventure novels in that)


Also am banging my head against my own code: working on code I wrote 5 years ago, and going OH DEAR GOD WHYYYYY DID I DO IT THAT WAY?!

Comments

[tessercat]

Sounds like an episode of Burn Notice! hee~

[jarodrussell.livejournal.com]

Once I build a time machine...and kick my ass five years ago for the same thing...you're welcome to use it.

[telophase.livejournal.com]

I haven't even done the thing I'm supposed to do yet - add an entry in the intranet calendar so people can check out items and list where the item will be during that time - because I keep getting distracted by the AWFUL AWFUL CODE.

[jarodrussell.livejournal.com]

Is this ASP/VBScript (never know what to call that) or PHP?

[telophase.livejournal.com]

ASP/VBScript, whatever it's called. :D Which I was learning at the same time I was coding the calendar app. Not that I'm any great shakes with it today, because I don't do enough coding to keep it fresh in my mind, but back then ... geeeaaaarrrggghhhh!!!

[jarodrussell.livejournal.com]

I was going to say, in my limited experience with ASP/VBScript, I don't think it can be made to make sense.

[telophase.livejournal.com]

I will admit the thing that I gave up on fixing for the moment is mostly coding-logic-related and not specifically the language. :D

I decided to put in a functionality that I had been meaning to since I coded it: when you make an error when logging something to the calendar and get sent back to the form, the info in the form fields isn't persistent, so you have to enter all the info in again. Only I ran into the problem of how I'd coded the date - you can enter it for today, or for a future date, or a range of dates, and to make the explanation shorter, I'd coded it in such a way that makes it damn hard to stick the previous info back in, and could easily have been done in a simpler way that is TOTALLY FRICKIN' OBVIOUS.

So at the moment, users only have SOME of the info persisting, which I predict will lead to wailing and gnashing of teeth! And I can't believe nobody complained about that for five years, because they all complained when the hours of the coffee bar were wrong on the intranet calendar believe you me!