Reputation
7,406
Next privilege 10,000 Rep.
Access moderator tools
Badges
13 32
Newest
 Good Answer
Impact
~358k people reached

  • 0 posts edited
  • 0 helpful flags
  • 560 votes cast
Jan
6
awarded  Good Answer
Nov
21
revised What's the alternative to DRY code when it requires too many parameters?
deleted 17 characters in body
Nov
12
awarded  Yearling
Nov
3
awarded  Nice Answer
Oct
27
awarded  Popular Question
Oct
1
answered What's the alternative to DRY code when it requires too many parameters?
Sep
4
awarded  Nice Answer
Aug
12
comment Development setup for TDD. Is it correct?
@Jodes updated online, but basically the VMs are on a secured network that have network access to the large (shared) systems.
Aug
12
revised Development setup for TDD. Is it correct?
added 368 characters in body; deleted 9 characters in body
Aug
2
comment Where does the Liskov Substitution Principle generally lie in different constructor parameter lists?
Reference to the actual paper: reports-archive.adm.cs.cmu.edu/anon/1999/CMU-CS-99-156.pdf
Aug
2
answered Liskov substitution and abstract classes / strategy pattern
Aug
2
comment Liskov substitution and abstract classes / strategy pattern
While constructors are precluded from the type specification, they are included in the invariant definitions. sec 4.3 of Behavioral Subtyping Using Invariants and Constraints
Aug
2
comment Liskov substitution and abstract classes / strategy pattern
Reference to Liskov's paper: reports-archive.adm.cs.cmu.edu/anon/1999/CMU-CS-99-156.pdf
Jul
13
answered Do objects in OOP have to represent an entity?
May
4
comment 2 methods that are 75% the same?
I think this is a valid question. There are many patterns of code reuse; a product of code deduplication. Going over them doesn't require intimate knowledge of the code as you can enumerate and explain the relative strengths and weaknesses of each. For example inline conditionals, parameterization, inheritance, function/object delegation, mixins, function wrapping (or more broadly Adaptors), functional composition, pipes and filters, etc. Albeit this may be too broad and having the language at least would allow a reduction in the number of patterns available.
May
4
comment 2 methods that are 75% the same?
That it violates SRP is a rather large assumption. Just because code 75% similar between 2 methods says nothing about responsibility, singular or multiple. It could be the exception handling code is duplicated except for a variant behavior such as some additional cleanup.
May
4
comment Thinking pragmatically about scalability
Excellent answer. Questions about scale, for me, always track back to system parameters around use (must be resilient, fast lookup, fast write, etc) and on which dimensions you can expect growth (amount of unique transactions, size of transactions, amount of stored data, data volatility, etc).
May
3
answered How do you unit test \ use TDD methods for ETL's and reporting projects?
Apr
14
comment What do you wish language designers paid attention to?
@Qix: You could still have your do..while, it just wouldn't have it's own special form. It would be a variant of the 1 special form for looping.
Mar
21
awarded  Informed