My 9-5 gig revolves primarily around Tibco LogLogic (I’ll write it as Log Logic going forward, as I write in English, not C++), which is a centralized logging product. The appliances collect logs from a variety of dissimilar systems and present you with a unified, web-based interface to search them. When something goes wrong, having all of the logs in one place is invaluable for figuring it out.
That value comes at a price. I don’t know exactly what these appliances cost, but generally speaking, $100,000 is a good starting point for an estimate. So what if I told you that you could store 45% more data on these expensive appliances, and increase their performance very modestly (2-5 percent) in the process? Read on.
Continue reading How to increase the capacity of a Log Logic appliance by 45%
Some revolutionary advice surfaced this past week–stop patching everything. And while I understand the argument that people need to stop letting the difficulty of patching everything paralyze them and cause them to do nothing–as I’ve seen some organizations do–and I agree that some patches are more critical than others, as someone who once had to prioritize patches, I can assure you that prioritizing the patches was more work than deploying them and recovering from the fallout was. We eventually found it was much less work just to install all the missing patches every month.
And guess what? Nothing bad happened from doing that.
Continue reading I don’t think I agree with the argument against patching everything
I saw this phrase in a job description last week: Troubleshooting at all layers of the OSI model. That sounds a bit intimidating, right?
Maybe at first. But let’s not overcomplicate it. Once you get past the terminology, it’s a logical way to locate and fix problems. Chances are you already do most of this whether you realize it or not. I was already troubleshooting at at least four of the seven layers when I was working as a part-time desktop support technician in college in 1995.
Continue reading Troubleshooting at all layers of the OSI model
Thanks to Tony’s Kansas City for the link this morning. Tony noted that “Security dude reminds us that Google Fiber could kill the software industry.”
That’s an interesting spin. I do think it will affect the software industry–but so long as Kansas City stays at the forefront and the rest of the country is content with being a technological backwater, the effect will be minimal. But “kill” is an awfully strong word, even if every major city in the country were to get affordable Gigabit Internet in the very near future.
I say that because of what I saw in college. Continue reading Welcome, Tony’s Kansas City readers
Yesterday an interesting question popped up on Slashdot, asking for an alternative to a computer science degree for an aspiring web developer. He complained that what he’s learning in class doesn’t relate to what he wants to do in the field.
Continue reading How to maximize a Computer Science degree
Consulting firm Deloitte is warning that 8-character passwords will be obsolete this year. Sound familiar? Of course, the Slashdot crowd blamed it as security “experts” (their words) creating hype to make money.
Well, I’m a certified security professional who doesn’t have a dog in this fight, except that I don’t want your accounts getting stolen. So here’s the problem with many of the solutions the Slashdot crowd posed.
Continue reading The problem with dictionary passwords
I saw a story on Slashdot this weekend writing Silicon Valley’s obituary at the hands of the Facebook IPO. The logic is that since social networking is an easier path to riches than traditional science, people will choose social networking.
In the short term, he may be right. But in the long term? The Facebook IPO looks more like Dotcom 2.0 to me. Continue reading Facebook’s IPO doesn’t have to be the end of Silicon Valley