Jody Lemoine 🇨🇦
ghostinthenet.bsky.social
Jody Lemoine 🇨🇦
@ghostinthenet.bsky.social
770 followers 700 following 210 posts
Network anarchitect and matrix greasemonkey, #CCIE 41436, Mikrotik Certified Instructor, #MTCRE, #MTCINE, #MTCIPv6E, #MTCSE, #MTCSWE, #TechFieldDay Delegate (Follow me in the Fediverse at @[email protected]. I’m here, but it’s a side thing.)
Posts Media Videos Starter Packs
Proof of concept lab complete (RFC 1925 Truth 1 has been satisfied) and my MikroTik Professionals’ Conference presentation request has been submitted. Now to start working on the actual presentation in case they actually say yes. #MTPC #MikroTik #NetEng
Them: What social media platforms are you on so I can follow you?
Me: Mostly Rebo and Zooty
Them: ?
#B5
The “Simplicity where possible. Complexity where necessary.” mantra applies long before we get to the design stage. 2/2 #NetEng #Labbing #RabbitHole #KISS
The problem with labbing cool networking ideas? Rabbit holes. Every step along the way, there’s another “Oh! Wouldn’t it be better if I integrated •this• idea?” Taking the red pill leads to a fun day of network geekery, but doesn’t get me any closer to the original goal. 1/2
I’m surprised I don’t misplace my military driver’s license (DND 404) constantly. #GeekJoke
Discovering that something is a DNS problem rather than a network problem feels good… until we learn to accept the fact that DNS is a fundamental network service. If it’s DNS, it’s the network. The real joy comes from it not being •my• network’s DNS that’s at fault. #NetEng #DNS
After two weeks of banging my head against this multicast routing lab, I finally found the problem. The default TTL for •all• multicast packets on Linux is 1. Of course, I overlooked the simple stuff in my troubleshooting, as one does. #NetEng #Multicast #Troubleshooting #LessonLearned #ThereAreDays
I haven’t played extensively with multicast routing for a little over a decade, but here I am grinding the rust off of the metal. Gotta stay fresh if I want to engage in silly proof-of-concept labs. #NetEng #Milticast #Labbing #WorthIt
“Something went wrong. Please try again later.” as an error message is about as helpful as “It’s broken.” is. Not only is the first part so vague that it’s useless to anyone who might be able to help, but we •know• that trying again later is unlikely to work either. #Grr
Apparently it’s one of •those• days again. #CorgiLife
An IPv6 address is composed of 8 16-bit quybbles (quad-nybbles) and this shall be the standard term used in all of my documentation going forward. #NetEng #Quybble #BecauseItMakesMeSmile #IHaveSpoken
“The standard that you walk past is the standard that you accept.” - LGen David Morrison. Simple phrase, but infinitely powerful. #Leadership #ThingsToLearn
Today I learned that my approach to leadership is actually an established method. Need to read some of Robert K. Greenleaf’s stuff sooner than later. #Leadership
Favourite use of ANI so far? Auto-generated transcripts for videos and podcasts. #NoTime #LetMeSkimThat #MyPace #AI
Some days I wonder if the companies that are so keen on using ANI to streamline their processes and eliminate jobs are considering that their customers are simultaneously using ANI to kill the need for their products and services. #AI
To those who keep asking, no. I’m not worried about ANI taking my job. Well, no more so than I am about my screwdrivers taking my job. The practitioner is always more than the sum of their tools. #AI
I would place businesses above 1,000 employees in the ultra-large category. That’s 500 above large, which is already the top 0.3% of businesses. Networking practitioners would be anyone specialized in networking. I agree that there’s a critical mass needed for those, but how much?
If (approximately) one in four people are employed by ultra-large businesses, do networking practitioners have a similar distribution? My experience in discussions with my peers indicates that we’re skewed heavily toward that market, perhaps four in five or even nine in ten. #NetEng
Reposted by Jody Lemoine 🇨🇦
why does enterprise software UI absolutely suck?
you get engineers with a sense of superiority because they “got gud“

bro, you have stockholm syndrome from an aruba controller, and you’re telling me to git gud? get outta here.
The products of #AI aren’t subject to copyright. Does this mean organizations who are vibe coding have no intellectual rights to the results? I’m thinking the answer is yes. If I’m right, I now wonder if these organizations have considered this… or have they been too caught up in the hype?
If we outsource our customer service, it can be fairly said that we’re not serving our customers at all. Now let that sink in.
It absolutely does. Then again, the bulk of HTTPS/QUIC requests go to servers that host multiple sites, so IP literals are becoming less and less useful.