For my primary small business account, I went with KolabNow which has pretty good spam filtering. The downside is that you're going to spend $65-$95 per year on the service depending on your mailbox size. They need to cut their prices a bit or offer more storage for what they charge. They have more of an incentive to stop spam as email is their primary business.

Running your own mail server is not worth it unless you absolutely need control over storage of the mailboxes for legal reasons. I've admin'd an Postfix/Dovecot/SA for the last decade. Setup takes 3-4 days, you have to tune it monthly for the first year, and then keep an eye on it. I estimated that we blocked about 90-95% of all inbound spam at the firewall, without too many false positives. The client-side spam filters took care of the rest.

That requires DNSSEC and DANE to be effective. There's momentum for both, but neither will hit mainstream until Google's Chrome forces it.

Ultimately, I expect a mix of pinned-certificates, DNSSEC/DANE, and cloud-based reputation for certificates (is everyone else seeing the same certificate?).

Key management is hard -- really hard. It's the weak link of modern encryption.

Having played both sides of the fence, Java vs C# for server-side stuff is about equal. Especially if you use a good framework, inversion of control, and unit/integration testing. At this point, you can succeed with either.

The main downside right now with C# is your limitation to running on top of Microsoft Windows/Azure servers stack. Support for running against non-Microsoft technologies (such as PostgreSQL, or under a different O/S) is still a rough edge.

#3 is pure shill. MSDN documentation is crap for 90% of what you search for compared to how it was back in 2000.

The big problem with MSDN is that they change URL schemes every 2-3 years, breaking every reference URL that you might have saved. Then there's the almost, but not quite, completely useless form of the documentation which tells you everything you already know without making the water less murky.

I prefer one GPG file per site. Downside is that it exposes the site name, but also means I only decrypt only a single site password at a time.

Bonus points for putting the files into a version control system (git/svn/hg) so that you can cleanly sync them between PCs.

And making backup copies is as easy as stuffing the ASCII armored block into an email. Or printing it out for OCR'ing later...

Don't be inside the bubble when it burst.

Very much this. Don't work for a shiny company that is not profitable and is valued based on hype rather then cold hard cash in the bank.

IT work at more traditional (and well-run) companies may not be sexy and flashy, but payroll is always on time.

Not that long. Depending on what the solar cycle does, Earth's atmosphere expands out far enough to drag this stuff down within weeks/months. Not years/decades.

Even at 250 miles above sea level (which is around the orbital altitude of the ISS), you have to regularly boost your orbit or get dragged down for reentry.

Customers who are running old, outdated, and insecure systems like WinXP are generally too cash poor to be good customers. They are going to nickel and dime you for any project that you do for them because they are either too cheap to invest in newer technology or too poor to do so.

Latest statistics indicate that Internet Explorer has less then 15-20% of market share, with versions older then IE 10 being just 2.5% of the market. Looks like IE 6 is under 1% now.

A year ago, you'd be a fool to cutoff support for IE on WinXP with 10-12% market share. Now? Not so much and it's not worth development time to support a 1% market share for IE 6.

HTC One (m8) is another good Android phone. HTC's UI is pretty close to stock and very light on its feet compared to some others. It even got upgraded to Lollipop a while ago with no issues.

Those four towers are the lightning protection system.

For more details, search for "rolling sphere" lighting protection system design. The idea is that if you roll a sphere of size X (usually 150ft or 45.7m) across the points of the masts, the area below the ball will be ~95% protected against a strike of power level Y. That is, any leader passing through the sphere will be more attracted to the mast, then to something below that point.

Yes there is margin.

But not launching on the exact instant when the ISS inclination is properly aligned with the launch site is expensive. The shuttle launches had to sacrifice 1100kg of payload in order to have a 10 minute wide launch window.

For a robotic launch where you can easily safe the vehicle after a scrub and don't have to unload passengers from the capsule, delaying 23h37m is not a huge deal. So you go with a much shorter launch window and gain a lot more payload to orbit. And if things don't go as planned, you scrub for a day and try again.

+/- 5 minutes was the shuttle's window and it cost 1100kg of payload to have a window that large (reference link).

The dog-leg cost of slipping into the proper inclination orbit with a launch that is mistimed can huge. On the order of hundreds of dV required to fix the issue.

So for robotic launches, where you don't have crew sitting in a capsule / vessel, and scrubs are relatively cheap as a result, it's better to go for a very small launch window (~1 second) to maximize payload.

Rule of law mattered more then unexploited resources.

When you look at the list of essentially failed countries that should have great wealth, all of them have very bad corruption issues.

Just because you can get away with something doesn't make it moral and/or legal and/or a good business decision.

Everything after Win7 bad . . .

Win10 looks to be a good and solid upgrade to Win7.