meta user
network profile
| bio | website | linkedin.com/in/… |
|---|---|---|
| location | Seattle, WA | |
| age | ||
| visits | member for | 2 years, 6 months |
| seen | May 19 at 3:29 | |
| stats | profile views | 216 |
Senior software engineer and sysadmin with experience in scalable software, front and backend web software, ETL tools, configuration management, automation, and continuous integration. Currently a team lead using a mixture of Agile and Lean methodologies as well as ATDD.
|
May 13 |
comment |
Pythonic way to map a function from one module to a method of a global object Is the purpose to write a simulator or to test your code? The simulator needing to stand on it's on will require a different design than one where the simulator is incidental and the real purpose is to test the embedded code. |
|
Apr 28 |
comment |
Coding style (do more, then simplify) Unnecessary length is orthogonal to TDD. Overcomplication is not TDD because your initial implementation is supposed to be the simplest code needed to satisfy the test. |
|
Apr 27 |
revised |
Python multiple inheritance or decorators for composable behaviours edited body |
|
Apr 15 |
revised |
Resources for improving your comprehension of recursion? added 234 characters in body |
|
Apr 10 |
revised |
Python multiple inheritance or decorators for composable behaviours edited body |
|
Apr 9 |
answered | Python multiple inheritance or decorators for composable behaviours |
|
Mar 18 |
awarded | Nice Answer |
|
Mar 18 |
revised |
Why is it often said that the test cases need to be made before we start coding? added 238 characters in body |
|
Mar 11 |
revised |
Testing a REST client against a REST Server. How to do fixtures? added 124 characters in body |
|
Mar 9 |
answered | Testing a REST client against a REST Server. How to do fixtures? |
|
Mar 6 |
comment |
TDD - is it just about unit tests? @Phil in practice you may refactor a large piece of code with a few tests, but end up breaking a significant number of other tests that rely on that structure. You still go back and fix those tests, but they do get broken get broken. |
|
Mar 5 |
answered | TDD - is it just about unit tests? |
|
Mar 5 |
comment |
TDD - is it just about unit tests? Structural changes will cause unit tests to break. A trivial example would be a method name change. There are plenty of other examples though. I have gone through and completely changed the structure of classes/objects by combining them, splitting them, etc. The behavior of the system stayed exactly the same, but the internal structure completely changed. These cases have definitely lead to broken unit tests. Any refactors that occur at a larger granularity than the unit have the potential to break the unit test without changing system behavior. |
|
Feb 23 |
revised |
If your unit test code “smells” does it really matter? added 122 characters in body |
|
Feb 23 |
comment |
Why aren't design patterns added to the languages constructs? Your question sounds backwards. Why would you ever want to include more in the base language when you can push it out into a library. You always want the language to be small for maintenance, management, and to prevent bloat. |
|
Feb 19 |
awarded | Caucus |
|
Feb 18 |
accepted | Why is nesting or piggybacking errors within errors bad in general? |
|
Feb 18 |
comment |
Do changes in performance violate the Liskov Substitution Principle? Barbara Liskov is very specific about what is and isn't covered. |
|
Feb 18 |
revised |
Is currying too complex a tool to actually use? deleted 1 characters in body |
|
Feb 17 |
answered | Is currying too complex a tool to actually use? |
