804 reputation
1117
bio website craigtp.co.uk
location England, United Kingdom
age 40
visits member for 4 years, 2 months
seen Dec 16 at 10:26

I'm an analyst programmer with a passion for software development.

combined Stack Exchange profile for CraigTP


Dec
11
awarded  Yearling
Nov
18
awarded  Popular Question
May
7
accepted Can you be Agile without doing TDD (test driven development)?
Oct
3
awarded  Yearling
Aug
8
revised Why is an anemic domain model considered bad in C#/OOP, but very important in F#/FP?
Fixed name of cited commenter and added link to that commenters profile.
Aug
8
suggested approved edit on Why is an anemic domain model considered bad in C#/OOP, but very important in F#/FP?
Jun
10
awarded  Good Question
Feb
26
awarded  Caucus
Feb
26
awarded  Constituent
Feb
15
comment Can you be Agile without doing TDD (test driven development)?
@ShadowChaser I get what you're saying, but to play devil's advocate for a moment regarding the Agile Point #1, if I were on a team that did a waterfall-style development but we had great communication and collaboration between the members of that team, would that make us agile?
Oct
21
awarded  Good Question
Oct
11
awarded  Notable Question
Oct
3
awarded  Yearling
Sep
13
comment if ('constant' == $variable) vs. if ($variable == 'constant')
@LokiAstari Fair enough. Code Complete 2nd Edition is now 8 years old, and the original 1st edition is almost 20 years old! I'm sure there have been a ton of compiler (and other general) improvements in those intervening years.
Sep
9
answered Define which tests are run after build in Visual Studio 2012
Sep
4
comment What does it mean by atomic commit for a versioning system?
@shabunc - At least it wasn't VSS!
Aug
29
comment Asking for a code sample of the company at an interview
ask.slashdot.org/comments.pl?sid=1330515&cid=29002695
Aug
26
comment TDD - is it just about unit tests?
TDD isn't about unit tests at all. TDD is about design. With TDD your classes and thus your program as a whole has to be designed to be testable. This means low coupling, high cohesion, and all the other benefits you get from SOLID code. The unit tests exist to enforce that, whilst also providing assurance that your code works, and continues to work, when you refactor to further improve design.
Aug
23
comment How can I make refactoring a priority for my team?
And the oft-quoted, must read for refactoring this kind of code-base is the excellent: Working Effectively with Legacy Code
Aug
10
comment I've inherited 200K lines of spaghetti code — what now?
@Govert - Note that in the correct circumstances, a complete rewrite from scratch can be the correct thing to do.