Reputation
7,405
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 18 33
Newest
 Enlightened
Impact
~421k people reached

Mar
9
comment Not getting paid for hours you've worked?
@Merchf - great work if you can get it! Congrats on having a rare position that never demands overtime. I'm just saying that after 10 years in the industry, I haven't seen overtime-free to be the norm.
Mar
8
comment How do managers know if a person is a good or a bad programmer?
@pythagras - my counter question would be "which manager?" A manager of 40 people - no, of course not. A manager of 10 people - probably wouldn't kill you to sneak in 1 hour per person scanning code in known to be critical areas. 1 hour per 10 employees over 6 months seems easily doable.
Mar
8
comment How do managers know if a person is a good or a bad programmer?
@Jigar Joshi - don't know how every manager does it - this is what I've done when asked to do performance reviews or make recommendations.
Mar
7
comment Why aren't we all doing model driven development yet?
@KeesDijk - UML, for sure! Particularly Rational Rose, but also a bit of Rational SW Architect.
Mar
7
comment Do you have to be good at math to be a good programmer?
@Job - who said I was a PM? Also... I didn't quite say I liked it. Good at it does not equal liked it. And I was good at it only in a relative sense.
Mar
3
comment How would you explain multi threading to a seven year old kid?
I think the only thing I'd add is maybe change "jobs" to "games" or playing with toys or doing chores or homework.
Feb
28
comment How would most programmers feel about the bugs they wrote?
I'd add just one thing - a way to see a bug found before a release is "it could have been found by a customer - this is a win!" - every bug the team finds is a bug the customer doesn't find.
Feb
8
comment Software Developer Interview Question - Fair or Unfair
Adding one more - whether they described the job title accurately or not, chances are good that these questions reflect the reality of what the people they are hiring need to know. Saying, in effect "what you want to know isn't important" suggests the potential new hire doesn't get that this is part of the job.
Jan
10
comment How to persuade programmers to follow the basic rules
My favorite example is consistent test environment setup. I didn't HAVE to enforce a Right Way. I had a guy in charge of the install document. I said - "it's all you- you can do whatever it takes to make an install mechanism that ensures consistent install - everyone is empowered to bug you if the install is messed up". In less than a month we had a solid tool and a very short document. And the tool was installed as a short cut on every desktop. I didn't need enforcement, proper installation was already the path of least resistance. Now our goal is to remove the shortcut, making it automated.