November 10, 2011 at 9:57 pm
Comments posted to this topic are about the item First Impressions
November 11, 2011 at 12:54 am
Categorisation can help if you must relate to many less well known people, but it's important to realise that one person will fit into many categories. Trying to fit a person into one category achieves nothing but subtraction... unless of course you're prepared to go for the real world solution and have a specific category for each person 🙂
November 11, 2011 at 3:59 am
I agree on categorizing people. It is a surviving thing inside each of us from being eaten by some animal or being beaten by... well, some animal too.
I agree to continually have "the first moment" on someone as we must known that people changes all the time: burn out, sickness, drugs, season, age and "month periode", to name only those, change the way people thinks and reacts.
So, I have a "first impression" every time I meet someone and I am ready to change the category I have put him the previous time, and my beahaviour toward that person, just in case I met him at the wrong moment e.g. a moment that made him a better or a worst person than he is...
Trusting someone comes from the experience you have with that person and from which category that person puts himself on different situation. But even there... you never know 😉
November 11, 2011 at 4:06 am
Mmm, just one category then.
November 11, 2011 at 6:39 am
david.wright-948385 (11/11/2011)
Mmm, just one category then.
yes, but which one depends on how you fill and how he fills in a specific moment :blink:
November 11, 2011 at 10:35 am
My first thought on this topic had nothing to do with people per se.
I inherit a lot of databases and sometimes architect databases that I pass along to others later. The first time I open up someone's tables and stored procedures I get a strong first impression of the developer who created them.
I can't tell you how may times I've seen 1000-line stored procedures with no comments or formatting and dozens of nested if-else statements and variable names like @a, @b-2, and @C. Yikes!
Or all the tables are heaps with no indexes or FKs or 10 columns to hold 10 variations of some attribute in the main table--or even worse--a delimited string that must be parsed before it can be used.
Talk about bad first impressions! But thank you lazy developers...your poor work is usually why you've been fired and I got the job.
November 11, 2011 at 10:57 am
Steven Willis (11/11/2011)
My first thought on this topic had nothing to do with people per se.I inherit a lot of databases and sometimes architect databases that I pass along to others later. The first time I open up someone's tables and stored procedures I get a strong first impression of the developer who created them.
I can't tell you how may times I've seen 1000-line stored procedures with no comments or formatting and dozens of nested if-else statements and variable names like @a, @b-2, and @C. Yikes!
Or all the tables are heaps with no indexes or FKs or 10 columns to hold 10 variations of some attribute in the main table--or even worse--a delimited string that must be parsed before it can be used.
Talk about bad first impressions! But thank you lazy developers...your poor work is usually why you've been fired and I got the job.
I once had to write a word processing application to replace the old one we had in the software. The original developer was a VP by that time. He was pretty brilliant. The issue was he was pretty brilliant and knew it.
Having the ability to do bitwise operations in C to save memory does not mean you should, or need to. Making function calls to a function that calls another function that calls another function that calls another function that calls another function that then calls a C base language function, when the ones along the line add no value, does not make it easy to understand your code.
I spent about a week writing the word processor. I spent two months going through his code to find out what he did, so we could duplicate his functionality. Functionality that looked at who owned the software, and verified that the owner was listed in the document being written, to prevent someone else from stealing the software and using it to write a letter.
My word processor did everything Word did at that time. His, the one being replaced, did everything Microsoft Write did at that time. Months were wasted because someone felt the need to show off their C skills.
Talk about first impressions! Or second, third, fourth... He was very smart, but man did he waste his intelligence proving it to everyone.
Dave
November 11, 2011 at 11:04 am
First impressions are almost always wrong. I know someone who came here from Tennessee. Southern, good ol' boy accent. Doesn't sound like anyone who should work in technology. A lot of Southern slang, phrases, and things that come across as "uneducated" or worse.
He is one of the smartest people I have worked with. Took to the job running, never looked back, and has improved the performance in that position 10 times over the last person.
Frequently people in our industry get a bad rap. We "can't talk like normal people", we "use too many acronyms", we need to "stop showing off" or "communicate like normal people". I hear this about my peers from people in other positions that drop more acronyms than techies ever do, that expect everyone to fully understand what they are talking about and never want to take the time to explain. They view us as difficult or stupid.
The fact is people are all different. We all have areas we are strong in, and areas we are weak in. Generalizing based on a limited number of conversations is not only wrong, it is unprofessional. Even the most difficult people I have worked with can be easy to get along with if you take the time to get to know them somewhat. We don't have to be friends, but we do need to take our time.
Tech is fast paced. It is hard to slow down in a meeting and take time to understand how someone communicates. Failing to do so is a bad idea and usually comes back to us in the form of more work.
Dave
November 11, 2011 at 11:19 am
While first impressions do count, I find myself relying on them very rarely. My impression of someone can change very quickly from that first impression.
I also find it important to try and not let that first impression (or any impression) get in the way of being able to work with that person.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 12, 2011 at 1:09 am
Those last two replies (djackson 22568 and SQLRNNR) are what I mean. Categorisation it at best a poor and time-limited approximation performed for convenience or speed. People fit into many categories and (as SQLRNNR pointed out) they change all the time. As geeks (some of us with poor interpersonal skills :-)) we need to take people as they ARE, not as they appear to be: less still from a single category that we placed them in. Even if we place them in a different category each time we meet them, we're still losing the person.
People are people, not categories. Each person you meet is different from all the people you've met in the past. If you can't see the difference(s) you either haven't looked, or you haven't known them long enough.
November 12, 2011 at 10:17 am
First impressions come from more than face to face interactions. It has become common to get a first impression in the form of written communication. I tend to be quite harsh when I see poor spelling or grammar. The first impression I get is that the person doesn't even care enough to think about what they are writing to check spelling and grammar. I'm no spelling or grammar expert, but, there should be a basic understanding.
I understand the multinational and multicultural nature of communications, and, I try to keep that in mind. But, still, it can be quite disturbing to me when frequent contributors to this website and other websites don't seem to care enough to run spell check.
My rant is over... thank you for "listening". 🙂
November 12, 2011 at 11:38 am
OCTom (11/12/2011)
First impressions come from more than face to face interactions. It has become common to get a first impression in the form of written communication. I tend to be quite harsh when I see poor spelling or grammar. The first impression I get is that the person doesn't even care enough to think about what they are writing to check spelling and grammar. I'm no spelling or grammar expert, but, there should be a basic understanding.I understand the multinational and multicultural nature of communications, and, I try to keep that in mind. But, still, it can be quite disturbing to me when frequent contributors to this website and other websites don't seem to care enough to run spell check.
My rant is over... thank you for "listening". 🙂
How about idiots who type everything:
i am so happy my daddy got me dis knew ipod thingy my mom loves me too who is your girlfriend
The content is obviously fictional (at least I hope it is) but some of them sound like little kids. The phrase "it hurts my eyes" is true when I attempt to read stuff like that. You went to school for a reason, show you made it out of first grade, damn it!
Dave
November 12, 2011 at 11:40 am
david.wright-948385 (11/12/2011)
Those last two replies (djackson 22568 and SQLRNNR) are what I mean. .
Excuse me, but maybe you need to take some time and think about what you are reading. When someone agrees with you and you then call them out by name and attack what they said, well, it doesn't become you.
First impressions are almost always wrong. I know someone who came here from Tennessee. Southern, good ol' boy accent. Doesn't sound like anyone who should work in technology. A lot of Southern slang, phrases, and things that come across as "uneducated" or worse.
He is one of the smartest people I have worked with. Took to the job running, never looked back, and has improved the performance in that position 10 times over the last person.
How can you not read this as first impressions ( or second, third or fourth ) are frequently incorrect!
Sigh.
Dave
November 13, 2011 at 1:59 am
djackson 22568 (11/12/2011)
david.wright-948385 (11/12/2011)
Those last two replies (djackson 22568 and SQLRNNR) are what I mean. .Excuse me, but maybe you need to take some time and think about what you are reading. When someone agrees with you and you then call them out by name and attack what they said, well, it doesn't become you.
First impressions are almost always wrong. I know someone who came here from Tennessee. Southern, good ol' boy accent. Doesn't sound like anyone who should work in technology. A lot of Southern slang, phrases, and things that come across as "uneducated" or worse.
He is one of the smartest people I have worked with. Took to the job running, never looked back, and has improved the performance in that position 10 times over the last person.
How can you not read this as first impressions ( or second, third or fourth ) are frequently incorrect!
Sigh.
Sign... I was agreeing with djackson 22568 and SQLRNNR - they raised good points and if you read my post again, I hope you'll see that I sought to support what they said and build on it.
November 14, 2011 at 1:55 am
david.wright-948385 (11/13/2011)
djackson 22568 (11/12/2011)
david.wright-948385 (11/12/2011)
Those last two replies (djackson 22568 and SQLRNNR) are what I mean. .Excuse me, but maybe you need to take some time and think about what you are reading. When someone agrees with you and you then call them out by name and attack what they said, well, it doesn't become you.
First impressions are almost always wrong. I know someone who came here from Tennessee. Southern, good ol' boy accent. Doesn't sound like anyone who should work in technology. A lot of Southern slang, phrases, and things that come across as "uneducated" or worse.
He is one of the smartest people I have worked with. Took to the job running, never looked back, and has improved the performance in that position 10 times over the last person.
How can you not read this as first impressions ( or second, third or fourth ) are frequently incorrect!
Sigh.
Sign... I was agreeing with djackson 22568 and SQLRNNR - they raised good points and if you read my post again, I hope you'll see that I sought to support what they said and build on it.
That wasn't the first impression I got from your post; but I read it again and realised that it was ambiguous, could have been intended either way, and decided to interpret it as what you have said you meant. But people don't always notice ambiguity, so it's better to be careful not to be ambiguous - as I know to my cost, as I don't always succeed.
Tom
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply