11
votes
7answers
259 views
Tips on persuading boss that code review is a good thing.
How would you persuade your Boss that code reviews are worth the time (and hence cost)?
Especially if, say, you worked in a hypothetical company that had several developers but they rarely worked …
11
votes
8answers
202 views
How common are “bandage” fixes?
Imagine the following scenario:
You've detected that your (or someone else's) program has a bug - a function produces the wrong result when given a particular input. You examine the code and can't …
6
votes
2answers
151 views
UI automation patterns and best practice for desktop applications
Background
I'm currently automating some tests for a plugin for MS Office. We are creating Coded UI tests in VS 2010. I suppose I could use the "Coded UI test builder" tool, but it does not really …
5
votes
13answers
347 views
What do programmers “micro-optimize” for today?
Back in the "good ol' days," when we would copy shareware onto floppies for friends, we also used a fair bit of assembly. There was a common practice of "micro-optimization," where you would stare and …
3
votes
6answers
172 views
Coding style - define fields separate or not.
Some use this convention:
private String event;
public getEvent() { return this.event; }
public setEvent(String value) { this.event = value; }
private int id;
... same as above ...
In some …
3
votes
7answers
308 views
Not specifying a return in a function, good or bad?
I have coded like this many times, and I've never encountered an issue, but the compiler always warns when it expects a return and there is none.
For instance, look at this:
-(NSString …
2
votes
16answers
260 views
Knowing what you know now, what one thing would you have done differently?
We constantly learn, evolve and grow as programmers. Think back to when you first started programming. If you could go back and do just one thing differently, what would it be and why?
