From the blog.

Managing Digital Racket
The more I tune out, the less I miss it. But that has presented me with some complex choices for a nuanced approach to curb
Complexity – My Friend, My Enemy
Over my years of network engineering, I've learned that the fewer features you can implement while still achieving a business goal, the better. Why? Fewer

NMC DOiT Vol.2 Scenario 14 – Quick Overview

183 Words. Plan about 1 minute(s) to read this.

I plowed through scenario 14 today.  This was a tough lab, lots of little tasks that killed time trying to track down.  It took  every bit of 8 hours.  This lab was the MOST frustrating of all the NMC labs so far because of the ambiguity of the wording in several of the tasks.  I found on the NMC support forum that others had similar problems.  I discovered while reading that if there’s a task in an NMC scenario, and you think leaving things as default will meet the requirements, then you’re probably wrong.  If there’s a task there, that means NMC wants you to do something specific.  Even if the default behavior seems to meet the task requirement, you’re most likely missing something.

More tomorrow.  I’d like to blog more now, but I’m taking the family out tonight.  I have to go make myself look human before we take off.  8 straight hours of rack time, and I don’t look human, I can promise you that.  Well, maybe I look human…but I don’t feel it.  Man, this lab was a kick in the head.