May 11th 2012, 20:58:06
Originally posted by Azz Kikr:
Ya know, I was just looking at my walls -o- text and realized that I should probably be more liberal with my proper capitalization and double-spaced paragraphs. Apologies. That fluff is hard to read.
Also, I'm not suggesting that lying on a resume is a good thing. Just that if you could read the hiring agent's mind, you could easily tailor the resume to say what you need for an interview. Bad idea all around, but it would probably work.
Also, I'm not suggesting that lying on a resume is a good thing. Just that if you could read the hiring agent's mind, you could easily tailor the resume to say what you need for an interview. Bad idea all around, but it would probably work.
Heh, I took your walls of text and make they wallier!!
Anyways I remember those times too, it was ridicules. I don't see any problem stretching the truth on your resume... I would advise against lying though, heh.
I remember classing up my resume to get a programming job at cisco early on by throwing down there all the work I did with open source projects. One was apache, and I stated all this fantastic stuff I had done, and it was all true but accomplishing those was literally like 10 lines of code. None of those being critical bug fixes or anything either.
Originally posted by Dibs Ludicrous:
that might work for other fields, but IT is a bit dynamic because new stuff is being developed constantly. junk tends to get put in place before anybody even thought about writing a book about it. sometimes the APIs aren't even properly documented when people start using them. course, then how can people get certified on it... hmmm, dang logic.
There is nothing I hate more than lacking APIs and documentation. I was complaining about OpenSSLs fluffty API documentation but I have never once went into a job in any field of IT and found decent documentation.
Like Radioshack uses this ass old POS. I was preparing an upgrade path plan and was going to pitch a contract offer to them. First off they don't even have documentation on the source, the source is all c, it has never been properly cleaned up. There is no documentation at all, even the in-code comments are terrible. I walked away.
Cisco had documentation but it was fairly unkept. Last time updated was a few years back, they had put out an entire new platform of routers and switches on a new platform of IOS in that time.
Every IT department I worked in had fluffty documentation. You would be lucky if they wrote down anything but license keys, and even then those were often missing. I know I updated several peoples documentation in my time, last year I went back to a business as a consultant that previously I had acted as coordinator and had from scratch documented nearly everything. Not a single update, they had a director and 2 coordinators since me and none of them even bothered with documentation.