It's so hard to do something that requires considerable focus when all of a sudden you have to explain the basics to someone whose job it is to know such things. It's frustrating, downright a waste of time, and completely sidetracks you.
New things, I believe, should be introduced with a fair amount of detail. Things like what it is, how it fits in our lives and what applications it has all deserve some explanation time when being introduced. However, if that something is new to someone because of their ignorance, that's an entirely different matter.
Being completely oblivious to something already there for the last 10 years in one's field is just another way of saying you refuse to adapt to changes that would make your work better and help you do things smarter. Adaptation to change prevents one from moving into irrelevance and extinction, but when I think of it, I won't mind if some people end up in a natural history museum.
Friday, March 26, 2010
Thursday, March 25, 2010
Dance around like an old fat sow
I started working at 2:30pm today. Yeah, 2:30 in the freakin' afternoon! Thanks a lot PLDT. Your services are as impressive as a sneeze trying to uproot a tree.
When I arrived today at work, I was informed by one of my colleagues that a technician arrived earlier and went back to get a new modem. Okay. He arrived about half an hour later with two units identical to our modem.
After fiddling around with our modem, he came to the conclusion that the reason was that the DHCP service on the modem was disabled. (For non-tech people, the DHCP service gives your PC an Internet address so you can go online and take quizzes on Facebook)
Being a network administrator for the past 4 years, I took a few moments to ponder that thought, then my brain said "BS in its purest form". He took a couple more hours trying to make up excuses (and in the process got intimidated by Mac OS X's terminal -- saying he preferred the "old style", Windows). Finally, around 2:30, he quit and told me he'd endorse it to the ISP's "techier" guys, whatever the hell that is.
Some people totally loooooove BS. I bet if there were pools built for that, they'd be wading there like old fat sows.
When I arrived today at work, I was informed by one of my colleagues that a technician arrived earlier and went back to get a new modem. Okay. He arrived about half an hour later with two units identical to our modem.
After fiddling around with our modem, he came to the conclusion that the reason was that the DHCP service on the modem was disabled. (For non-tech people, the DHCP service gives your PC an Internet address so you can go online and take quizzes on Facebook)
Being a network administrator for the past 4 years, I took a few moments to ponder that thought, then my brain said "BS in its purest form". He took a couple more hours trying to make up excuses (and in the process got intimidated by Mac OS X's terminal -- saying he preferred the "old style", Windows). Finally, around 2:30, he quit and told me he'd endorse it to the ISP's "techier" guys, whatever the hell that is.
Some people totally loooooove BS. I bet if there were pools built for that, they'd be wading there like old fat sows.
Tuesday, March 23, 2010
Give me some double dutch
I'm sad. Lately, I haven't gotten much respect from my colleagues. Not because I did something wrong or scandalous, but for reasons I believe to be unfair. And when I'm sad, I buy good food to console my tortured soul. Give me some double dutch.
So today...
I was programming when I got to the office and making existing code prettier. It's a normal thing. To get more things done in the same amount of time, I have to either work harder or smarter. Given the choice between something that is a matter of laziness or stupidity, I'd go for the former. Better a lazy genius than a hard-working idiot.
Then out of nowhere, I get a notice that we have to set up videoconferencing equipment just for the plain purpose of testing if the equipment works. There's two things that came to mind here:
If I've learned anything at all, it's that our management doesn't know how to take care of its IT people. The said people are treated no differently than utility people, even though as few as they are, they can hold up many systems in the organization -- equipment, offices, initiatives, programs. As long as such abuses are tolerated, I doubt that its core business will flourish the way they want.
So today...
I was programming when I got to the office and making existing code prettier. It's a normal thing. To get more things done in the same amount of time, I have to either work harder or smarter. Given the choice between something that is a matter of laziness or stupidity, I'd go for the former. Better a lazy genius than a hard-working idiot.
Then out of nowhere, I get a notice that we have to set up videoconferencing equipment just for the plain purpose of testing if the equipment works. There's two things that came to mind here:
- Technology has never been on our side. Even management admits this. We do all the trials we want in practice and get it right every time. When it comes to the actual implementation, a myriad of problems crop up.
- It's one thing to test if you've never done this, but if this has been done over 30 times, that's another issue. Our office has only one web developer. One. The rest who dabble in it are a far cry. And it's a smart thing to expect that developer to do the same as someone who is actually competent in setting up online conferences? Further on, is it also logical to blame that person for the problems encountered when they do happen? Ever heard of Judas, you pig?
If I've learned anything at all, it's that our management doesn't know how to take care of its IT people. The said people are treated no differently than utility people, even though as few as they are, they can hold up many systems in the organization -- equipment, offices, initiatives, programs. As long as such abuses are tolerated, I doubt that its core business will flourish the way they want.
Monday, March 22, 2010
Office politics
Geeks don't get political. We don't like that. We leave people to do what they have to in areas of administration, management, operations and such. As much as possible, we want to be sitting in our comfy chair, looking at an IDE writing code.
So when I got to the office today (and after putting my job down), I got a call from an officemate demanding to know why I didn't go to work over the weekend. Now, there's a thousand reasons I could give and they still wouldn't give a rat's ass, so I decided to hear everything they had to say while checking my email on my iPod.
The talk was brief (or so I thought -- I was able to read about 6 emails -- I wasn't really listening), but the tone of voice was intense. Annoyed that we didn't help them "sign in and make a call" in Skype, they unleashed a flurry of complaints about our absence. Seems that people who don't want to help themselves and prefer to be spoonfed will never get anywhere. They won't die because of it (unlike in the Stone Age where you get scalped by a sabertooth tiger for your stupidity), but they won't share in the equivalent of battle glory today.
Friday, March 19, 2010
Metaphorically
I'm going to engage in a bit of wordplay today...
I work in an institution where the definition of "beyond the call of duty" is defined as "performing a task that is usually well out of your area of expertise ignoring risk to property damage or grossly inefficient use of employee time using reasons like 'the higher-ups need it', 'we need to impress our visitors', or 'you seem to always have an idea how to solve things so you do it'."
Let's break that down. The phrase originates from the military, where terms like "call of duty" or "duty calls" refers to something ranging from unpleasant (e.g., patrolling at unholy hours) to dangerous (e.g., going to war), but has to be done because they were trained to do it and they took an oath to do it even if it meant death.
Mixing "beyond" in that phrase obviously refers to doing more than what is usually expected. It can be in quantity (e.g., doing extra hours on patrol) or quality (e.g., improvising a contraption so it can take one away from a dangerous situation or save lives). In any case, the key is doing something that surpasses the requirements considerably.
Going back to my office, this phrase seems a far cry from the original context. It has been continuously abused to bring glory to one's self for something they thought was not part of their job because it was not listed in their job description or somebody else in the organization has started doing a huge bulk of it and they "led that effort".
I'm not impressed though. Things change. Therefore, doing something in the same manner for the next decade isn't going to get one anywhere. It's going to be a matter of adapting to these changes and integrating them into one's mindset. So when crunch time comes and things require going beyond the call of duty, I think it'll be pretty clear who's going out into the field and who gets left to guard base camp.
I work in an institution where the definition of "beyond the call of duty" is defined as "performing a task that is usually well out of your area of expertise ignoring risk to property damage or grossly inefficient use of employee time using reasons like 'the higher-ups need it', 'we need to impress our visitors', or 'you seem to always have an idea how to solve things so you do it'."
Let's break that down. The phrase originates from the military, where terms like "call of duty" or "duty calls" refers to something ranging from unpleasant (e.g., patrolling at unholy hours) to dangerous (e.g., going to war), but has to be done because they were trained to do it and they took an oath to do it even if it meant death.
Mixing "beyond" in that phrase obviously refers to doing more than what is usually expected. It can be in quantity (e.g., doing extra hours on patrol) or quality (e.g., improvising a contraption so it can take one away from a dangerous situation or save lives). In any case, the key is doing something that surpasses the requirements considerably.
Going back to my office, this phrase seems a far cry from the original context. It has been continuously abused to bring glory to one's self for something they thought was not part of their job because it was not listed in their job description or somebody else in the organization has started doing a huge bulk of it and they "led that effort".
I'm not impressed though. Things change. Therefore, doing something in the same manner for the next decade isn't going to get one anywhere. It's going to be a matter of adapting to these changes and integrating them into one's mindset. So when crunch time comes and things require going beyond the call of duty, I think it'll be pretty clear who's going out into the field and who gets left to guard base camp.
Thursday, March 18, 2010
Dumb and dumber
I'm not obliged to help you. Yes, I'm good with computers and you're students in this university, but it is not my problem if you're using f****d up software that messes up your PC. A lot of stuff in school goes around responsibility so if you aren't responsible, bad things will happen. Not because some staff member didn't answer your email, so stop making excuses!
And for you people asking me install email client software. If you can install your ridiculous screen savers that have malware, you can install Mozilla Thunderbird. You do not need to go through 7 years of web development or system administration to figure out what's written on your screen. Yeah sure, you'll need help if it's your first time to see a computer, but if you're still asking dumb questions until now, you have a problem.
And for you people asking me install email client software. If you can install your ridiculous screen savers that have malware, you can install Mozilla Thunderbird. You do not need to go through 7 years of web development or system administration to figure out what's written on your screen. Yeah sure, you'll need help if it's your first time to see a computer, but if you're still asking dumb questions until now, you have a problem.
Wednesday, March 17, 2010
Civil engineer Jec
Ah, no. Maybe just a construction guy.
Just after the qualitative seminar (where I was a participant, but turned into a Macgyver-all-around utility guy), I was asked why the hell the Internet connection cable had to go up to the rooftop. Our connection was an aerial one, so I explained that was the only point visible from the other building that could get into the hall. Instead of inquiring what else could be done to improve the "invisibility" of the cable, we got hit with this:
"What do we do?"
"Well sir, the ideal setup would be to drill a hole from on that side and protect it with a PVC pipe."
"Okay, so you guys drill a hole."
Right. I'm a friggin' programmer, not some dude with a mini jackhammer! But if you want a hole so bad, give me about two hours and I'll walk to the rail line, get a huge nail and a circus hammer, then start pounding on the east side of the building. Sorry if the hole isn't perfect, gets a bit large or looks like a baseball-sized diamond flew from the moon.
Just after the qualitative seminar (where I was a participant, but turned into a Macgyver-all-around utility guy), I was asked why the hell the Internet connection cable had to go up to the rooftop. Our connection was an aerial one, so I explained that was the only point visible from the other building that could get into the hall. Instead of inquiring what else could be done to improve the "invisibility" of the cable, we got hit with this:
"What do we do?"
"Well sir, the ideal setup would be to drill a hole from on that side and protect it with a PVC pipe."
"Okay, so you guys drill a hole."
Right. I'm a friggin' programmer, not some dude with a mini jackhammer! But if you want a hole so bad, give me about two hours and I'll walk to the rail line, get a huge nail and a circus hammer, then start pounding on the east side of the building. Sorry if the hole isn't perfect, gets a bit large or looks like a baseball-sized diamond flew from the moon.
Thursday, March 11, 2010
And the ranting continues
Let me see. Network engineer => Technician => Utusan.
Get one thing straight. I'm a programmer. I build software. Occasionally, I will do some other things like edit photos, transfer files to another server, build a server, or set up an Internet connection. But it's not because that's my job. It's because I refused to be an ignorant fool like yourself. It's because I chose to learn something that will help me work independently and smarter. It's because I understand that job qualifications aren't just something you put on a sheet of paper to fill it.
Get one thing straight. I'm a programmer. I build software. Occasionally, I will do some other things like edit photos, transfer files to another server, build a server, or set up an Internet connection. But it's not because that's my job. It's because I refused to be an ignorant fool like yourself. It's because I chose to learn something that will help me work independently and smarter. It's because I understand that job qualifications aren't just something you put on a sheet of paper to fill it.
Wednesday, March 10, 2010
YAAFM
I just need to let this out because it's bad for my health to keep this anger inside me.
What the hell is your problem?! Just because I'm a tech guy, I'm supposed to fix your computer, even if you were irresponsible, negligent and downright careless in using it? Following that line of reasoning, if you stuck a knife into your pantry's outlet and got third-degree burns, should the electrician be at fault for putting such a hazardous device in your office?
Computers, just like your table or cabinet, are assigned to you. You're supposed to take care of them in the same manner that you keep your table clean and your cabinet organized. It is not the IT department's fault if you get a virus because you keep cancelling virus updates or scans. It is neither the IT department's fault if Microsoft kills your office suite program because you bought counterfeit software just so you have the convenience of using software you were used to.
One more thing. It is none of your freaking business as to what reasons are behind my resignation. So don't go around, asserting that just because you have a high position, you have the right to demand why I am resigning as if I was supposed to fax you the reasons a week ago. Besides, you damn well know why I am resigning. Given the choice between removing viruses from your PC and programming fun applications, I'd rather do the latter. Go get some novice PC enthusiast to clean up what you were to ignorant to do. You are a f*cking moron.
What the hell is your problem?! Just because I'm a tech guy, I'm supposed to fix your computer, even if you were irresponsible, negligent and downright careless in using it? Following that line of reasoning, if you stuck a knife into your pantry's outlet and got third-degree burns, should the electrician be at fault for putting such a hazardous device in your office?
Computers, just like your table or cabinet, are assigned to you. You're supposed to take care of them in the same manner that you keep your table clean and your cabinet organized. It is not the IT department's fault if you get a virus because you keep cancelling virus updates or scans. It is neither the IT department's fault if Microsoft kills your office suite program because you bought counterfeit software just so you have the convenience of using software you were used to.
One more thing. It is none of your freaking business as to what reasons are behind my resignation. So don't go around, asserting that just because you have a high position, you have the right to demand why I am resigning as if I was supposed to fax you the reasons a week ago. Besides, you damn well know why I am resigning. Given the choice between removing viruses from your PC and programming fun applications, I'd rather do the latter. Go get some novice PC enthusiast to clean up what you were to ignorant to do. You are a f*cking moron.