Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • nice analysis - however, I wouldn't say I have any stature as a dev in my day job, except that I am the only one here who knows anything about db/c#/vb/etc... so guess I'm part time dev by default. this is a fairly small project, so the consultants sheer number of tables and joins left me saying "wtf" (but thanks to you fine folk I am now saying "oic...") Commented Sep 30, 2011 at 18:09
  • Quite an old topic, but still relevant... refactoring may be very hard, imagine you need multiple departments in the future instead of one, but have only a department ID in Users as FK. You will likely end up with duplicate referendes (Users.DeptID and UsersDepartmentsTable) or complete garbage, like comma-separated lists in Users.DeptID, or XML. The correct solution could not be easily added, as suggested by YAGNI or KISS, but would be obstructed. Commented Oct 5, 2015 at 9:45