4,172 reputation
21729
bio website daedtech.com/blog
location Chicago, IL
age 34
visits member for 2 years, 9 months
seen Jul 9 at 20:20

The more I learn, the more I learn that I have to learn. :)

Find me on Github, Sourceforge, and Twitter @daedtech


Oct
30
answered Assigned to a new WPF project, know nothing about it
Oct
17
answered How easy is it to change languages/frameworks professionally?
Oct
11
answered How important is positive feedback in code reviews?
Oct
10
awarded  Yearling
Oct
5
comment What's the opposite of cohesive?
I understand the difference between the metrics, but I'd say disjointed is closer to opposing "cohesive" than "coupled". Disjointed is an antonym for "coherent", which I'd say is closer to "cohesive" than "coupled". Coherence and cohesion both imply rational grouping, whereas coupled just implies proximity. My take, anyway, for what it's worth. (edit - I guess it's also the opposite of "joined" though, obviously, so that maybe puts us back at square one :) )
Oct
5
answered What's the opposite of cohesive?
Oct
2
awarded  Popular Question
Oct
2
awarded  Good Question
Sep
5
awarded  Civic Duty
Aug
31
answered Name for this antipattern? Fields as local variables
Aug
30
answered What to do when projects are slow and you are being held up by others?
Aug
15
answered Why do we need to separate classes which have different functionality?
Jul
19
answered Are Design Patterns SuperSet of OOP or SubSet?
Jul
14
answered Use verbs with functions, nouns with classes - what about interfaces?
Jul
12
answered Are Persistence-Ignorant objects able to implement lazy loading?
Jul
8
comment How can I quantify the amount of technical debt that exists in a project?
@ZoranPavlovic Your bizarre and unsolicited false dilemma is missing a third option: I wanted to know if there were any tools that attempted to quantify technical debt.
Jul
4
comment Something confusing about Single Responsibility Principle
I mean, I can only say so much when speaking in hypotheticals, but yes, something seems fishy about two vastly different classes always needing to change at exactly the same time, like it would seem fishy if you always needed to replace the tailpipe of a car when you replaced the steering wheel. There may be a reasonable explanation for it in your situation, but that's why it's a design 'smell' and not necessarily a problem. It just seems... curious.
Jul
4
comment Something confusing about Single Responsibility Principle
I would say so. I mean, the fact that two classes/responsibilities may change at the same time for the foreseeable future doesn't mean that will always be true. Though, I would offer the caveat that it would be easier to comment on specific examples. Two classes that are always changing at the same time only might be a design smell.
Jul
4
answered Something confusing about Single Responsibility Principle
Jun
26
comment Moving from mock to real objects?
As for the "when", I think most people run unit tests regularly (either continuously with a tool or as often as saving files) while they develop. Integration tests are probably run about as often as source code promotions/deliveries happen. Beyond that, I'm not really sure what you mean by "design versus implementation". Using mocks is designed to isolate your classes so that you can test them individually without juggling too many balls at once. Your unit tests are testing implementation.