My story: Been using Linux and BSD heavily since the 90s. I don't really care if you spell "restart foo" as "/etc/init.d/foo restart", "/usr/local/etc/rc.d/foo.sh restart" "service foo restart", "systemctl restart foo", or just "pkill foo && foo". As an end user of the init systems, those are fungible.

As a developer of things that uses the init systems, there's a huge difference. SysV and BSD inits are close enough in functionality that if you learn one, you can pick up the other. systemd changes that totally, in ways that many of us aren't convinced are actually better. I love learning new stuff! I just changed jobs to learn new stuff! New stuff is cool... but only as long as there's a reason for it. I don't see systemd as being advantageous, at least on the server machines where I spend my days.

I'll be happy to pick up systemd if and when 1) there's no alternative short of maintaining my own private Debian fork, or 2) I can see a reason I'd want to rip out the tried and true, Unix-philosophy-conformant "do one thing and do it well" init systems we have today. As of this moment, systemd seems to do way too much. Given that it's a single point of failure for an entire host, that makes me distrustful.

I bought a Synology NAS and it comes with something called Cloud Station, which is basically Dropbox. You install the client on your machines and it keeps your ~/CloudStation folder in sync with your own NAS. Your data never leaves your personal control. I currently have about 4TB of open storage, which is a little more than the 8GB or so of Dropbox I've accumulated over the years.

I'm sure other NASes offer similar arrangements. Pick one you like, install it, then forget the whole idea of paying some company $$$ per month and praying they care about your privacy.

To be fair, Agile can be freaking awesome. I worked at a devotedly Agile shop and it was a developerocratic utopia. After the few meetings we had, all participants walked away with legitimate action items. You didn't just get called in to listen to something that didn't concern you - if you were invited, it's because you were specifically needed.

I've also worked in places where Agile was a stultifying cover story for "actually waterfall but that doesn't sound as cool so we'll never admit it". That might be the kind of /dev/hell you found yourself stuck in. But that's not Agile Done Right, and shops that Do Agile Right really do exist.

I know all of those words but still have no idea WTF the summary is talking about. Does this boil down to "Wikipedia teens with infinite free time are trying to build fiefdoms", which is the usual explanation for Wikidrama?

I'm perfectly happy with the compensation of "we'll let you use the Internet connection you already had if you want to not come into the office and be distracted by a hundred meetings and other interruptions".

Ummm, no. The skills required to be a good engineer are not the skills required to be a good manager of engineers. There's some overlap, sure, but you can be an outstanding engineer but have poor leadership skills, or be an amazing and revered leader but terrible at actually designing the stuff your people are working on.

You should be in charge of exactly as many people as you are good at being in charge of. That's unrelated to how good you are at being one of the workers.

Here is a table of National Stock Numbers: http://www.gsa.gov/dg/NSN_DATA...

If anyone is interested, I can import both spreadsheets into a PostgreSQL database, join by the NSNs, and post a dump/query/something.

Or Go, which looks a lot like C Done Right, was designed for systems programming, and has a positively minimal learning curve compared to C++. I get why C++ exists and what problems it aims to solve, but I don't think I'd want to have to use it to solve those problems when there are more programmer-friendly alternatives.

I have Comcast, and have native IPv6 over my home-grade Internet connection. I can ping6 www.google.com from my autoconfigured laptop without problems.

I don't doubt that they're slow rolling it out everywhere, because when has Comcast ever been in a great hurry to upgrade their network? But here, at least, it works as advertised.

Wow, your setup sucks. My ISP offers native IPv6 and all our laptops, tablets, etc. come up with both protocols live. I have literally never, not once, zero times, ever had a problem that traced back to having IPv6 enabled. Maybe we just buy better equipment or have a better ISP or something, because it Just Works for everyone in our household.

Note that I'm not actually complaining about faster-than-needed Internet. :-) Comcast had 50Mbps service for a small price bump over 30Mbps when I signed up, so we went with it.