Reputation
4,297
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
9 28
Newest
 Cleanup
Impact
~126k people reached

Aug
14
reviewed Approve How to approach program design with respect to data strucutres and algorimths - is there an equivelant of the OO design process for d.s.'s + algs?
Aug
13
answered Question about mocking externals
Aug
12
awarded  Yearling
Aug
11
comment Is splitting up a function into several inner functions an anti-pattern?
If you think Clean Code is "the bible for devs", you should read Code Complete.
Jul
29
comment Avoiding Double POST
Why are you worried about this?
Jul
25
revised In a REST service project, where should we put code that calls a third party REST API?
made the title more generic; improved RestTemplate link
Jul
23
revised Omitting “destructors” in C is taking YAGNI too far?
spelling
Jul
23
comment Improve coding quality
Reading Code Complete is a great start.
Jul
21
comment Web Service REST clarification
@Residuum - multiple PUT requests to the same URL should not insert a new entity every time. If the entity already exists, it will simply replace its current state with that given. The effect of N PUT requests to the same entity URL is the existence of the entity with the given state.
Jul
21
answered Web Service REST clarification
Jul
21
revised Web Service REST clarification
grammar, formatting, tags
Jul
18
revised Should we avoid using design patterns in constantly changing projects?
grammar
Jul
15
revised Started wrong with a project. Should I start over?
improved the book link
Jul
9
comment Program Design clearness vs convenience
One option would be to add a source property to DomainObject and set it to the filename when loading from a file. This provides the info your colleague wants without breaking encapsulation or leaking the abstraction too much.
Jul
1
comment Should I be using a composite key for this table?
See dba.stackexchange.com/q/8334/13333
Jun
27
answered Good or bad practice to mask Java collections with meaningful class names?
Jun
25
comment When to stop reviewing code?
Code quality and defect detection are both products of code reviews. I recommend you read chapter 20 "The Software Quality Landscape" of Code Complete. It opened my eyes.
Jun
25
comment When to stop reviewing code?
Part of the goal of code reviews is absolutely spotting bugs. Testing will never catch everything, so multiple defect detection techniques should be used. See Code Complete, Table 20-2 for details on defect detection rates of various methods.
Jun
20
reviewed Approve Serialized values or separate table, which is more efficient?
Jun
19
reviewed Approve How to check the space complexity of this program?