139 karma · joined October 8, 2007
As a PC user and occasional twitch-gamer, I personally stick with plain 104-key USB keyboards from Dell or Microsoft (quiet you), since they're fairly cheap to replace at local thrift stores. If my keyboard happens to die by misadventure, I'd rather not drop another $60+ just so I can use my machine comfortably.
When it comes to notebooks, the answer for me is and has always been ThinkPad, though the MacBook Pro/PowerBook keyboards are pretty solid as well. Sadly, nobody seems to be donating any MacBooks to my cause... :{
- Make sure your policies/procedures are clearly written and do not have any gaps or gray areas. Keep in mind that you will probably have to train a new hire from the ground up at some point, and the less hand-holding needed, the better. This goes for everything from operations to sales to billing.
- Automate EVERYTHING. Linode is a great example of how to do this correctly (although automating VPSes is a touch easier than bare-metal servers). Softlayer's web panel is pretty good, as well. The more your clients can do without opening a support ticket, the better.
- Monitoring is important. You should be notified of problems instantly so that they can be fixed very quickly, ideally before any clients notice a problem.
- Proprietary software/hardware for core offerings is generally a bad idea, unless you're hosting MS Exchange (and Openchange should eliminate that issue eventually). Keep in mind that you may have to migrate every bit of data someday in the future, and implement your stuff accordingly. This also ties into automation: proprietary stuff tends to be harder to write code for, harder to troubleshoot, and more expensive to maintain in the long run.
- Do not skimp on facilities, hardware, or network architecture. Always have hot spares to replace your live gear in case something gets fried (switches/routers, power supplies, hard drives, RAM, server chassis). This requires some investment, but telling clients "we're waiting for a new powersupply shipment from Dell, you're down for X hours" will make them spend X hours researching their next hosting company.
- If your organization is responsible for deploying hardware in datacenters, be absolutely sure that you are not overloading your power drops. If you can, get intelligent power strips that allow you to monitor load on each circuit. Know the maximum load for your hardware, in case everyone on a circuit gets slashdotted or similar.
- Do not roll out new services/datacenters/hardware without stress testing them first. Launching new stuff that doesn't quite work 100% (or will work with minor adjustments) will cause headaches for staff and clients alike.
- DO NOT LIE TO ANYONE, ABOUT ANYTHING, EVER. Transparency may be your policy, but integrity is pretty high on everyone's list, too. Admit mistakes, especially the embarrassing ones. Don't make promises you can't keep without breaking a sweat.
- When mistakes are made, take systematic steps to eliminate their causes, permanently. Examine procedural failure before human failure; the former generally leads to the latter.
That's just a few things I've gleaned from the last 6 years fixing broken servers... I may have left a few things out, but that should be a good start. Feel free to drop me a line sometime (email is in my profile) if you want to talk more about this kind of thing :)
i.e., "Am I doing something worthwhile?" -- which could mean different things depending on the context, the goals or principles of the person, or what have you. I guess it depends on how you define "value" :)
You cannot change your SSN.
And some BBB-style fraud reports, fairly recent (July 08):
http://voip.yuku.com/reply/421/t/Re-premiervoice-net-aka-pvo...
I don't mean to cast aspersions or commit libel, but it looks like Mr. Faulkner might have a bit of a spotty history, and according to these reports, has used multiple names in the past. This might get interesting :)
I've worked at various hosting companies around Dallas for 5 years, and have worked or observed quite a few abuse cases involving the federal government. This sort of heavy-handed action (killing an entire company's operations for a single client) has NEVER happened in my experience, and definitely not for something as innocuous as copyright infringement. That's what the DMCA is for. The feds don't get involved unless it's some seriously nasty stuff going on, like child porn, suspected terrorist communication, fraud, malware distribution, etc.
In the event that the government gets involved, they will have a field agent demand access to individual systems under a subpoena, but only to the systems actually involved (maybe some switches/routers as well). Unless Core IP has been proven to be complicit in some kind of ultra-illegal activity, e.g. the CTO is the kingpin of some hardcore piracy network, I have a hard time believing that this has anything to do with a leaked movie. I'd think that the Secret Service (US Treasury) would be involved in such a case, rather than the FBI.
This really is completely ridiculous, though. Makes you want to go read the common carrier laws cover-to-cover :)
edit: I guess this piracy thing has been confirmed as a rumor for some time... but hopefully this sheds some light about how the process works :)
ouch
I personally won't allow any money to ride on a machine to which I do not have root. :)