- Joined: Jun 20, 2018
- Last Login: Nov 23, 2021, 8:03pm EST
- Comments: 378
Share this profile
No, it’s either gross negligence or complete incompetence if true. Leaving a publicly known critical 0-day security vulnerability unpatched for a year is NOT something that should be happening on any professional dev team, even a small one. You either fix it or hire a consulting firm that can.
Comment 1 reply
Seriously though, even when we don’t explicitly screw up, there’s also the time pressure to fix things quickly instead of correctly, which in turn makes it harder to debug next time.
Comment 1 reply, 11 recs
That would never happen. Every pull request I send in is bug free an 100% to requirements, and that’s the story my lawyers told me to stick to.
Comment 1 reply, 1 rec
I was also considering ordering a Model 3 this year, but I ended up deciding on a hybrid instead and an EV next time after:
A) other manufacturers catch up
B) Tesla’s promoted killer features are less half-baked (looking at you FSD) and they ditch the cowboy CEO.
Comment 1 reply, 13 recs
Irrelevant. If the car I paid for is missing standard features of said model without being notified, I’d probably be banned from the dealership for life by end of day if they pulled this crap.
If they let me know ahead of time, even if that was after the time of the contract, I’d be cool with it.
I don’t expect miracles, just honest communication.
Yeah. I need a 3090 myself for some ML projects. Compute units for training NNs on Amazon rack up fast, and I can’t justify the continued cost. I’m a gamer though, so a sweet upgrade that also allows me to do some decent (basic) ML projects can’t be justified, but it CAN be rationalized, and that’s good enough for me.
Was their a point to your whining?
Comment 1 reply
3 days offline and it (supposedly) wasn’t related to a breach? If that is true … and I’m skeptical it is … pretty much the entire IT team and CTO need to go.
Comment 1 rec
If you were ever down for over 24 hours for anything BUT a breach (because of LE involvement), your team wasn’t very good. Even 24 hours w/ a breach is not a good look for a company of this size.
Comment 2 recs
Yep. Thought the same thing. Any configuration issues would have been resolved by now. Short of their DC burning down, equipment issues would have been handled as well.
Data loss would have been mitigated by backups unless they were A) compromised or B) being analyzed for a potential compromise.