551 reputation
46
bio website
location
age
visits member for 3 years, 3 months
seen Jul 16 at 11:49

May
13
awarded  Nice Answer
Jan
25
awarded  Necromancer
Apr
4
awarded  Yearling
Sep
21
comment What branch of computing involves object recognition in images?
I'd use umbrella term for such a diverse field: Computer Vision (alternatively Machine Vision).
Sep
20
answered How to write a very basic compiler
Aug
17
answered printf - source of bugs?
Jun
8
awarded  Constituent
Jun
8
awarded  Caucus
Apr
23
comment How important is the ability to touch-type?
Imo very bad analogy. Typing to programming is more like 'steering' or 'shifting gears' is to driving. It helps to drive efficiently and with less effort, but the real problem is to navigate, maintain awareness, know traffic rules, etc.
Apr
4
comment How to represent a Rubik's Cube in a data structure
[6][X][X] will probably yield the most convenient solution. Imho forget lists - those just obfuscate need for convenient model of cube surface.
Apr
4
awarded  Yearling
Apr
2
answered Why not write all tests at once when doing TDD?
Mar
20
answered Steps to Learn a Programming Language / Framework
Mar
13
comment Tooling and support for message format specifications
After being 'blessed' with a few ICDs in Word I am also looking for something like that.
Mar
9
answered Asserting in public methods
Feb
23
comment What's the difference between “Programmer” and “Coder”?
Developer,Engineer > Programmer >= Coder
Feb
21
comment How can I quantify the amount of technical debt that exists in a project?
@Thomas Owens: agreed, but almost any metric alone can be cheated. If used right and honestly, "TODO metric" provides cheap overview what code is actually missing or should be changed (=invisible debt for code-only based metrics).
Feb
21
comment How can I quantify the amount of technical debt that exists in a project?
Another simple metric I'd add to the list is number of TODO/HACK/WTF? comments in a codebase...
Feb
10
comment industry averages for time spent on maintenance
Maintenance isn't only about fixing bugs (defects) and its amount greatly varies for individual projects (=no definite answer). To me it seems you have rather quality issues.
Feb
9
comment Why should I prefer composition over inheritance?
Nice answer. I would summarize it that trying to achieve code reuse with inheritance is plain wrong path. Inheritance is very strong constraint (imho adding "power" is wrong analogy!) and creates strong dependency between inherited classes. Too many dependencies = bad code :) So inheritance (aka "behaves as") typically shines for unified interfaces (=hiding complexity of inherited classes), for anything else think twice or use composition...