For a long time, I believed that being a good network engineer meant knowing the right answer.<\/p>\n\n\n\n
Knowing the command. And in many ways, I did know those things.<\/p>\n\n\n\n But knowledge alone doesn\u2019t always translate into trust \u2014 especially in production environments where the cost of being wrong is immediate and visible.<\/p>\n\n\n\n I learned that the hard way.<\/p>\n\n\n\n The hardest part wasn\u2019t making a mistake.<\/p>\n\n\n\n It was realizing that the mistake didn\u2019t come from rushing or carelessness. I recognized the situation. From my perspective, I was being careful. That gap \u2014 between intent and impact \u2014 is where trust erodes.<\/p>\n\n\n\n What I\u2019ve started to understand is that confidence, by itself, is neutral.<\/p>\n\n\n\n Unstructured confidence can be dangerous. In networking, one line of configuration can affect dozens of systems. The CLI doesn\u2019t care how sure you feel \u2014 it only cares what you typed.<\/p>\n\n\n\n I didn\u2019t need more confidence. The most dangerous moment in production isn\u2019t panic.<\/p>\n\n\n\n It\u2019s comfort.<\/p>\n\n\n\n It\u2019s the moment you think:<\/p>\n\n\n\n \u201cI\u2019ve seen this before.\u201d<\/p>\n<\/blockquote>\n\n\n\n That thought shortcuts curiosity. I\u2019ve learned to treat that moment as a warning sign \u2014 not a green light.<\/p>\n\n\n\n One of the hardest lessons for me has been this:<\/p>\n\n\n\n Not every correct fix should be applied immediately.<\/p>\n\n\n\n Sometimes the right move is to:<\/p>\n\n\n\n That feels wrong when you care about doing good work. Stability matters more than cleanliness.<\/p>\n\n\n\n I used to think becoming a better engineer meant:<\/p>\n\n\n\n Now I think it means:<\/p>\n\n\n\n Being \u201cboring\u201d in production isn\u2019t a flaw. I still care deeply about doing things right. What\u2019s changing is how<\/strong> I act on that care.<\/p>\n\n\n\n I\u2019m learning that growth isn\u2019t always about adding skill \u2014 sometimes it\u2019s about adding structure.<\/p>\n\n\n\n And that kind of growth is quieter, slower, and easier to miss \u2014 but far more durable.<\/p>\n\n\n\n A reflection on confidence, mistakes, and learning to slow down For a long time, I believed that being a good network engineer meant knowing the right answer. Knowing the command.Knowing the fix.Knowing what should be done. And in many ways, I did know those things. But knowledge alone doesn\u2019t always translate into trust \u2014 especially in production […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-171","post","type-post","status-publish","format-standard","hentry","category-engineering-growth"],"_links":{"self":[{"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/posts\/171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zachthomas.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=171"}],"version-history":[{"count":5,"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/posts\/171\/revisions"}],"predecessor-version":[{"id":329,"href":"https:\/\/zachthomas.net\/index.php?rest_route=\/wp\/v2\/posts\/171\/revisions\/329"}],"wp:attachment":[{"href":"https:\/\/zachthomas.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zachthomas.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zachthomas.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Knowing the fix.
Knowing what should<\/em> be done.<\/p>\n\n\n\n
\n\n\n\nThe uncomfortable gap between knowledge and outcome<\/h2>\n\n\n\n
It came from confidence<\/strong>.<\/p>\n\n\n\n
I remembered something similar.
I acted from memory instead of verification.<\/p>\n\n\n\n
From the outside, it looked like recklessness.<\/p>\n\n\n\n
\n\n\n\nConfidence is not the same as readiness<\/h2>\n\n\n\n
Structured confidence is safe.<\/p>\n\n\n\n
I needed more pause<\/strong>.<\/p>\n\n\n\n
\n\n\n\nThe most dangerous moment<\/h2>\n\n\n\n
\n
It replaces checking with remembering.<\/p>\n\n\n\n
\n\n\n\nLearning to leave things alone<\/h2>\n\n\n\n
\n
But restraint is part of professionalism.<\/p>\n\n\n\n
\n\n\n\nRedefining what \u201cbetter\u201d means<\/h2>\n\n\n\n
\n
\n
It\u2019s a goal.<\/p>\n\n\n\n
\n\n\n\nClosing thought<\/h2>\n\n\n\n
That hasn\u2019t changed.<\/p>\n\n\n\n
\n","protected":false},"excerpt":{"rendered":"