The mendicant was perplexed. This wasn’t unusual and, truth be told, the mendicant often didn’t understand everything and lived in a constant state of perplexedness. But this time, he was sure of the facts and knew that something was not right. He sighed and went to find the the Master. The Master was communing […]
The post Network Zen: You Cant Change The Fact But You Might Change The Perception appeared first on EtherealMind.
In this post, I will give you a business requirements and information about the business of a fictitious company,together we will try to find an optimal solution for the given questions. There will be many valid solution as you will see from the comments, we will have to make tradeoffs between each design goals while… Read More »
The post VPN Design discussion appeared first on Network Design and Architecture.
Saisei's latest FlowCommand offering aims for the FCC's favorite buzzword.
I’m fundamentally lazy. That’s why automation appeals: less work for me. Get the machine to do it instead. But automating everything isn’t always the right answer. Sometimes you need to ask yourself: Does this task need to be done at all? Or can I get someone else to do it for me?
Automating tasks carries some overhead. If you’re really unlucky, you’ll end up spending more time on the automation than doing it manually:
So if you can eliminate tasks, you’re in a much better position. Here’s a few contrived examples, based around a fictitious email provider:
15-20 years ago we had limited bandwidth, and limited storage. It seemed reasonable to limit the maximum email message size. Otherwise people would send monstrous 2MB attachments. Of course, there were always ’special’ cases that needed to be able to send enormous 5MB AVI files. So we had special groups of users defined that could send large emails.
Users could put in a request to the Help Desk to get access to send large emails. That would go via some manager, who would of course approve it. Someone would then need to manually update that Continue reading