Reputation
354
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 10
Newest
 Yearling
Impact
~4k people reached

Jul
15
comment My boss decided to add a “person to blame” field to every bug report. How can I convince him that it's a bad idea?
"Could I have named the field [differently], so that feelings don't get hurt? Sure. But what's the fun in that?" -- this says a lot about how Jason wants to run his team.
Sep
12
comment How are mock objects commonly misused?
Just taking shortcuts isn't really enough to get you only dailywtf...
Nov
10
awarded  Yearling
Sep
19
awarded  Organizer
Sep
19
revised Can daily reports decrease a developer's productivity?
relevant to the general topics of management and meetings; saying "micro-management" kind of begs the question and is an uncommon tag
Sep
19
suggested approved edit on Can daily reports decrease a developer's productivity?
Sep
14
comment *Code owner* system: is it an efficient way?
It's natural some people will come to know some parts better than others. But the concept of "ownership" implies that other people must not touch that code without permission, or that only the owner has final say, and that's going too far. Obviously yes, "it depends" if that's what they actually mean.
Sep
13
comment Can daily reports decrease a developer's productivity?
Can you say more about what benefit you will get (or hope/expect to get) from daily reporting?
Sep
13
answered Can daily reports decrease a developer's productivity?
Sep
13
awarded  Citizen Patrol
Sep
12
comment What are the pros and cons for the employer of code questions during an interview?
@duros, I too am sorry to hear that. However, asking pedantic questions about trivia or esoterica is not using technical questions well. Asking you how you use printf or malloc in C is not so bad.
Sep
10
comment Responding to interview questions involving unknown algorithms
@Steven, I wish that was true but in practice it's not‌​: some people with years of experience on their CV actually can't write code for fairly simple algorithmic problems. Case in point: the OP thinks this question is unreasonably hard and doubts many people could solve it. So I think these questions are a reasonably cheap and useful measure.
Sep
10
awarded  Critic
Sep
9
awarded  Necromancer
Sep
9
awarded  Suffrage
Sep
9
revised What are the pros and cons for the employer of code questions during an interview?
clearer title
Sep
9
suggested approved edit on What are the pros and cons for the employer of code questions during an interview?
Sep
9
comment How do you feel about being asked to code during an interview?
But suppose you're working on some problem and you discover you need, for instance, to write some 15-line algorithmic function. Do you have to stop and prepare and write it tomorrow? Or do you just write it? I think better programmers will normally do the latter - though, obviously they may choose to make tea or take a break first.
Sep
9
comment How do you feel about being asked to code during an interview?
Well, at least these interviews are slightly useful in telling you something about the culture of the place. :) I agree it's really important that hiring managers do not look at it as a chance to show how superior they are, but rather to sell their company, and to learn about the candidate.
Sep
9
comment How do you feel about being asked to code during an interview?
A code question isn't meant to be the only question you ask. Ask them separate questions about how they'd test something, how they'd solve a performance problem, how they indent their code (sheesh, the correct answer is "the same as the rest of the team"), how they solved an interesting problem with someone else. Passion you can judge from whether they actually get interested in these questions.