This is a great free tool, just don't ask for something the developer doesn't agree with. He and the IRC community supporting it will tear you to shreds.
Always wire payments. My consulting clients are mostly based in Europe for their HQ's, so they don't believe in checks. They also are very timely, within 5-7 days of a NET30. Like clockwork.
We're receiving roughly 200 msgs/s in our environment. We have it set up in an active/active environment across two data centers. It's been rock solid for us. It takes a little bit of time to get certain applications to send messages properly, but once you do, it's pure gold.
We are using NXLog on our Windows servers to send event log messages in GELF format. This allows us to truly delve in and search event logs so much easier than what we normally would be able to in Windows.
We use the heck out of GrayLog2. We have a dual datacenter setup with multiple elastic search instances. A coworker of mine did a fantastic job writing up our setup:
I believe it does. I will spin up an OS X VM and test it later tonight, since my MBPr is fully up to date. I will of course update the site with what I find.
I've actually never run into Secrets! Thanks for bringing it to my attention. I will certainly be adding more to it over time. Do you have any specific suggestions?
Between 20-30% would be my best guess. I'm including business emergencies as well, regarding client support. These emergencies get me out of the groove, which also adds up wasted time, while I try to get back into what I was working on.
Completely agree with you on this one. Only build the site if you're willing to maintain it long term as well, not just as a means to an end (get a job). Get involved in the community and watch your career grow.
I think something that is very important to remember from the beginning, is to create a personal "Brand". Use the same profile picture everywhere, including LinkedIn. For your website, target content for people in your field, not recruiters or HR. The companies that you want to work for are ones that understand that contributing to the community is important.
Take content you've written while in school (especially if you're in IT) and put it on GitHub (assuming you can legally). Write about it. Worry less about making it a resume and more about what you're capable of.
That's my two cents... In the end, I found my job via a Twitter follower who happened to be the CIO of a telehealth company. He was most excited that I write content and contribute to the community via Github, Blogs, and Twitter.
Also, make sure to add a personal touch. I've struggled with that on my blog, but am focusing on it more now.