3 ms·
> someone fubared the initial database config Utter incompetence. Developers seem to have this almost-magical ability to blame management for their fuck-ups. G
by vinceguidry 10y ago
> someone fubared the initial database config
Utter incompetence. Developers seem to have this almost-magical ability to blame management for their fuck-ups. Guess I can't blame them too much, there's practically no decent software engineering training anymore. All we get is irrelevant science-y shit.
> We came up with a plan that would eliminate the risk,
You don't call it a risk if there's a 100% chance. Managers are not going to understand scenarios you put in front of them, you have to guide the conversation. You say, "this is going to happen if we don't fix this right effing now." Then you threaten to quit if they don't take you seriously. But again, professional pride is something nobody teaches developers.
- hackits 10y agoI would say that the threatening to quit because they don't take you seriously kind of re-inforces their view point why they don't you take you seriously in the first point.
- vinceguidry 10y agoIf that's the case then they're only hiring you for grunt labor and you should quit anyway.
- Spooky23 10y agoIt was a mess that I had inherited, this was 16 years ago... my guess is that they weren't aware of some of the platform differences as they transitioned to Sun. But yeah, total fuck up. Keep in mind I was newb, 4-6 weeks out of college. A dramatic walkout wouldn't have proven anything. They'd just blame me and dirty up my name. The management made a dumb call. Today, I'd probably be able to stop a situation that ridiculous, but I'm also a more respected professional with more conference room time.