- 2 comments //
I scarcely believe this needs to be said, but in addition to the fact that I am a lazy fuck, I feel very little motivation to take the time required to go back to all the old posts and fix dead links, references, and many other things that might not be working now that I’m almost on my fifth year (!) running this place.
If any of you want me to correct something specific, poke me and I’ll try. No guarantees though. :VBack to top
I refused to fucking look at a guide to solve it so it took me fucking HOURS of crunching numbers, considering it’s been years since I last worked on one.
Zero, you fucking bitch.
[End rant]Back to top
Did some cleanup on the sidebar. Been a couple of years since I stopped playing SMT Imagine so most of my stuff is not only outdated but probably no longer relevant. Also, because of the closure of the western servers, some friends’ blogs and links became inactive, so took those out too. Will be rewriting some stuff and probably changing the sidebar order soon.
Also took up a cosplay photography gig. Kinda want to see how far I can get with this because the cosplay community is seriously fucking underrepresented in my country.
- 1 comment //
Flame Haze Shana, Buddy Jesus and my small task force of GUNDAM Mobile Suits will protect my work computer from any intruders.Back to top
This coffin is an eyesore.
This coffin. This coffin. This coffin. This coffin this coffin this coffin this coffin this coffin this coffin this coffin this coffin THIS COFFIN!!
- 2 comments //
I’ve seen a bunch of compilations like these on various places in the web, but I’m listing these from personal experience. In no particular order:
- Getting asked by everyone and their bloody mother to fix their computers. This is by far, I think, the absolute worst of them all. Just the mere fact that I have a degree in ANYTHING related to computers doesn’t make me the family technician, assholes. Even more so considering that my degree is in SOFTWARE ENGINEERING (aka knowing how to program efficiently and effectively), not computer repair. (This is, more often than not, not just limited to hardware, but also virus-cleaning, installing updates, and ridding the computer of all the fucking porn you unwittingly stuck in the system because you didn’t heed our fucking warning NOT to use Internet Explorer.) To add insult to injury, it usually has to be done for free, quickly, efficiently and with extremely detailed explanations, because if there’s one thing these pricks do well, it’s being fussy and overly demanding.
- Incomplete error reports. For fucking Zeus’s sake, telling me that you found an error and telling me nothing is the exact same bleeding thing at all if you don’t tell me WHAT THE ERROR MESSAGE WAS. Apparently, the fact that I know how to program also makes me somehow capable of divining absolutely any and all errors, the exact cause, the circumstances of when it was triggered, and everything related to it just by you telling me that you got an error. Never fucking mind that a single software can crash in a myriad of ways with sometimes TENS OF THOUSANDS of error messages, or that due to hardware/software configuration it might be an error that only happens to you, or any of that shit. “I got an error, you have to solve it!” “But what kind of error did you get?” “I don’t know, I just know I got an error!” is way too common a conversation for my personal tastes.
- Users ignoring app documentation. Apparently, for the users, the Instruction Manual and Help documents are just there to occupy space and look pretty. And hence, the gods saw fit to grant unto us developers and unto sysadmins as well one of the most useful acronyms for when a (l)user asks a stupid question that’s already answered clearly in the documentation: RTFM. (Which translates to Read The FUCKING Manual — and yes, that fucking goes to YOU as well.)
- Deadlines (especially ones NOT set by us). Once I’ve agreed to develop an application or any other piece of software for you, it’s understandable that you may want to know when you can get your finished product. But when you hire me to develop something for you which YOU will be delivering to a third party, setting deadlines arbitrarily without consulting ME is a surefire way to get me pissed and look for ANY way to use the legal system against you so I can fuck you sideways with your project and GTFO. In case you didn’t notice, I don’t fucking give a flying rat’s ass about who you or the actual clients are, or what your relationship is with them, or anything of the sort. I want to do my fucking job, get paid, and go home. But when you start telling the client that the product will be ready by a given date where I am 100% sure that it will NOT be, that’s when I start actually getting morose and actively attempt to make YOU look bad in front of your client. Preferably, in ideal cases, also having side conversations with said client explaining the ACTUAL situation and circumstances of the product.
- Unexpected bugs and errors after code freeze and when porting code to production. This one pisses me off to no end. You make sure your code is as clean as you can, you make an actual inhuman effort to make sure everything is working, you document all possible exceptions and error situations, and write code to make sure your software fails gracefully if an error comes up; you build your error library with error codes, descriptive messages, and make absolutely freaking 100% SURE everything works… And the moment you move your stuff to the production environment, EVERYTHING starts to blow up here or there. Cue an insatiable, irresistible desire to rip your hair out of your scalp with your bare hands.
Sigh. Such is the life of a code monkey.
- 1 comment //
- 6 comments //
- 10 comments //