665 reputation
157
bio website
location
age
visits member for 2 years, 8 months
seen Oct 8 at 12:57

Apr
17
awarded  Yearling
Jun
9
awarded  Publicist
Jun
8
awarded  Booster
Jun
8
awarded  Announcer
Jun
8
awarded  Guru
Apr
27
comment How to fix quickly, dummy errors?
+1 for mentioning leveraging version control. I just type "git diff" (or use my own alias "gd") to see what I've changed, and there I immediately see that commented block of code and remember to uncomment it. And if you find that you've got some 27 modified files and you cannot find things like this from your diff listing, it's a sign that you are not committing often enough. I usually shudder if I have to commit more than three changed files at once.
Apr
17
awarded  Yearling
Mar
14
comment Is imposing the same code format for all developers a good idea?
@StijnGeukens By the way, would you mind posting a comment later on when you've made a decision and, hopefully, amassed some practical experience on this issue? It'd be interesting to know how everyone feels about this in, say, a couple of months.
Mar
13
awarded  Good Answer
Mar
12
comment In which order should I do comparisons?
In Java, it sometimes makes sense to compare if( CONSTANT.equals(variable) ), because then you avoid risking a NullPointerException or writing a null check.
Mar
8
answered Extreme Programming Daily Commits
Mar
6
awarded  Nice Answer
Mar
5
awarded  Critic
Mar
5
comment Is imposing the same code format for all developers a good idea?
It's not professional to wage wars about code formatting. A professional software developer will get things done just as well no matter if their code reads "if( foo )" or "if (foo)". If you really need to sell this kind of change to someone, you should appeal to the fact that they are professionals. They can't talk back or they'll appear anal-retentive. If someone does anyway, well, I hope for your sake they'll find a new job soon.
Mar
5
awarded  Editor
Mar
5
revised Is imposing the same code format for all developers a good idea?
came up with yet another reason
Mar
5
answered Is imposing the same code format for all developers a good idea?
Nov
30
comment What to do when a project is too difficult to continue developing?
@Dima I think you can easily get to the described situation if all the original people who worked on the project have left it and you just inherit it.
Nov
29
comment What to do when a project is too difficult to continue developing?
I'm going to have to comment on your point "How much time and money has already been spent?": it's an example of what's called the the sunk cost fallacy. You should instead consider to fail early, fail often.
Nov
29
awarded  Teacher