2y ago

Peak engineering

You're viewing a single thread.

73 comments

Hate to be that guy, but for something bad like this to happen, it's never one person's fault. Like the engineer who nuked the gitlab backup by mistake while production had been deleted. He didn't lose his job and rightfully so, there were a thousand other issues that led to that.
- Recently, YouTube started adding a tracking parameter to their share URLs, when using the "share" button on a video. With this, they can track who is sharing videos with who, and under some circumstances even how they are shared. The tracker starts with the question mark in the link you posted and the link works perfectly fine without that part.
  
  Thanks for pointing this out, I think it's not only youtube that does this and the solution is to edit such link before sharing them, right?
  
  There's the clearurl addon that removes known trackers. But you gotta copy it from the URL bar first.
  
  Thanks, I already have it enabled on all my Firefoxes
- https://www.latimes.com/business/autos/la-fi-hy-vw-hearing-20151009-story.html
  Or when VW management tossed some employees under the non emissions compliant bus.
- There aren't bad employees. Only bad processes.
  
  I struggle with your statement. I've worked with inept people, but they weren't malicious. In one instance the inept person was the DBA. That one guy made the whole team's life miserable. He was a significant reason I quit a job.
  I don't know what framework you could put on a DBA to make them not royalty mess up a system.
  
  But who hired him and why was he still working in that position? That's also failing processes.
  
  That's an interesting thought.
  I was there for under a year. The person in that position before me was also there under a year. As was the person before them.
  I think the manager was frustrated they couldn't get a person to stick around long enough to get trained up to be helpful. I think she couldn't fire the DBA because he was the only guy who knew how things worked.
  The DBA was just one of several toxic people at that role.
  
  You never worked anywhere?
  
  The argument here is having a good process can prevent bad actors (e.g. bad employees) from causing harm due to incompetence or malice.
  
  Maybe, but I could see a dereliction of responsibility in there that is becoming more and more common in my opinion, like processes fall from the sky and employees are just there to follow them and if they fucknup it's never their fault.
  Maybe the right mindset if you are working at subway but I find it offensive for an engineer. Mind you I truly believe in processes, but everywhere I worked processes came from the engineers themselves, often after something went wrong we write a process to prevent a reoccurrence.
  Except for Nathan. Nathan would throw his arms up and say "someone should do something". Fuck Nathan.
  
  And managers
- I love the video
- Don't hate to be that guy. You're completely right

73 comments