5 ms·

What a terrible abuse story. > if the project failed in a production environment it would be a “go home, stare at a revolver, wonder if you should use it” sit

What a terrible abuse story. > if the project failed in a production environment it would be a “go home, stare at a revolver, wonder if you should use it” situation. Oh mate, you are taking your job too seriously. You should go and do 100% of what you can, and if the project still fails, hey it wasn't your fault. Some tasks are FUBAR before they arrive at your desk and there is no point in worrying about that. > “Why were you using Python?” the Director of Engineering asked. Why are you asking that after the project is done? What kind of twisted upside down world is where this question is appropriate at that point? I don't know what exactly a Director of Engineering is expected to do at that joint, but if this question even comes up after development that means that they are very hands-off and the company doesn't have the right processes. > “Yeah, well. Murderboard.” DirEng shrugged. Oh jees. That level of casual indifference. They are probably even proud of their terrible processes.

Angostura 5y ago
I couldn't quite understand why the answer to the "Why were you using Python? question wasn't "We carefully assessed the client's ability to maintain and use the code - which is a critical requirement..."
- goohle 5y ago
  ... and used Python instead of a language with good compile-time safety enforcement, like Ada, because Python is easier to learn by noobs.
  - donkarma 5y ago
    if you read the story they picked Python because the sysadmins knew it and they had to know the language in order for them to maintain it
    - goohle 5y ago
      So, they picked Python because it is easy to learn by noobs. Yeah, this changes everything.
- belval 5y ago
  Probably because we're reading it in a low-stress situation where we don't fear for our job and can think clearly. While I can only speak for myself, if I'm getting talked at the way this guy was being talked at, I'd probably forget the requirements too.
stavros 5y ago
Seriously, what the fuck. There is no good part to this story. If I'm the Director of Engineering and I have to deliver a project and I find out at the last minute that they've been doing it wrong for months, it's my fault and nobody else's. If it's fine, why would I chew an employee out? This story is fucked up (not just screwed up).
pjc50 5y ago
I mean, presumably that's why it's called "murderboard". This reminds me of the old BOFH stories. There's a lot of casual verbal brutality in older engineering/ops cultures, that's why people invent things like "#hugops" to try to soften it a bit. It is not how things should be done in 2021.
Mandatum 5y ago
> Oh mate, you are taking your job too seriously. You should go and do 100% of what you can, and if the project still fails, hey it wasn't your fault. Some tasks are FUBAR before they arrive at your desk and there is no point in worrying about that. Agreed. This is exactly the type of person that shouldn't be working on these types of projects. Yes, take the job seriously. Yes, feel responsible for your own actions. But don't assign all blame to yourself before you even start. Treat yourself as you treat others.

Angostura 5y ago

I couldn't quite understand why the answer to the "Why were you using Python? question wasn't "We carefully assessed the client's ability to maintain and use the code - which is a critical requirement..."

goohle 5y ago
... and used Python instead of a language with good compile-time safety enforcement, like Ada, because Python is easier to learn by noobs.
- donkarma 5y ago
  if you read the story they picked Python because the sysadmins knew it and they had to know the language in order for them to maintain it
  - goohle 5y ago
    So, they picked Python because it is easy to learn by noobs. Yeah, this changes everything.
belval 5y ago
Probably because we're reading it in a low-stress situation where we don't fear for our job and can think clearly. While I can only speak for myself, if I'm getting talked at the way this guy was being talked at, I'd probably forget the requirements too.

stavros 5y ago

Seriously, what the fuck. There is no good part to this story. If I'm the Director of Engineering and I have to deliver a project and I find out at the last minute that they've been doing it wrong for months, it's my fault and nobody else's. If it's fine, why would I chew an employee out? This story is fucked up (not just screwed up).

pjc50 5y ago

I mean, presumably that's why it's called "murderboard". This reminds me of the old BOFH stories. There's a lot of casual verbal brutality in older engineering/ops cultures, that's why people invent things like "#hugops" to try to soften it a bit. It is not how things should be done in 2021.

Mandatum 5y ago

> Oh mate, you are taking your job too seriously. You should go and do 100% of what you can, and if the project still fails, hey it wasn't your fault. Some tasks are FUBAR before they arrive at your desk and there is no point in worrying about that. Agreed. This is exactly the type of person that shouldn't be working on these types of projects. Yes, take the job seriously. Yes, feel responsible for your own actions. But don't assign all blame to yourself before you even start. Treat yourself as you treat others.