The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I'm assuming you are talking about poorly gathered requirements.
Yes, but not just.
I've inherited a database and has been given the task of making it work according to new intentions.
And while it's actually quite fun most of the time, I would at other times find it even funnier to meet the original designer and teach him the virtues of normalization using a bundle of nettles.
The biggest problem is that he didn't have the domain knowledge to use the correct keys.
Then again, he's been using a surrogate key (identity) for a year table. Yes, it has two columns (YearID, Year) .
FORMAT(y.Year, '0000') + '-' + FORMAT(m.Month, '00') + '-' + FORMAT(d.Day, '00') AS OrderDate
FROM SalesOrder o
JOIN Year y ON y.Id = o.YearId
JOIN Month m ON m.Id = o.MonthId
JOIN Day d ON m.Id = o.DayId
I had a customer say to me once, "I won't know what I want until I see it." Yes, that is a direct quote. He was definitely the worst customer I have ever had but there are some serious contenders. The top two are both quite large companies and I do everything I possibly can to avoid buying their products.
"I won't know what I want until I see it." Yes, that is a direct quote. He was definitely the worst customer I have ever had
Really? That is pretty much how all customers are. They might know what they need it to do but as far as UI design, for example, they have no clue what they want until they see it. That's pretty normal in my experience.
Everyone is born right handed. Only the strongest overcome it.
It is quite far from normal in my experience. My customers have run the entire spectrum of zero specifications to every detail fully specified down to the colors of the items on the user interface displays. Even those with no specifications would say things like "do it like this one" or "do it like the last one was." In this customer's case, they actually had a specification but this guy treated the whole thing as being optional and we were at his beck and call. He ended up delaying the project so badly that when we were asked about it we said because of (this guy) and when his bosses saw the absurdities things were changed in a big hurry.
We have this as SOP, users come to us with an idea, partial spec is proposed and accepted, prototype developed and then the real requirements begin to emerge. Been doing it that way for 30+ years, I have never worked from a complete spec in my entire career.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
had a customer say to me once, "I won't know what I want until I see it."
Handled properly these are way better than clients that give you a whole mess of specs...
often in a small co: written by a boss who doesn't really know what the underlings need nor appreciate how it's done now and even less how it could be done better.
often in a large co: written by a bunch of idio "consultants" who get led around by a boss and never really ask the users as all they do is listen to the boss who <copy above="" item="">.
For mine, the less specs the better, talk to the users, don't ask them "what they do," but rather "what do they need to get done and what's the best way to get it done (with respect to, if any SOP)"
End result is a combination of application and business improvement, the staff will be happy, the boss will be happier as he gets happy staff and improved productivity.
Put simply: Show me someone that asks for specs and I'll show you a junior programmer.