Reputation
13,504
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
3 47 68
Newest
 Enlightened
Impact
~234k people reached

Mar
21
awarded  Enlightened
Mar
21
awarded  Nice Answer
Mar
8
suggested rejected edit on
Mar
8
suggested rejected edit on
Mar
8
revised How to apologize when you have broken the nightly build
edited tags
Mar
7
revised
added 20 characters in body
Mar
7
revised
added 86 characters in body
Mar
7
wiki
Mar
7
wiki
Mar
7
suggested approved edit on
Mar
7
suggested approved edit on
Mar
4
revised How to handle huge necessary internal processes in user stories?
added 70 characters in body
Feb
26
comment Why is there no language supporting a if..elseif..any..else construction?
This is a highly confusing construct which you would suggest adding in place of the currently clear and concise solutions to the same situation. Also, how you imagine not nesting something in a confusing location to "violate DRY" is altogether unclear. I would say this doesn't exist because it's beyond strange and any language designer would just throw the idea out off-hand as bad design.
Feb
17
revised What kind of security enforces a tree of permissions on it's users?
added 104 characters in body; edited title
Feb
17
revised What kind of security enforces a tree of permissions on it's users?
added 979 characters in body
Feb
17
answered What kind of security enforces a tree of permissions on it's users?
Feb
11
comment Why should I use List<T> over IEnumerable<T>?
@ErikE great point!
Feb
11
comment What was the first language that allowed a class to contain a member of it's own type
This was typical in maths long before programming was even a thing.
Feb
1
comment How do I more effectively design this per its intended design while ensuring I'm meeting SOLID design principles?
@bjhuffine if inheritance absolutely makes sense for what you're doing then go ahead and use it, but look for the option of composition first because it allows a greater flexibility and looser coupling than inheritance. It's typically always preferable to compose pieces of functionality rather than derive them for this reason.
Feb
1
comment How do I more effectively design this per its intended design while ensuring I'm meeting SOLID design principles?
@bjhuffine with composition you could create one Entity class with those pieces of information and you wouldn't need to make other classes inherit from it at all. They could all take that class and utilize it to describe those properties/attributes of themselves. Like in a Building class, instead of inheriting from Business you could have an instance of Business in the building class which describes the business in that building. All the things that Building wants to do with it's Business like CauseInsuranceClaim() it could do through calls directly to it's Business