Reputation
498
Next privilege 500 Rep.
Access review queues
Badges
2 3
Newest
 Yearling
Impact
~77k people reached

  • 0 posts edited
  • 0 helpful flags
  • 0 votes cast
Dec
11
awarded  Yearling
Dec
11
awarded  Yearling
Nov
25
awarded  Nice Answer
Feb
2
answered Studies on code documentation productivity gains/losses
Feb
2
answered What are technical writing principles?
Feb
1
answered Does TDD really work for complex projects?
Feb
1
answered Arguments to homologate Firefox in a Company
Feb
1
answered What software development process should I learn first for a solo project?
Feb
1
answered TDD/Tests too much an overhead/maintenance burden?
Feb
1
answered Ideal programming language learning sequence?
Jan
30
answered Why does TDD work?
Jan
30
answered Interview advice - Google Developer Advocate position
Jan
30
answered Methodology for documenting existing code base
Dec
29
answered How to persuade programmers to follow the basic rules
Dec
28
answered Is 4-5 years the “Midlife Crisis” for a programming career?
Dec
28
answered Relation between developers and clients
Dec
27
answered What does your Technical Documentation look like?
Dec
27
answered How to keep a team well-trained?
Dec
27
comment Are debugging skills important to become a good programmer?
Great answer. I've spent literally days searching for the simplest bug fix and literally stumbled into fixing a tricky bug in minutes. A good dev should have a reasonable strategy. And it depends a lot on the app. Say your app doesn't exhibit an issue when you put in a bunch of print/log statements or run the version with symbols. What then? The applicant should at least be able to articulate some sort of coherent strategy.
Dec
27
comment What are you telling yourself if you can't understand new concept, paradigm, feature …?
I have to chuckle hearing this. Years ago I got tasked with bringing some Windoze VB devs up to speed on our Linux/Java environment. The senior folks and I had a raging discussion over some of the analogies.