Reputation
406
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 5
Newest
 Editor
Impact
~15k people reached

  • 0 posts edited
  • 0 helpful flags
  • 16 votes cast
Feb
22
comment What's the most effective way to perform code reviews?
Sorry about the link rot. I edited to the current URL, but that won't prevent it from happening again.
Mar
3
comment What should be a fair amount of time in an interview before rejecting a candidate?
+1 for not wasting the interviewee's time.
Mar
3
comment What should be a fair amount of time in an interview before rejecting a candidate?
+1 For making sure they candidate leaves knowing why they were rejected. Otherwise, it was a waste of their time.
Mar
3
comment How do you cope with ugly code that you wrote?
I think this is mostly the right approach, but I would characterize it differently. They are hiring you to develop professional quality code. That means you need to build into your estimates time for "doing it right". Don't make estimates based on the time it would take you if you stayed up all night hacking and declared "complete" as soon as it ran correctly the first time. This may mean in a competitive situation you will be underbid sometimes. That's ok. You will develop a reputation for delivering quality and consistency and will ultimately win. Play the long game.
Mar
2
comment How do programmers deal with Project Lead/Managers?
As phrased, this question is misleading. What you're describing is bikeshedding (which I linked to in my answer). It's neither unique to, nor characteristic of Project Leads and Managers. Bikeshedders/nitpickers exist in all places and have all sorts of titles.
Nov
1
comment How did you become a const correctness convert?
"Programs must be written for people to read, and only incidentally for machines to execute." - Abelson & Sussman, SICP
Oct
26
comment Are code reviews necessary for junior developers?
@Thorbjørn - We do: goo.gl/7dMf. This comes from our book on code review, which you (and anyone else) can have for free: codereviewbook.com
Oct
25
comment Are code reviews necessary for junior developers?
@TMN Too right. The title "senior developer" does not mean "incapable of making mistakes" or "incapable of improving". If it does, that's not the kind of senior developer I want on my team.