Incompetent DBA and incompetent developer. A DB is designed to be optimized for speed, so "lightning fast" has no meaning there; it a consultants term. One can also simply export-copy a part of the DB for reporting
DerekTP123 wrote:taking into account the use cases against that data. A design that might allow for lightning fast single-row updates might be a complete dog when running summary reports.
The DBA owns the server and the data. If he doesn't, he cannot guarantee consistency of the data. How many of the other people involved have done the DBA's training? Where does the arrogance come from to explain the DBA how he/she should do their work? If the work is so simple as you explain, you don't need anyone with an education - since you know it better anyway!
DerekTP123 wrote:If you allow the DBA to dictate the *only* possible structure without proper liaison you end up with inappropriate solutions.
What happens in practice is that the DBA caves in to threats and continous whining, delivers something that he doesn't fully support, and leaves before the sh*t hits the fan. You don't tell the cook how to cook, you don't tell the DBA how to administer his database.
Hahaha, most costumers will not accept that, but that hardly requires negotiations in the kitchen. Once you place your order, negotiations are over.
DerekTP123 wrote:Empire building - in your example, that would be the chef telling the customer what they were going to have for dinner. The customer wants a vegan salad, they get served a rare steak - not a great outcome.
Ah, so now we use philosophy to justify the extra talking? How about biology, as everything we do is related to sex? All life is about sex, not negotiating sex.
"I never negotiated". All of life is a negotiation.
I write code, and do not negotiate. Never have in what's now nearly 25 years of work. The idiots that keep on negotiating are usually the projects that fail. There's a problem-statement, there's specs, there's a way to turn specs into code.
There's nothing that hasn't been done before with databases. Your ideas aren't that unique, as I already explained.
DerekTP123 wrote: I just mean doing something with that database that hasn't been done before.
Collaboration is a bullshit term. Devs work in project teams, and collaboration is nothing new for them. We will even work with people we never seen. Lots of Open Source to prove exactly that.
DerekTP123 wrote:ollaboration and negotiation are the "soft skills" that the IT industry is finally waking up to realising are as important as technical ability.
Negotiations aren't a dev-skill either. Yes, a recruiter will wet their pants when reading those words. Also, the project-team has a sprint to do, and the project-lead should kick your negotiating arse out too - there's a price on what has been agreed, and the lead should not renegotiate.
That's not a developer. We don't need to talk to everyone, because there are specs. The graphics designer is ignored a thousandfold, as I determine how the UI will work.
DerekTP123 wrote:A good software developer doesn't just sit hunched over a terminal, they are involved with people - end users, DBAs, graphic designers, hardware planners etc..
We also do not disturb the people who make hardware; if we need to work together, we'll talk about and define an interface. Last thing we need is more politics in IT, there's already too many people that talk alot, cause more confusion, and do not bring any added value to the table.
..and before you state I lack the soft skills; I'm rather good at it. Might be due to the fact that we never had "collaboration" and "negotiation" in our schooling, but things like "working in a project" and are good enough at our work that we need not hide in countless meetings that lead nowhere.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.