It’s been a while since I posted anything. I read Atomic Habits a few months back and tried to get myself into the habit of blogging regularly. It didn’t really work. In fact, I acquired exactly zero new habits after reading that book. My blogging time is directly affected by my work schedule. I tend to get busy, and then I don’t blog.
Anyways, I was digging through old posts and I realized I’ve been at this blog for quite a long time. My first post was back in 2013, back when I worked for Juniper Networks. I listed my goals for starting a blog, and it’s interesting to consider whether I have achieved them.
My hope is to provide several types of articles here.
Well, that’s true enough. This blog is not a one-trick pony. If anything, my lack of focus probably diminishes my readership. Will it be Jeff going off on the corporate world or Jeff reminiscing about technology that was current 20 years ago?
I will be breaking down difficult technical subjects for my readers.
This is what I love to do, mainly why I started this blog, and what I do very little of. In fact, at the time I was very frustrated with certain Junos concepts that seemed poorly documented. One was the inet.3 routing table, and the other was the concept of RIB Groups. Those two articles are historically the most read on this blog, because they confused the heck out of everyone else. I also wrote an article breaking down the difference between ISIS levels and adjacencies and OSPF areas. When I was studying for my JNCIE-SP, I got totally confused by hub-and-spoke VPNs, a somewhat useless concept that I broke down in two articles (here and here). When I got to Cisco, I was briefly assigned to DCNM, at that time the name for Cisco’s non-ACI data center “controller”, and I did a two-part series on DCNM’s fabric management, again because I found it utterly confusing and wanted to share what I learned (here and here).
Unfortunately, I haven’t had much opportunity to do additional articles of this type. When I found myself leading a team of 50 engineers, I didn’t get a lot of hands-on time in the lab. Now I do, but most of what I’m working on is secret. I had set up an SRv6 lab and was really excited to do a breakdown, but that darn time thing… So, I give myself a C- here. The first articles were good, but there just aren’t many anymore.
I will also provide frank commentary on the industry…
A+ here. Also known as: “Jeff gets pissed off and says too much.” These are, in a way, the easiest articles to write. No lab setup required. I’ve spent a lot of virtual ink on corporate culture, because (a) it disgusts me in various ways, (b) most of us live in it, and (c) the culture of large tech vendors directly impacts network engineers, the products they are sold, support for these products, etc.
Of course, it does put me in a weird position working at Cisco. Frankly, I cannot be as honest as I would like to be because I have a mortgage to pay. I try to generalize my comments to the industry at large, but my take is obviously colored by 11 years at this company. Still, I think I’ve been refreshingly honest here, and I don’t regret it.
…and on training and certification.
I did my “10 years a CCIE” series, so check. I’ve written a few one-off articles on the subject. I strongly believe training and certification programs can be a powerful way for technical folks to learn a given subject using a structured curriculum with a goal of gaining a credential at the end. I’ve also seen the badly written exam questions, useless paper certs, and people certified up the yin-yang who can’t configure a static route. It’s a part of our industry, so it’s worth discussing.
I will also augment this with stories from my years as a network engineer that hopefully will keep things entertaining.
This turned into my Netstalgia and TAC Tales series, some of my favorites to write. The problem with these series is I have a limited reserved to draw on, and I’m running out. I’m debating if stuff I did at Cisco 10 years ago now qualifies for Netstalgia, but it doesn’t seem retro enough.
I hope my language and humanities experience will lend some interesting color to this site
I’ve dropped a few references to Greek and Latin, Gregorian chant, and Romanian absurdist playwrights, so I guess I accomplished this goal.
Overall, it’s been enjoyable for me to write the blog, but I don’t know that it has had much impact beyond my own personal satisfaction. I don’t advertise or promote it and I rarely put a post on LinkedIn.
The last time I did, it was my post about leadership. When I posted it on LinkedIn, I assumed only a few people would read it. “Management vs. Leadership” posts are a dime a dozen on LinkedIn. It seems like there are about five a day. Why would anyone pay attention to another? Maybe it was the photo that went with it, of me pensively looking out over the ocean, contemplating my future. That picture was actually taken by my nephews when I took them on a trip to Monterey, California, years before I wrote the article. I found a nice nook and asked them to take a picture to remember it. It just seemed to go well with the theme. I had never intended the article to be self-defense or a personal hagiography. About a year after I wrote it, an executive asked me if it was a reproach of my boss at the time (an SVP). I explicitly said it was not, but that it was a composite of what I had seen over the years. Nonetheless, many people took it that way. The SVP himself read it. It made me hesitant to post on LinkedIn anymore.
Naturally, then, the question arises as to whether I should continue devoting time to this blog anymore at all. Perhaps it’s run its course? I don’t have working stats, so I don’t know how many people read it. I rarely get comments. Long form articles seem to be less popular than 10 second video shorts. I don’t have the time to devote to it. Perhaps I should stop paying the hosting fees and retire it.
I don’t really have an answer to that yet. We’ll see where it goes.