Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
4
Newest
 Teacher
Impact
~77 people reached

Jan
22
awarded  Teacher
Jan
22
answered Design - shallow routes for an API
Jan
22
comment Design - shallow routes for an API
Also, are the IDs used to identify an employee globally unique, or unique within an individual database?
Jan
22
comment Design - shallow routes for an API
Will the same user generally be connecting to more than one database when using the API? Or will the majority of users connect to a single database, but different users will connect to different databases?
Jan
20
comment Specify optional parameter names even though not required?
@NiklasJ - I like the Flags approach because it allows the caller to pass WhatToInclude.Managers | WhatToInclude.Cleaners and the bitwise or expresses exactly how the caller will process it (i.e. managers or cleaners). Intuitive syntactic sugar :-)
Jan
20
comment Specify optional parameter names even though not required?
I like the enum approach, but I'm not a huge fan of mixing Include and Exclude in the same enum as it's more difficult to grasp what's going on. If you want this to be truly extensible, you can make it a [Flags] enum, make them all IncludeXxx, and provide a IncludeAll which is set to Int32.MaxValue. Then you can provide 2 ReturnEmployeeIds overloads - one which returns all employees, and one which takes a WhatToInclude filter parameter which can be a combination of enum flags.
Feb
13
awarded  Editor
Feb
13
revised Is throwing an exception an anti-pattern here?
Fixed spelling
Feb
13
suggested approved edit on Is throwing an exception an anti-pattern here?
Jun
13
comment Should I tell a departed coworker about their “sev 1” defect?
@user16764 - I think you mean The Daily WTF?
Sep
15
awarded  Supporter
Sep
15
awarded  Autobiographer