Reputation
1,884
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
9 17
Newest
 Revival
Impact
~72k people reached

Feb
7
comment Have you ever been involved in a BIG Rewrite?
How big were they? How many lines of code in original system, how many person-months did the rewrite take?
Feb
7
comment Problems (such as maintenance) in development with unpopular language
It's your boss's job to worry about continuation. But it is your job to make sure the boss is aware of the issues they should worry about. You should talk it over with the boss.
Jan
29
comment Why are developer commit statistics harmful?
I don't think gathering the statistic is harmful in itself but using it to evaluate programmers would be. Our VCS gathers that info, along with a myriad if other stats, and its available to the whole team but we hardly ever look at it. So no, gathering the statistic isn't harmful.
Jan
28
comment How do you respond to “Tell me a little bit about yourself.” question in interviews?
It could be a bad sign if the main interviewer really hasn't read your resume. Maybe you don't want the job. Could be they will always be rushed and won't read your requirements docs, emails...
Jan
26
comment Will giving new recruits a separate subproject from experienced developers help the newbies ramp up more quickly?
And who's going to interview these new hires, update the written requirements and design docs, fill in the bug database, spend time on the training sessions...?? Is it the current developers? Because that means they won't be developing full-time. So development speed goes down. Oops.
Jan
25
awarded  Mortarboard
Jan
25
awarded  Nice Answer
Jan
24
comment In pseudo code what does := mean?
@back2dos etc Even today using = for assignment is confusing. I can still remember, long ago when I first learnt to program, how confusing it was to see x = x + 1. Once you've studied basic high-school maths, x = x + 1 just looks like impossible contradictory gibberish. Next I read an excellent book on computer science for the general reader (I think it was this) which used <- for assignment. x <- x + 1 is much easier to understand.
Jan
21
comment Frankly, do you prefer Cowboy coding?
+1. Maybe you can't choose your skill level but you can choose to improve, like an illiterate person can go to night school. Read, find good developers and learn from them, reflect on what works and what doesn't.
Jan
11
comment How can I answer interview questions about developing in a team when I've always been a lone developer?
+1. In fact it sounds like the OP actually answered the question perfectly well!
Dec
30
awarded  Nice Answer
Dec
29
comment How does unit testing work?
+1 for running the existing code and recording the results. In this situation, that's probably the pragmatic approach.
Dec
29
answered Why do programming language (open) standards cost money?
Dec
14
comment How do quick & dirty programmers know they got it right?
@Steve Yes it is, that is why I quoted it. It does say "beware of bugs"
Dec
13
comment How do quick & dirty programmers know they got it right?
Donald Knuth: "Beware of bugs in the above code; I have only proved it correct, not tried it." haacked.com/archive/2007/11/29/…
Dec
13
comment How assertive should I be in handling exceptions in objects?
@one.beat You can easily tell which objects need manual disposing. They implement IDisposable. That means the API designer is telling you to dispose the object. Follow the instructions.
Nov
29
comment What is the supposed productivity gain of dynamic typing?
... it's not really relevant to compare with C. Better to compare with C# or another modern statically typed language
Nov
29
comment What is the supposed productivity gain of dynamic typing?
@bryan he's disagreeing because many if not all of the things you've listed are also available in modern static languages. They are irrelevant. You might as well compare dynam
Nov
29
comment What is the supposed productivity gain of dynamic typing?
Conversely if you have erroneously entered an incorrect program the compiler tells you immediately and highlights the bad line. this improves your productivity, when compared to noticing a failed test run and debugging to find the error.
Nov
28
answered What are the key points of Working Effectively with Legacy Code?