Reputation
505
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 12
Newest
 Enlightened
Impact
~11k people reached

  • 0 posts edited
  • 0 helpful flags
  • 72 votes cast
Dec
13
revised Separation of construction and initialization
added 21 characters in body
Dec
13
answered Separation of construction and initialization
Oct
4
awarded  Enlightened
Oct
4
awarded  Nice Answer
Sep
24
awarded  Autobiographer
Jul
1
comment How to be a zero-bug programmer?
+1. In the words of Twisted Sister, What you don't know sure can hurt you / What you can't see makes you scream.
Dec
11
awarded  Popular Question
Sep
24
awarded  Yearling
Feb
26
awarded  Constituent
Feb
19
awarded  Caucus
May
3
awarded  Yearling
Feb
11
awarded  Critic
Jan
29
comment How can we inspire “hacker” culture?
I... really don't see the connection between commoditisation and hacking, I'm sorry. I doubt others will, either, because it's not clear what goal your question has. Why would you want to "inspire" hacker culture? Your tastes are your tastes, not all of us want to be hackers!
Jan
26
awarded  Nice Question
Jan
26
accepted In a legacy codebase, how do I quickly find out what is being used and what isn't?
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
Yeah, I don't think it's as clear cut as that, though that book looks worth reading. It does depend very much on the size/complexity of the codebase, and warm bodies available to do the work.
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
+1 This is a fantastic answer. Where's that +5 button gotten to...
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
+1. In response to Joel's comment, "It bloody well shouldn't be." Because I don't see the problem as inherent. I see it as being partly the fact that many people write shoddy code and don't care, while many others write reasonably good code but live by the "self-documenting code" concept... which is just plain BS: One may flatter one's own coding style all one wishes in privacy, but when it comes to public codebases just spawn comments like there's no tomorrow. Doesn't hurt. And finally there are people who have to get things working in a legacy codebases, on a tight time budget.
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
@Oded Rename is definitely easier than trial-and-error deletion! Good thinking there. That's one more tool in the box.
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
Thanks. Although your answer's somewhat Java specific, it's interesting to see your layered approach... peeling the onion, so to speak. Something to think about.