Pass your Cisco CCNA with David
#CCNP
Three years ago, I was at a crossroads.
I already had my CCIE Routing & Switching for quite some time, and I was asking myself the big question: whatโs next?
DevNet? CCIE Security? I started exploring bothโฆ but something kept pulling me towards one thing: design. The kind of work where you donโt just make networks run, you make them make sense.
So I went all-in.
I poured every spare hour into the CCDE path, starting with the written exam (400-007). In June 2024 I passed the CCDE Written in Las Vegas and thought, right, now itโs โjustโ the practical.
I knew the practical would be tough.
I did not expect it to take a year and a half of my life.
Early mornings. Most weekends. A few nights every week with the study group.
And, if Iโm being brutally honest, a lot of it was time borrowed from my family. Time they graciously sacrificed with me, even when it wasnโt fun, even when it dragged on.
But todayโฆ I walked into the Cisco office in London knowing it was the day.
Almost 7 hours exam (yes, I finished a bit early). Then, I waited. Waited. And waited. In the end, the email arrived.
โ๐ฌ๐ผ๐๐ฟ ๐๐๐๐ ๐๐๐ฎ๐๐๐ ๐ถ๐ ๐๐ฒ๐ฟ๐๐ถ๐ณ๐ถ๐ฒ๐ฑ (๐๐๐๐ ๐ฎ๐ฌ๐ฎ๐ฑ๐ฌ๐ฌ๐ฒ๐ฐ)โ
Iโm proud. Iโm relieved. And Iโm genuinely grateful.
To my study group: you kept me accountable when motivation wasnโt enough.
To my family: you carried a chunk of this journey with me.
To everyone whoโs grinding through something big right now: keep going, but donโt forget why you started.
Nowโฆ Iโm going to take a breath. Then Iโll decide whatโs next. ๐
#CCDE #CCIE #CCNP #CCNA #NetworkDesign #Cisco #CareerJourney #Learning #NeverStopLearning
Cisco SD-Accessใซใคใใฆใพใจใใฆใฟใ
https://qiita.com/yamaharu1128/items/d1ba4dd11b8fd36f892a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Any network engineer lives on the edge of configuration, analysis and troubleshooting. Even a network architect. ๐จโ๐ป
Think about how often we:
โข Correlate logs, SNMP traps, telemetry and packet captures to find the real root cause ๐
โข Spend time with wireless issues like roaming, sticky clients, RF interference and capacity ๐ตโ๐ซ
โข Analyse path changes, flaps and convergence in complex routing environments ๐
โข Validate policy and segmentation (ACLs, security rules, VRFs, SDA/ACI policies) against what the business thinks is happening ๐
โข Spot patterns in performance issues that only appear at scale or at weird times of day โฐ
Used well, AI tools can genuinely improve the quality of our work while cutting execution time dramatically. โก
Better designs, fewer mistakes, faster troubleshooting, clearer docs.
All good on paper.
What I find interesting, though, is how this plays out in real life. ๐ค
Instead of using that time-saving to improve our work-life balance, what often happens is that once we deliver faster, we are simply given more work.
More projects, more tickets, more โquick asksโ, more meetings squeezed into the same week, because โyou are efficient with those tools nowโ. ๐ฅ
The result is a strange paradox.
We are more productive than ever, but not necessarily less tired.
AI boosts output, yet the space it creates in our day is quickly filled with additional tasks, not recovery, not learning and not thinking time. ๐งโโ๏ธ๐๐ง
I am genuinely curious:
๐ Have you noticed the same behaviour in your team or organisation?
๐ Are you using AI to work better, or simply to work more?
I would love to hear how others are experiencing this shift. ๐ฌ
#cisco #ccde #ccie #ccnp #ccna #netengs #AI #worklifebalance
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst