10,963 reputation
53350
bio website stackoverflow.com/users/…
location Columbus, OH
age 41
visits member for 3 years, 10 months
seen 3 hours ago

Programmer

.Net (Asp.Net/C#/VB)
XML
PHP
Perl
JavaScript

Web/Windows


Dec
18
comment Is reinventing the wheel really all that bad?
Attributed to Douglas Crockford: The good thing about reinventing the wheel is that you can get a round one.
Dec
12
revised C# OOP Class Usage
added 5 characters in body
Dec
12
comment Real-world examples of failed businesses because of technical debt
@Dibbeke: I think it's a valuable question, but in the format for questions here it should be rephrased so that one answer can be viably accepted as the "real" answer. In the current format, you could receive hundreds of answers all of equal value.
Dec
11
answered C# OOP Class Usage
Dec
11
awarded  Custodian
Dec
11
reviewed Approve How do I tell my boss that their custom cms is terribly inefficient?
Dec
11
reviewed Approve How do I tell my boss that their custom cms is terribly inefficient?
Dec
11
answered How do I tell my boss that their custom cms is terribly inefficient?
Dec
5
comment Emotional detachment from bad code
Let us continue this discussion in chat.
Dec
5
comment Emotional detachment from bad code
@Telastyn: In my experience, situations get this bad because too many people are off in the corner doing their own thing instead of communicating, establishing a standard, pattern, architecture as a team and making the conscious choice to move forward. I'm not saying "rely on leadership". I'm saying be the leader and hold management accountable.
Dec
5
comment Emotional detachment from bad code
@Telastyn: It needs to be fixed from the top down. The developers need to get with leads and determine a modernization/correction plan, get with project managers/supervisors to determine when/what can be refactored, etc. Impacts have to be determined, and it needs to be agreed upon at an organizational level (team level at the very least). First and foremost, a standard must be developed and agreed upon.
Dec
5
comment Emotional detachment from bad code
...and would require project oversight most likely. I'm not saying the developer should do nothing. But a developer blythely taking it upon themselves to decide what's "right" for the codebase is foolhardy, arrogant, and a recipe for an even worse situation.
Dec
5
comment Emotional detachment from bad code
@Telastyn: But many negative actors working independently on their own agenda will make the train wreck so much worse. Coupling the phrased excuse "this is too much work" with the concept of "not doing your job" refutes your statement of applying this to non-controversial things, and OPs question asks deliberately about something that would be an architecture change (his item #1). Typos are relative, bad variable names should have a definition of "bad" based on a team standard or company standard, gigantic functions/classes may require significant retesting when refactored...
Dec
5
comment Emotional detachment from bad code
-1: The tactic you're suggesting will actually only lead to more code rot. If every developer simply decided that his/her way was better and thus took it upon themselves to refactor every thing they felt in their opinion was bad no one would get anything meaningful done because the code base would be in a constant state of refactor. This is such extraordinarily bad advice.
Oct
28
comment Is it permissible to use explicit interface implementation to hide members in C#?
I worked with a guy who did this on a regular basis. It drove me absolutely nuts.
Oct
16
comment In ASP.NET MVC, should the view models have an ID?
You have to abandon statelessness. - You have just made the choice to use MVC pointless.
Oct
7
answered Abstract Class confusion
Oct
4
comment In the light of the open / closed principle, is shared code ownership still important?
@Giorgio: That's through extension. You can modify behavior through extension. However, the original entity should not be changed directly for the purpose of modifying behavior. It should only be modified to correct bugs that are introduced from outside factors. If the original intended behavior is not the desired behavior, but it still functions without error, then extension is required to illicit new behavior.
Oct
3
answered In the light of the open / closed principle, is shared code ownership still important?
Sep
19
awarded  Notable Question