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

  • 0 posts edited
  • 0 helpful flags
  • 75 votes cast
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.
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
@jcmeloni No, I'm not being paid for the evaluation. But in my experience, and from small things I have picked up in the last couple of days, they don't have anyone else at the table right now. My skillset is fairly unusual, so I'm even more at ease that they don't have anyone else competing for it, based on the quote. The actual quote in question is from my client-to-be to their client, who is planning to re-award them the contract. Really from my end, I am meant to assist them in providing said quote. HTH.
Jan
26
comment In a legacy codebase, how do I quickly find out what is being used and what isn't?
Ordinarily I'd be 100% with you on the toss-and-rewrite approach. But in this instance (and at least for now), I am to be paid just for work to maintain the site, rather than a more extensive overhaul which would take several weeks. Also, even if I wanted to right now, I couldn't keep up with doing that and holding down the other contracts I have on the go, since my weekly availability for this is explicitly limited -- my primary contract must be fulfilled to its 40 hour weekly minimum.
Jan
26
revised In a legacy codebase, how do I quickly find out what is being used and what isn't?
added 49 characters in body
Jan
26
revised In a legacy codebase, how do I quickly find out what is being used and what isn't?
added 25 characters in body
Jan
26
asked In a legacy codebase, how do I quickly find out what is being used and what isn't?
Jan
13
answered How to avoid “DO YOU HAZ TEH CODEZ” situations?
Dec
15
comment Do TODO comments make sense?
Yep, given a listing in your IDE, they are helpful. I would say they're of very limited use otherwise, since the codebase may be enormous.