Skip to main content

The thing I didn't see coming

I keep forgetting I have this blog. But today felt like the right time to write something - something a bit more personal than usual.

I want to talk about burnout.

A while back I was deep in a very large infrastructure project. What started as a technical role slowly turned into something much broader - I found myself handling bits of legal, commercial negotiations, RFP work, supplier discussions. A lot of moving parts. And somewhere along the way, I realised I was doing most of it on my own.

The late nights started adding up. Long calls with suppliers making sure the bill of materials was right, checking the solution actually held together end to end, always that nagging feeling that something had been missed somewhere. It just kept going.

And then something shifted in me.

It's hard to describe. I'd never experienced anything like it before - burnout, anxiety, call it what you want - but it hit me in a way I really wasn't prepared for. I've always been someone who just gets on with things, so even recognising what was happening took time.

I'm still working through it, honestly. But the one thing I keep coming back to is how much my family and friends have helped. I didn't realise how much I'd need that, or how much it would matter.

I'm not going to go into all the details here. I just needed to write this down. And maybe, if someone else has been through something similar and didn't quite have the words for it either — this is me saying, yeah, me too.

Popular posts from this blog

Juniper IS-IS summary

##################################################################################################### ## ISIS ##################################################################################################### # Be sure to set family iso on the interface to be placed into ISIS set interfaces <interface> family iso # By default Junos places interfaces as L1/L2 # Default route leaking:         L1 to L2 - all internal routes         L2 to L1 - 0/0 route # L1/L2 will send the attached-bit down to L1 and it will act as a NSSA-like area.  When the L1 interface # receives the attached-bit it will inject a 0/0 route into the RIB point to the L1/L2 interface. # To disable the attached bit use: set protocols isis ignore-attached-bit # Be careful with the "interface all" command, as it may have some unexpected consequences such as trying # to establish a neighbor on your fxp0 management...

SecurityIE Forum

http://www.securityie.com/ Securityie is an open forum for CCIEs and CCIE candidates to discuss issues and technologies related to the CCIE Security certification. Signing up is free. If you sign up for one forum you are automatically setup for our other forums Routerie and Voiceie. We have over 20000 members active on these boards many of which already have their CCIE.

IOS on Unix (IOU)

source http://evilrouters.net/2011/01/18/cisco-iou-faq/ What is IOU? From the Cisco Engineering Education web site (a long time ago): IOS on Unix (IOU) is a fully working version of IOS that runs as a user mode UNIX (Solaris) process. IOU is built as a native Solaris image and run just like any other program. IOU supports all platform independent protocols and features. What operating systems does IOU run on? It is my understanding that, initially, IOU was Solaris (SPARC) only. Nowadays, however, there are also builds for OS X and Linux. Similar to dynamips, IOU allows you to build out a network topology on a computer, without the need for physical routers. This is useful for validating designs, proof-of-concept testing, and certification self-study. Is my system compatible with IOU? You will need to be running the operating system that your IOU image were built for, obviously. Other than that, there are no special requirements to run IOU. It is not very CPU- or memory-intensive, unlik...