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

5 Labs in 8 Days

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

I’m going for it.  5 practice labs in 8 days.  I’m taking 3 days off of work next week, but I’m going to still get up at my normal time.  At 4:35am my alarm wakes me from blissful slumber.  I shall get cleaned up, then head down to my private little corner of the house to start hacking.  I wired my touchy terminal server up to a manageable power strip so that I can remotely reboot the silly thing if it locks up.  I printed all the scenarios I’ll need.  I’m as ready as I can be.

Here’s the plan:

  • 11/17 Saturday – NMC DOiT scenario 14
  • 11/19 Monday – NMC DOiT scenario 15
  • 11/20 Tuesday – NMC DOiT scenario 16
  • 11/21 Wednesday – NMC DOiT scenario 17
  • 11/24 Saturday – NMC DOiT scenario 18

Why am I doing this, you ask?  I’d do “6 days on/1 day off” until I was ready to make my first lab attempt if I could work that out.  You have no idea how bad I want to be ready for my first attempt.  Or maybe you do.  Wanting it badly doesn’t give me the ability to hack IOS all day, though.  My employer expects me to show up and actually be lucid when I’m there.  And my family wants my attention rather a lot.  Ergo, I’ve been restricted to one day a week of practice lab time lately.  But I had some vacation time I had to take (use it or lose it at my company).  So, I’m going to take that time to crank out these practice labs.  If I haul my keister out of bed, I should be able to be done around 1pm every day, say hello to my fellow humans, then blog for a while.