This is strange and funny to read; the only two DBAs I’ve worked with matched this description perfectly.

The first guy was so irate and literally yelling about his entitlement to punish us for making bad architectural decisions that I thought he was joking. I just laughed, but he got angrier. Then it clicked after maybe five or ten seconds – he was in the process of verbally punishing us for querying the database too much.

The second guy was similar, but didn’t yell. Still super protective of his domain, almost antagonistic about us integrating with the database at all.

Both brilliant, taught me more than I can recount here, hilarious and interesting… But total jerks too, and both let go more or less for that reason.

One they had a great system in place and the product felt mature, the companies axed them.

The DBA career did seem to nurture some big egos. They had the keys to the castle, a lot of technical sway and could also have a big impact.

They also earnt good money for a while. When I worked for Oracle, there were lots of stories of Oracle consultants being payed day rates which would still be considered high today.

I’ve seen the same ego with network engineers, they setup some switches and configure a couple vlans but act like they’re the fucking shit because they have a cert.

I think this kind of conflict often comes from frustration at developers not having much understanding of the underlying technology that the network engineer / DBA is responsible for.

Networks & DBs present abstractions, but they're very leaky ones, yet developers often expect to just treat them as magical black boxes about which they don't need to know much of the inner workings, constraints, tradeoffs etc. That makes the interface between the network engineer or DBA and software developers a natural site of conflict.

(You even see this above in this very thread, someone complaining that a DBA was punishing developers for "querying the database too much". Most likely the DBA was actually upset about how they were querying the database, not that they were querying it too much, but the developers want it to "just work" so the distinction isn't important to them.)

So what if per request it makes 1001 sql queries that do a full table scan each? It works!

Isn't that their job? Your mechanic doesn't berate you for being a crappy driver, they get paid to fix your car when it isn't working

If you turn up a few times after destroying the gearbox from shifting into reverse on the highway, they might have a word. I don't condone the berating, I just mean to point out the source of the conflict [0]. A car (especially a modern one) abstracts away its insides much better than a database or network does, too.

[0] The mechanic is also being paid by you to fix your screwup, in proportion to the severity of the screwup. Your colleague is not.

Would they though? The profit margin on replacing a gearbox is pretty good, just like Dba wages

Most mechanics I know would grumble a bit after the third time. It's a bear of a job, and they'd make more profit doing twenty oil changes in the same amount of time.

The DBA's job doesn't generally extend to fixing your code to use database features correctly, write SQL in a sane way, etc. Even if it does at your company, unlike the mechanic they're not being paid by you to do that work; they get their salary regardless. So it's natural that if you keep bringing unpleasant work to them because you're bad at your own job, they're going to get upset.

I think a better analogy would be the engineering team we see frantically trying to keep the engines together in Sci-Fi movies/TV. The DBA is on the same ship as everyone else!

Is this the DBA gone off the rails story thread?

I tried to hire a guy for a postgres DBA at a company I had worked at. I knew him from before as a MS SQL DBA from a previous company and hoped he could fulfill the role, he said he could. The guy saved our asses in the previous case.

We gave him like a month paid time to get acquainted with postgres. Dude DISAPPEARS, gets his vpn keys revoked and everything because we're like what the hell. A month later he sends this big long email saying how he got in some altercation with the police, and landed in jail... it was just way too rambling to take seriously. We ask a mutual friend what the hell was up and he said that since he was working too much his wife CONFISCATED HIS CELL PHONE.

I think we called him 'ballgag ***' (fill in the blank with your least favorite person's name) after that

These guys are worth their weight in gold though, I think I heard he ended up getting a job at Microsoft down the line

I had a colleague who was a DBA who used to be very loud. In a discussion he'd just be louder than you to shut you up. Really nice guy otherwise, btw, and I learned a lot from him. He was just extremely loud.

We used to joke that he was reading/writing so much all-caps SQL code that his brain altered to scream more :)

I guess there are a few stressful things that might trigger this behavior:

- DBAs have the most important thing under their management: data

- Any fault they make can result in downtime, data loss, data corruption, etc.

- They typically have to deal with the same (basic) stuff from developers

- I haven't seen any DBA get involved in the data modeling.

- Work on production is usually when the shit hit the fan

- Work on production can be slow (live, large datasets), which makes things more stressful

I appreciate your point but it’s important we (being people working in technology) never accept or justify this behaviour. If a job is too stressful, quit. There’s no justification for talented, well-paid technologists to stay in a job that triggers them and harm those around them.

I think we, collectively, should strive for avoiding making other people's life stressful.

Just by having a different role, title or label attached to you can be pretty stressful by itself, specially if you are out numbered and decision making is done by number of hands.

The majority not always get that. Also is so common to be exposed to other people's frustration when explaining things, or denying a request, balancing between letting someone shoot their own feet, explaining once again why that is not a good idea, or just restoring a backup later.

I had eerily similar experiences from an older DBA guy, who was going through college in his 40's while working away. He knew his stuff, helped a lot optimizing the ETL process, but could turn nasty in an instant, and had a major chip on his shoulder about younger analysts with college degrees.

Only thing, was this guy had zero programming experience outside SQL and Bash. Anytime he had a question in a meeting about some calling Java process, he used to wait until the meeting was finished and then grab five minutes with me privately to ask about whatever. So there was this perceived weakness that his professional persona "knew everything", which meant he couldn't ask fundamental questions or try to (publicly) learn things outside his domain.

In the end, we moved to Amazon Redshift, and he was progressively moved into a smaller and smaller role, where now he just curates 2-year old JIRA tickets. Probably knows he can't get a similarly well-paying gig elsewhere now.

This is eerily similar to my experiences with two very, very good DBAs I worked with.

I'm now wondering if there is something about the role that lends itself to such behavior. One day they are super pleasant, helpful and friendly. The next they are chewing people out for seemingly minor and random transgressions and saying things like "ruining my fucking database".

Today these guys remind me a lot of JK Simmons character in "Whiplash"

> I'm now wondering if there is something about the role that lends itself to such behavior. One day they are super pleasant, helpful and friendly. The next they are chewing people out for seemingly minor and random transgressions and saying things like "ruining my fucking database”.

There’s something to your observation. Ok, I’ve held enterprise and application DBA roles, literally decades of experience. Sometimes the cruelty and dominance is necessary because of the responsibility focused on the position. I’ve often proposed being over-accommodating is important for non-architect application DBA roles, whereas the implications of SRE and resource planning might require an enterprise DBA to immediately and summarily cut off stupid/ignorant ideas before they acquire momentum and screw things up for the business. A DBA might not have time to be patient when resource constrained. Also, all too often people ‘suppose’ what the data specialist is doing and gum things up trying to be “helpful” when they should be asking for help, costing much frustration.

I’ve had developers try to take on DBA responsibility and find enlightenment when they learn enough to grok the rationale behind my seemingly arbitrary demands...I try to spend time as a developer periodically so I can refresh my developer perspective and not just expect engineers to automatically conform to my narrow perspective.

Wait, what? You are still at the same company as 6 years ago? I thought 2 years is the longest HN users stay with a company.

I’ll be hitting 11 years here in a couple months. We’ve been bought a couple times now, but working on the same product the entire time.

I wonder if he had some sort of https://en.wikipedia.org/wiki/Borderline_personality_disorde... type issue.

The impact that you describe very broadly reminds me of https://en.wikipedia.org/wiki/Stockholm_syndrome. I'm still learning about the subject, so the only nearby useful axis point I'm aware of is the concept of chronic trauma, which I'm surprisingly unable to find a synopsis on in Wikipedia (the closest I can find is https://en.wikipedia.org/wiki/Complex_post-traumatic_stress_..., which is vaguely in the ballpark but a couple notches too far).

Personality disorders have the potential to have the same sort of impact as water on a rock over time. I wonder how this person impacted other people at the company - and whether the boundary-defying nature of this sort of problem caused the line between "broken individual" and "DBAs are scary" to be blurred.

It could be very interesting for the various decisionmakers to wind up in a conversation with a good psychologist (psychiatrist?) who might be able to make that line a little bit clearer for everyone (and provide closure) and perhaps even outline ways to screen for this sort of thing happening in the future - which may be the speedbump everyone's (very quietly) stuck at.

It's a bad idea to start pathologizing bad behavior. The vast majority of assholes are just assholes, with no pathological reason for their shitty behavior. It also stigmatizes those with actual medical problems because "being an asshole" isn't a symptom of any disorder you've listed, yet the association is still being reinforced by comments like this.

Honestly I think it’s most akin to an abusive relationship. You love the person for their good parts/periods, but the bad in reality outweighs the good.