Guess what? I *AM* an asshole.

If you want "nice" managers and project leads, check the unemployment lines.

I'm guessing you're a twenty-something who grew up in the age of "everyone gets a trophy" instead of learning that failure IS an option.

Self-training is YOUR responsibility. The days when companies would pay to train you have been over for 20 years at least.

The fact that he treated it as "free time" instead of investing in HIS OWN CAREER is the problem.

Although the copyright holders can send out threatening letters here in Canada, they're not allowed to collect the thousands of dollars that they do for "infringement" in the US. They're only allowed to collect *actual* damages.

So if you're a "leech" and just download without sharing later, they can only claim the loss of one copy. If you shut off your torrent after uploading to a 1:1 ratio, they can only claim loss of one copy.

It really takes the wind out of their sails and their idle threats if you know that fact and can respond to them appropriately. Their claims that you could be subject to "thousands" of dollars of damages is absolute BULLSHIT under Canadian law.

Sounds right to me, except for the assumption that link batching would necessarily increase latency. I believe tor already handles asycnronously in most cases and only rotates circuits as needed or about every 10 minutes.

So circuit creation time, generally speaking, should have little effect that the user can see (unless he requests a new circuit through a control app).

I hate to tell you this, but I wouldn't hire you no matter what "skills" you try to pick up in two months time.

You knew the project would finish someday, yet you spent three years content to sit on your arse and while away the time on the current project instead of learning something new at home on your own time.

You dropped the ball. You didn't plan.

And because you don't plan ahead, I wouldn't want you.

I came here to say a lot of this. Especially since, as I have gotten into the devops world myself, and there is a bit of an equalizer in that a lot of the big buzzwords are things that most people have kind of similar and easily obtainable levels of experience with.

Chef hasn't been around so long that there are many people with more than a couple of years epxerience....but its also all done in ruby, which is decently easy to pick up at a basic level, especially if you know perl. You could easily get yourself up to speed, especially with any sysadmin background.

If you can make it through the level of the advanced chef courses, which, seriously, for someone who knows what they are doing we are talking, a few weeks here you could be up to speed with most candidates out there. Which isn't a dig on them at all, its just that, most of the experience from administrative work or writing, running services is directly translatable, its really just a new toolbox to get get familiar with; for someone who can already fill admin and dev shoes, its a very natural move

Hard to say but it will happen eventually. I have seen it go a few years, then lose 2 within a few months. Always make sure monitoring works and will alert you if its degraded. You can run degraded mode for a long time without monitoring.....till the next one fails.

They are mechanical, so manufacturing quality and environment will factor in. My drives likely see a lot of shake and heat being on the third floor of a 100 year old house, between the wind, the washing machine and seasonal heat.... its no data center in here.

Well for starters, the people on Hacker's List apparently. If you really wanted to know who they are, you can, in fact, easily go ask them.

I must admit it's been a few years since I last used C#, and I've yet to shift from Java 7 to Java 8. Both have moved forward.

But at the point I was heavily using both, they were more alike than different. At that point, LINQ had just come out so no one was using it for production systems yet.

I have been running a 4 disk RAID 5 array for a few years now at home, and did a replacement upgrade a couple of years back.

Overall I find in a 4 disk scenario I lose just a bit less than one disk per year. Maybe one disk every year and a half.

So when you say RAID 0 that is 3 years old, that sounds about right. I would call such an array in serious danger of loss.

What amuses me is that many people rave on about how great C# is, while denouncing Java. Yet other than a few minor syntax tweaks (like the way you write getters/setters and the "?" indicator for nullable attributes), they are virtually identical right down to the API.

They're both very easy to read and code with, and if you know the packages/libraries of one you'll find the equivalent in the other in short order, with very, very few differences in the details of the APIs.

Yet C# is "great" and Java "sucks".

Go figure.

>The other reason to regenerate frequently is to limit the window of opportunity for brute force attacks, but that doesn't make much sense either:

Lets not lose sight of the fact that, even doing it only once EVER, even if you then redistribute that result to every future machine you build, is already far better than the status quo.

The current standard appears to be "use the same default ones distributed to everyone else". So really even "each unique machine generates a new set once" is a massive improvement and downgrade to the usefulness of breaking any given prime.

That was my solution too, it took longer to realize it wasn't trickier than that than it did to realize the solution.

Though the solution only works if you assume the earth is a sphere and north means the where the current pole of the planets spin is and not magnetic north. However those are pretty normal assumptions for a brain teaser.

as a gauge of how easy it is I asked my wife since, she isn't someone who has done math for fun or played 1000+ hours of kerbal..... and well her answer was "Why are you asking me this? does this have a point?" Maybe I would have gotten better data after she finished her coffee?