Programming Forums > Application Development > C++

Infinite Recursion · Jun 6th, 2005, 10:12 AM

Wow DaWei ... 64. You are possibly the oldest person in PFO, therefore, probably the wisest.

How many of your 64 years were spent in this field?

Pizentios · Jun 6th, 2005, 10:42 AM

can't we just get along?

DaWei · Jun 6th, 2005, 2:49 PM

Nah, we don't need to discuss this here. Grunts, invective, and cuss words ain't germane to the topic of "How to Post Well."

As far as how long I've been around, it's since before C was a readily available choice for programming. Programming was just a part of my career path. If you're really interested, you can view an old resume synopsis on my site.

If you want to know about judging a book by its cover, this is a true story:

In 1989 or thereabouts, I needed to hire an engineer/programmer. Just one. My company put a blind ad in the paper and I got maybe 500 resumes. To be fair, I personally interviewed every single person for a minimum of one hour. Yeah, right, sure I did.

The first thing I did was toss all the pastel colored ones in the trash. You know, the ones provided to graduating students by the placement office. The odds are very, very good that I missed an opportunity to hire a very sharp person. Sorry, mom, how was I to know? Your child's looked just like all the others, but for the name.

My next step was to select all the ones where the applicant's abilities appeared to EXCEED my requirements. That still left a lot.

Once those were in hand, I began to judge the books by their cover. Grossly unfair. All else being equal, if one was clear and crisp and one was done on an ancient typewriter with a faded ribbon, guess how the choice was made between the two? They're MY eyeballs, right?

Ten people were scheduled for and notified of a telephone interview. Six were there to answer the phone at the appointed time. The other four didn't get a second chance. Grossly unfair. How do I know Joe's mother hadn't just been rushed to the hospital following an accident?

Two people got face to face interviews. I knew which one I was going to hire. The other one had an excellent resume, experience in projects very similar to the one I had opening up. His problem was that he claimed to have been project leader on a certain project (for another company) a couple of years previously. His BIGGEST problem was that I had been the leader for that project. He got an interview solely for the reason that I wanted to see his face when he walked into my office. Mean, huh? I still laugh about ol' Ed's face.

Being like everyone else isn't necessarily good -- look at all those deep-sixed pink resumes. Being a maverick isn't necessarily good. Most mavericks (by the actual definition of the word in cattlemen's circles) get their cojones cut off.

It's YOUR career. It's YOUR persona. It's YOUR choice. It's YOUR responsibility. Not mine, and not your mom's.

Programming professionally concerns a lot more than correct syntax or barely adequate functionality. Some of my posts tend to address these kinds of issues. Others might just present a coded solution to the immediate problem of an OP. One never knows, do one? (Climbs down off soapbox). I'm done.

grumpy · Jun 7th, 2005, 4:00 AM

Quote:

Originally Posted by big_k105

Do we really need to be discussing proper english here? I mean I personally understand the need for atleast good communication skills esp in the interview. As i have blown many interviews because i get nervious which in case i dont speak very well when im nervious. Not that im the best at proper english but im not the worst either. So again do we need to be discussing this here?

When you ask a question, it is usually a good idea to ask a question in a way that can be understood by someone else who attempts to answer it.

Good language skills are a part of that. That's not saying one's skills have to be perfect. But it means you have to put some effort into using language that can be reasonably understood and doesn't unnecessarily offend someone who might help you.

Do I get upset over imperfect english? Do I worry if a native speaker of another language doesn't express themselves perfectly in english? No, to both questions: I will help if I understand the question (or can make an educated guess about what the problem is) and if I can help. But I am unlikely to help someone who hasn't put some effort into asking a sensible question. I am also unlikely to help someone who's choice of language annoys me - and unnecessary crudity annoys me. That's not denying anyones right to use that language: I'm simply exercising my rights not to respond to it or, in some cases, expressing my dislike of that language.

Berto · Jun 7th, 2005, 4:50 AM

Quote:

Originally Posted by DaWei

Nah, we don't need to discuss this here. Grunts, invective, and cuss words ain't germane to the topic of "How to Post Well."

As far as how long I've been around, it's since before C was a readily available choice for programming. Programming was just a part of my career path. If you're really interested, you can view an old resume synopsis on my site.

If you want to know about judging a book by its cover, this is a true story:

In 1989 or thereabouts, I needed to hire an engineer/programmer. Just one. My company put a blind ad in the paper and I got maybe 500 resumes. To be fair, I personally interviewed every single person for a minimum of one hour. Yeah, right, sure I did.

The first thing I did was toss all the pastel colored ones in the trash. You know, the ones provided to graduating students by the placement office. The odds are very, very good that I missed an opportunity to hire a very sharp person. Sorry, mom, how was I to know? Your child's looked just like all the others, but for the name.

...............

Programming professionally concerns a lot more than correct syntax or barely adequate functionality. Some of my posts tend to address these kinds of issues. Others might just present a coded solution to the immediate problem of an OP. One never knows, do one? (Climbs down off soapbox). I'm done.

One of my life's goals is to interview someone and also fire soemone.

The Dark · Jun 7th, 2005, 5:02 AM

Quote:

Originally Posted by Berto

One of my life's goals is to interview someone and also fire soemone.

I've been on both sides of each of these processes (downsizing in most of the firing cases). While I've found that both sides of the interview process are usually very stressful, both being fired and firing someone is a lot more painful. I wouldn't recommend it to anyone, unless you are lucky enough to find someone to fire who really deserves it.

Pizentios · Jun 7th, 2005, 9:06 AM

Quote:

Originally Posted by The Dark

I've been on both sides of each of these processes (downsizing in most of the firing cases). While I've found that both sides of the interview process are usually very stressful, both being fired and firing someone is a lot more painful. I wouldn't recommend it to anyone, unless you are lucky enough to find someone to fire who really deserves it.

heh, i know a few people around wher i work that could use a good firing.

peace_of_mind · Jun 7th, 2005, 9:49 AM

Quote:

Originally Posted by Nuticulus

Yes, they have code tags, but once you minimise the space it takes up, it's annoying to read the code because it's cramped into such a tiny space. So if there's a large wad of code to read through, it's annoying. I much prefer it when people nopaste large chunks of code (normally nopastes have decent syntax highlighting) or post it as an attachment.

What really peeves me is when people post code in quote tags. It doesn't happen often around here, but it's annoying. Takes up a stupid amount of space, too. That, and when you get quotes being quoted. And when you quote a hugemongously long post already.

I like code tags mostly for the purpose of spacing/indentation. Pasting code into the body of the post makes it a real pain in the ass to read through, especially in longer programs. Just my point of view.

Pizentios · Jun 7th, 2005, 9:52 AM

Quote:

Yes, they have code tags, but once you minimise the space it takes up, it's annoying to read the code because it's cramped into such a tiny space.

that's why i run at 1600x1200 :-)

Infinite Recursion · Jun 7th, 2005, 10:05 AM

lol @ DaWei ... brought him in just to see the look on his face. Honestly, with 500 applicants, I probably would have used a similar approach... I'd even drill it down to the font choice and layout.

Jun 6th, 2005, 10:12 AM	#51
Infinite Recursion Programming Guru Join Date: Jul 2004 Location: United States Posts: 3,464 Rep Power: 8	Wow DaWei ... 64. You are possibly the oldest person in PFO, therefore, probably the wisest. How many of your 64 years were spent in this field? __________________ http://jasonpowers.net "There are a thousand hacking at the branches of evil to one who is striking at the root."

Jun 6th, 2005, 10:42 AM	#52
Pizentios Programming Guru Join Date: May 2004 Location: Brandon, Manitoba, Canada Posts: 2,023 Rep Power: 7	can't we just get along? __________________ Profanity is the one language that all programmers understand. Check out my Blog <---updated Nov 30 2007!

Jun 6th, 2005, 2:49 PM	#53
DaWei Resident Grouch Join Date: Jun 2005 Posts: 6,453 Rep Power: 10	Nah, we don't need to discuss this here. Grunts, invective, and cuss words ain't germane to the topic of "How to Post Well." As far as how long I've been around, it's since before C was a readily available choice for programming. Programming was just a part of my career path. If you're really interested, you can view an old resume synopsis on my site. If you want to know about judging a book by its cover, this is a true story: In 1989 or thereabouts, I needed to hire an engineer/programmer. Just one. My company put a blind ad in the paper and I got maybe 500 resumes. To be fair, I personally interviewed every single person for a minimum of one hour. Yeah, right, sure I did. The first thing I did was toss all the pastel colored ones in the trash. You know, the ones provided to graduating students by the placement office. The odds are very, very good that I missed an opportunity to hire a very sharp person. Sorry, mom, how was I to know? Your child's looked just like all the others, but for the name. My next step was to select all the ones where the applicant's abilities appeared to EXCEED my requirements. That still left a lot. Once those were in hand, I began to judge the books by their cover. Grossly unfair. All else being equal, if one was clear and crisp and one was done on an ancient typewriter with a faded ribbon, guess how the choice was made between the two? They're MY eyeballs, right? Ten people were scheduled for and notified of a telephone interview. Six were there to answer the phone at the appointed time. The other four didn't get a second chance. Grossly unfair. How do I know Joe's mother hadn't just been rushed to the hospital following an accident? Two people got face to face interviews. I knew which one I was going to hire. The other one had an excellent resume, experience in projects very similar to the one I had opening up. His problem was that he claimed to have been project leader on a certain project (for another company) a couple of years previously. His BIGGEST problem was that I had been the leader for that project. He got an interview solely for the reason that I wanted to see his face when he walked into my office. Mean, huh? I still laugh about ol' Ed's face. Being like everyone else isn't necessarily good -- look at all those deep-sixed pink resumes. Being a maverick isn't necessarily good. Most mavericks (by the actual definition of the word in cattlemen's circles) get their cojones cut off. It's YOUR career. It's YOUR persona. It's YOUR choice. It's YOUR responsibility. Not mine, and not your mom's. Programming professionally concerns a lot more than correct syntax or barely adequate functionality. Some of my posts tend to address these kinds of issues. Others might just present a coded solution to the immediate problem of an OP. One never knows, do one? (Climbs down off soapbox). I'm done. __________________ Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Jun 7th, 2005, 10:05 AM	#60
Infinite Recursion Programming Guru Join Date: Jul 2004 Location: United States Posts: 3,464 Rep Power: 8	lol @ DaWei ... brought him in just to see the look on his face. Honestly, with 500 applicants, I probably would have used a similar approach... I'd even drill it down to the font choice and layout. __________________ http://jasonpowers.net "There are a thousand hacking at the branches of evil to one who is striking at the root."

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)