Works offline too (my netbook has a full checkout, incl. history).
Only real downsides:
* Doesn't work natively on my iPhone
* I have to remember to push/pull when I make changes (but even here, I just have to manually merge changes - nothing is "lost")
Git + GPG + a GPG-VIM plugin.
I use "vim" to edit my password file as if it is plain-text; git pull/commit/push to make changes to it.
If I need to roll back, I check out an older copy of the file.
1: Have kids, then it'll be natural for both of you to be up regularly, and nobody will mind the occasional night-time waking that you get paid for.
2: Your S.O. will learn to sleep through it, and you'll learn to react faster to silence the alarm.
3: Fix your systems and monitoring to wake you up only when it's more important. (eg., use a different alert threshold for non-daylight hours, use email-only alerts where you can, etc).
I look upon the inevitable Kindle conversion with a terrible dread. I'm typing it up in Google Docs, but because I use italics for emphasis, this means I have to either manually construct the book (and manually re-put in all my italics and formatting), or use a converter which will produce sucky output which will require a lot of manual cleanup...
Have you tried (say) Calibre's conversions? I've thrown random HTML files at it to create MOBI-format eBooks for my Kindle, and it's done a brilliant job, with no twiddling needed at all in most cases.
I'm guessing the main haters are sysadmins, who see threats to their importance and way of working.
Spoken like a true developer
Developers need to get used to the idea of Operations, as much as the Ops folk need to get in bed with the dev side of things.
Devs and Ops have traditionally led very different lives, and it's that schism that's really made DevOps-style movements so hard (and important).
As a random example - Ops people are typically on call, and get woken up (automatically by a monitoring system) because disk space on server 'x' filled up. Yet much of the time, it's the application's fault - and the sysadmin then spends far too much time trying to get developers to think about disk space growth, data retention, etc - rather than the developer being across those operational concerns from day one, which in a DevOps-ified world they should be.
It's about trying to get both groups to work towards a common goal - and too many people on _both_ sides of the fence don't understand why the other side wants what they do.
(I'm an ex-developer sysadmin, FWIW).
My phone uses a dual core processor and 256MB of RAM and still can't reliably open my contacts list.
We have gone backwards since those days.
Ah, you need to turn the GUI on your phone off and start using it in 80x24 text-mode. I did that with mine, lightning fast now!
Has any commercial site since 2001 or so actually ever returned a 404 response to a non-existent page, rather than an arbitrary ad-happy landing page or redirect to the homepage?
You can serve a 404 response that includes content, which would be The Right Thing To Do to ensure happy users and happy crawler-bots.
...and on a day I don't have mod-points, too
There is NO REASON for regular customers to have
/64
I want a
Pssht. You humans and your TV shows.
It's this one: http://memory-alpha.org/wiki/Daedalus_class
Why use your ISP for DNS? Chances are their servers suck
I'd really consider seeing if you can find a better ISP (if it's possible in your area).
IMVHO, It's not too much to ask of an ISP that they have reliable and uninfested DNS.
(Disclaimer: I am in the sysops team that maintains resolvers at an ISP in
Isn't that what the header packets are for? So each packet knows where it came from and where it's going?
Anycast breaks that though, because all servers in the anycast pool share the same address, so it confuses the server & clients when you add and remove servers from a pool.
But that already happens in numerous situations - governments run large NAT gateways / proxies, some 3G carriers use 10.0.0.0/8 and NAT/proxy, etc.
It's a perfectly valid issue *today*, not just in the future. Sure, it'll get worse, but at least there's now a solution in sight (ie., move to IPv6 to get better service).
More to the point, SMTP hosts will be pretty much forced to do something more productive than blocking via IP, which amounts to group punishment. (Something apparently only tolerated on the internet).
Not really. By the time you're talking about LSN/CGN, you're talking about customers that send mail via their ISP's mailserver, not directly. Business customers wanting to send mail direct to the Internet without worrying about NAT making "their" IP look worse, will undoubtedly be able to buy a non-NATted IP.
(Disclaimer: I work for an ISP but am not speaking for them).
E = MC ** 2 +- 3db
