The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
1st. Every resident of Israel will receive 45760 EUR from the European Union [link]
2nd. Every resident of Israel will receive 33674 EUR from the European Union [link]
3rd. Every resident of Israel will receive 64868 EUR from the European Union [link]
And it is all before 8 at the morning...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
like that [a lot of "doh" variations compatible here], and mage millions
And then we wonder, that the world goes as it goes...
I can't tell, what is worst... the one putting such crap online, or the millions clicking on it and making them earn (big) money from it
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I read/studied the fascinating responses, reactions, cathartic recapitulations of trauma, etc., on the thread. I appreciate the opportunity to hear your voices.
It made me realize how atypical my experience was: I started programming at age 42, after dropping out of a doctoral program in social science after time in academia, and practicing psychotherapy. My path was from SAS/SPSS on mainframes, to 6909 assembly language to BASIC, to LISP, to PostScript.
By the time I was being interviewed, I had a rare specialty, PostScript, and thanks to a book I wrote most of for Addison-Wesley, and my work on Cricket Draw 1.1, I was quite well known in the "desktop publishing" arena.
When I participated in interviews as interviewer (at Adobe), the candidates were already pre-selected for excellence. Personality didn't matter that much unless the candidate really blew it.
Your responses tell me that the modal experience these days, in which personality is more of a factor, is in a context very different from my weird zig-zag through pre-internet days.
I hear, in many of your comments, a reflection of the current zeitgeist of political correctness in the workplace, that emphasis on protecting people from being "triggered" by whatever.
If I were hiring today, for a major desktop app project, I would try to achieve a mix of styles/personalities, and I would not base this on everybody "getting along." In fact, I'd like at least one a'hole on the team. Autistic: no problem if you write great code ! Painfully introverted: ditto. Obsessive-compulsives: you're hired. Caution for hysterics, and temperamental geniuses, however.
What this mix requires, of course, is careful planning and allocation for who works on what. And, yes, that's easy to say, and really hard to do ... well.
Meetings: most are a total waste of time. Formal code-reviews: yes. Hiring testing specialists who delight in finding bugs: yes, when budget and development allow.
Conflict/confrontation is not always a bad thing, and, imho, it's a program manager's task to channel conflict into "fair-fights" rather than sabotage, and inhibited productivity.
Say, I'm a manager, and, a relatively new hire comes to see me, someone still trying to getup to speed, but whose performance is adequate in terms of their role and length on the job:
Me: Hi, I want to reassure you you are doing okay, and meeting our expectations,
NH: Thanks, but, I'm worried ... I feel like the other programmers think I am stupid.
Me: What have you observed the other programmers doing that makes you react by having thoughts like 'I am stupid,' and feeling bad ?
NH: Little things, like the way Jane rolls her eyes when she looks at my code ... the way James kind of grins when I ask him a question that demonstrates I don't fully understand the question.
Me: What if your code is stupid ? Where "stupid" means not yet reflecting the mastery of the complex codebase you are busy learning ?
NH: I hadn't thought of it quite like that ...
Me: What if rolling eyes and a sly grin are really a kind of superficial teasing that says: we know what you are struggling with ... we've been through it.
NH: It's hard to see it that way !
Me: It is hard for anyone to see it that way ! It takes effort to become aware of the trigger for the internal negative self-appraisal and develop the habit of confronting it before it takes root in the emotions.
NH: okay, that's interesting.
Me: Remember you might need to change how you react, and how you behave, but, you don't have to change who you are !
Me: Gotta go, the VP for Sales and I are going to go smoke enough crack that we can see how to fudge the sales for the quarter to keep the VC's off our back.
Well, I told you I came from the past
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
You're making a huge mistake, thinking that people are logical and reasonable
Here's how such a conversation could work out as well:
NH: *I can't really say the others make me feel stupid, because that would give off the signal that I might be stupid or insecure and I don't want to be a snitch.*
You: "Hi, I want to reassure you you are doing okay, and meeting our expectations."
NH: "Yeah, I'm fine, I really like it here and I'm learning a lot." *I don't know how much of this sh*t I can take.*
You: "So you have no worries at all?"
NH: "Well... It's all pretty complex, but I think I'm managing quite well." *Phew, almost blew it there.*
You: "How are your coworkers?"
NH: "They really help me out." *They're all assholes for making me feel stupid.*
And then two things can happen, either the new hire stays long enough to become the a**hole he think the others are, or he quits and finds a new job because there are plenty of them.
I've had a discussion with a coworker about logging.
He thought my code had to few logging and couldn't find a bug because of it.
I found the bug in five minutes and it was actually HIS code that was faulty.
He was like "NO SANDER! YOUR CODE NEEDS MORE LOGGING!"
Me: "But I could find it in five minutes, the logging literally says which function threw the exception and it's only a couple of lines. So how much logging do you need, after every statement?"
Him: "I want logging at the beginning and at the end of the function!"
Me: "But that wouldn't help as we already know the code entered the function, but didn't finish correctly..."
Him: "IT WOULD HELP ME!"
He then went to our manager because "fine" wasn't the correct answer, he wanted a sincere apology and that I'd add the logging because I saw his point rather then making him shut up.
We got along pretty well, but I don't think he ever liked me anymore after that.
I wasn't the only one who had troubles with that guy.
He was pretty resentful and took everything personally.
So tell me how people like that are an asset to any team, even if they are brilliant?
Unfortunately, a lot of people are like that (this guy wasn't even the most toxic of the team, go figure).
I agree that "getting along" is probably a bad measure, but some form of social skills and ability to work in a team are at least as important as programming skills.
And nothing kills teamwork more than a bloated ego.