I want to ask a genuine question to folks here about disaster recovery and management. It sounds pretty horrible, but at what point do you just throw up your hands and give up? How many people in your company would need to be hit by a bus? Or maybe if aws went down completely for a week? I guess I'm wondering: how far into the rabbit hole must we go? I guess the changes of a coworker passing away are more than aws go…
I'm pretty sure he's not a Roman but a Finn. (I'm also quite sure most languages today aren't Latin, namely English isn't. But what do I know, English speakers seem to have a different opinion.)
Finland is the heir of the Roman Empire though: https://i.imgur.com/eNuUdTd.png
I'm having a hard time deciding what's more far-fetched, between this and the actual areas of spread of Finno-Ugric languages.
Involving a technically convoluted mechanism doesn't change the fundamental legal question here. It's just made it harder for you to undo your potential violation. A temporary web mirror has at least a narrow time scope and a justification. Choosing to embed a copy of content you don't own into a permanently-public record is a greater offense.
I wonder where exactly do you see the violation? Is it that I archived it on the blockchain, or that I shared a reader link to that transaction where the article is archived?
I wonder where exactly do you see the violation? Is it that I archived it on the blockchain, or that I shared a reader link to that transaction where the article is archived?
But for better understanding, I would love to hear more about "embed a copy of content you don't own into a permanently-public record is a greater offense". What is this based on? Are there any known precedents?
I am bothered by the fact that Linus is made plural as "Linus Torvaldses" and not "Lini Torvalds".
I'm pretty sure he's not a Roman but a Finn. (I'm also quite sure most languages today aren't Latin, namely English isn't. But what do I know, English speakers seem to have a different opinion.)
(I actually checked, and turns out the name Linus comes from Latin―which however doesn't change my position on using local grammar.)
Real Story Here. A colleague and I developed a training course on the Foundations of DevOps. We started the course off with a discussion about risk in Software Delivery and IT in general. Attendees would often surface the "Key-Person Risk" or the "Hit by a Bus Risk" to which we would use as a teachable moment for pair programming, cross pollination, and measuring and improving the time it takes for new joins to becom…
I'm very sorry for your loss. I've heard "wins the lottery" as a less morbid metaphor for the same concept: one of your employees stops working in a low-probability event. Of course the higher-probability event is leaving their job (but somehow it's less polite to just say that); you usually get two weeks to hurriedly start documenting things, and with the current state of employee/employer relations you might easily…
In the "wins the lottery" and "left for a new job" cases there is at least the possibility of knowledge transfer. I was brought in on a situation where the primary IT lead suffered a stroke, rendering him unable to communicate for weeks. We had to reverse engineer everything, crack passwords, rebuild servers, etc. This is, unfortunately, my go to example of the need to mitigate risk of a central point of failure.
the problem with 'wins the lottery' as a metaphor to me is basically that one is calling the winner a jerk.. if I suddenly could retire without a care in the world, I probably wouldn't mind dropping in for a day or two every now and again for knowledge transfer, even if I didn't like the company overall, to help my teammates..
I am the same way, but we are not the norm. In fact, most people don't even want to provide the occasional consulting once they leave the team (but stay at the company), let alone the company. There's also the problem of where to draw the line. Is a quick question ok? What about a bunch of questions? What about asking for a training session? What if the question requires diving back in to the source code to answer? E…
Yep. In every company I've been in here in the UK, I have pretty much never heard of an ex employee returning to explain their work, fix a bug, do training, etc. And well, the more people leave a company, the less likely they are to come back to help at all, cause of a 'toxic' atmosphere or sub par working conditions.
Its not the norm outside VC-backed tech land There is just a lot of stuff to build and a salary that needs to increase 30% every other year
I see all the comments about needing huge pay bumps every 2-3 years and then I also see things about how you can’t get a job in sv over 40. I wonder if it’s related