* So you can tell me the exact backup times of everything at Facebook for your machine right? You're an engineer at Facebook therefore under your broad assumption you should be performing the exact same of your statement. If tomorrow everything was to fail at Facebook & there was no data recovery you're saying that everyone in the company should come blame you because well, hell, you're an engineer there after all...
The more reasonable point is that he's an engineer not a sysadmin or ops guy this isn't his responsibility directly & more so this falls on the CTO shoulders of failing to assign someone to this task.
* If they point directly to production this really isn't unheard of.
* Why are we making any assumptions if the guy is fired or not; This has nothing to do with the fact of the bonus not being paid out on time while he was an employee.
* You're going to argue that the company failing to perform backups is confidential information about infrastructure and operations especially after the company mentions it in an email after his employment :|?
* These are emails after his employment & the company is or should be well aware that these emails from that point on can publicly be posted because he's not bound by anything to keep them confidential any more. This is why most companies follow strict HR policies of no further communication & very strict emails to former employees.
Come on, I expect a bit more from an engineer working at Facebook other than broad assumptions & statements.
According to their site Miso have four engineers. At that scale there each and every engineer is responsibility for how things are run. If you want to only do what is assigned to you then you shouldn't be working at a startup. I've worked at small companies who'd punted on revision control and backups, and I made sure those things were put in place. When I haven't had the knowledge or access I've bought up the issue with those who did.
I wasn't trying to ad hominem the guy by suggesting he was fired. For all I know he may have got a better offer elsewhere. I was pointing out that in his attack on Miso he's made himself look bad. If a future potential employer reads this his comments are vague enough they could draw the conclusion I suggested. The same applies to publishing the emails. He may be within the law but to me it's a major red flag.
I shouldn't have to have a disclaimer; this is very obviously my personal opinion. I don't see how my employer is relevant to the discussion. Am I supposed to refrain from commenting at all in case someone tries to tie my professional life to my personal opinion?
Just so you're aware it didn't make him look bad at all & if he was up here in Canada I'd be hiring him but he's not.
He did exactly what any person who got screwed over by any company should do...make it public and call them out on their bullshit.
Thanks to this fellow I will NOT be recommending Miso for their future series C round & this is why no company should screw over their employees it can cost you millions down the road.
I have to say he's handled the attention and criticism really well. His updated posts have addressed a lot of the points I bought up in my original comment.
* The lack of backups is partly your fault. You were an engineer there after all.
* Nuking a production database can happen, but the default assumption is that you are sloppy.
* Based on the timeframes one could assume you were fired from Miso.
* You have no problem revealing confidential information about your former employer's infrastructure and operations.
* You publicly post private emails between you and your former employer.