You’ve probably seen “tenets” before.
They’re written on posters, buried in wikis, or flashed briefly at the start of some all-hands meeting. Most engineers glance at them once, think “corporate fluff,” and go back to their terminals.
I get it. A lot of so-called tenets are fluff.
But when they’re done and followed properly, tenets are one of the most powerful tools you can have as an engineer, for your day-to-day decisions, for your team’s culture, and for your career growth.
Used well, tenets are how you move from “I configure things” to “I define how we work around here.”
Let’s talk about what that looks like, especially in the context of modern network engineering and NetDevOps.