{"id":60,"date":"2025-10-18T22:08:15","date_gmt":"2025-10-18T22:08:15","guid":{"rendered":"https:\/\/blog.darkbytes.dev\/?p=60"},"modified":"2025-10-18T22:11:37","modified_gmt":"2025-10-18T22:11:37","slug":"between-water-and-code-what-canyoning-taught-me-about-leading-engineering-teams","status":"publish","type":"post","link":"https:\/\/blog.darkbytes.dev\/?p=60","title":{"rendered":"Between Water and Code: What Canyoning Taught Me About Leading Engineering Teams"},"content":{"rendered":"
\"\"<\/figure>\n\n\n

There\u2019s a particular kind of conversation that happens in Costa Rica over coffee \u2014 the kind where someone unfolds a map on the table and points at a patch of green marked by nothing but contour lines and rivers. Someone inevitably asks, \u201cWhat\u2019s out there?\u201d<\/em><\/p>\n\n\n\n

That simple question is how most canyoning adventures begin. A few friends \u2014 engineers, climbers, explorers \u2014 gathered around coffee, tracing potential routes through rivers and ravines. Within days, the idea turns into action: training sessions, gear checks, ropes and descenders spread across the floor.<\/p>\n\n\n\n

Canyoning is the art of descending rivers carved through volcanic rock \u2014 waterfalls, pools, narrow walls of stone. It\u2019s a mix of climbing, swimming, and rappelling through unpredictable terrain. Once you\u2019re inside a canyon, there\u2019s no turning around; you commit to the flow. Mistakes have consequences. Every knot, every anchor, every decision matters.<\/p>\n\n\n\n

When I\u2019m not navigating waterfalls, I lead a distributed team of software engineers as a Senior Security Software Architect in a large tech corporation. The difference between the two worlds seems obvious \u2014 one is made of stone and water, the other of code and systems \u2014 but the deeper I\u2019ve gone into both, the more parallels I\u2019ve found.<\/p>\n\n\n\n

Both depend on trust, awareness, discipline, and teamwork.<\/strong> Both require pushing limits while managing risk. And both demand the same thing: that you care not only about reaching the goal, but about the people who make the journey possible.<\/p>\n\n\n\n

This is what canyoning has taught me about leading engineering teams.<\/p>\n\n\n\n

1. The Mission Isn\u2019t Always Yours \u2014 But the Team Is<\/h3>\n\n\n\n

In canyoning, the mission is clear: get from the top of the river to the bottom safely. Sometimes the goal is exploration \u2014 a new canyon, a hidden waterfall. Other times it\u2019s a rescue mission, where you go not because you want<\/em> to, but because someone needs you to.<\/p>\n\n\n\n

That distinction matters. In engineering, most of our missions aren\u2019t chosen either. They\u2019re driven by business goals, customer demands, or strategic shifts. We don\u2019t always get to pick where<\/em> we go \u2014 but we always own how<\/em> we go.<\/p>\n\n\n\n

Whether I\u2019m descending a canyon or leading a distributed team through a product launch, the principle is the same: the mission might not be mine, but the team is.<\/strong><\/p>\n\n\n\n

My responsibility isn\u2019t just to execute a plan; it\u2019s to ensure that every member of the team is equipped, prepared, and supported to make it through whatever conditions arise. That\u2019s leadership in its purest form \u2014 not commanding, but protecting the system that protects everyone else.<\/p>\n\n\n\n

2. Training, Redundancy, and Knowledge Sharing<\/h3>\n\n\n\n

In canyoning, redundancy is survival. Every system has backups: a main anchor, a safety line, a second descender. But redundancy isn\u2019t just about gear \u2014 it\u2019s about skills<\/em>. Everyone in the team must know how to rig an anchor, set a rappel, tie a knot, perform a rescue.<\/p>\n\n\n\n

If only one person knows how to rig an anchor and that person gets injured, the entire team is stuck in a waterfall with no way out.<\/p>\n\n\n\n

Now imagine the same thing in an engineering team. The \u201canchor rigger\u201d is the person who knows how to deploy the CI\/CD pipeline, or the one who understands the encryption module, or the one who manages production secrets. If that person disappears, everything halts.<\/p>\n\n\n\n

In both worlds, knowledge silos are dangerous.<\/strong>
Sharing knowledge isn\u2019t a luxury \u2014 it\u2019s a safety mechanism. In canyoning, it keeps people alive. In engineering, it keeps systems alive.<\/p>\n\n\n\n

Cross-training, documentation, pairing, and group troubleshooting aren\u2019t just \u201cgood culture\u201d \u2014 they\u2019re what turn a group of individuals into a resilient, self-reliant team.<\/p>\n\n\n\n

3. Awareness and the Human Factor<\/h3>\n\n\n\n

Inside a canyon, water and gravity never stop. You\u2019re constantly assessing risk \u2014 not just external hazards, but the state of your teammates.<\/em><\/p>\n\n\n\n

You watch how people move through the water, how they land a jump, how they breathe after a cold pool. You listen for tone changes in their voice. You learn to spot fatigue, hesitation, or fear before it becomes a problem. Saying \u201cI\u2019m good\u201d<\/em> is never enough; you verify<\/em> it.<\/p>\n\n\n\n

Engineering teams face their own kinds of pressure \u2014 cognitive, emotional, organizational. Deadlines, outages, and shifting priorities create a psychological current that can quietly wear people down. Someone who used to contribute energetically starts going silent. Another seems perpetually \u201cbusy\u201d but disengaged.<\/p>\n\n\n\n

If you don\u2019t notice, the team\u2019s current starts to fragment.<\/p>\n\n\n\n

Just as in canyoning, awareness in engineering isn\u2019t passive \u2014 it\u2019s an active form of empathy. It\u2019s reading the flow of your team and knowing when to slow down, when to push, and when to get someone out of the cold for a while.<\/p>\n\n\n\n

A healthy team, like a good canyoning crew, thrives on awareness \u2014 not just of the environment, but of each other.<\/strong><\/p>\n\n\n\n

4. Trust, Communication, and Pragmatic Honesty<\/h3>\n\n\n\n

When you\u2019re hanging midair in a waterfall, you trust that your teammate at the top built the anchor right, that the rope is correctly set, and that they\u2019re paying attention. You can\u2019t see them, but you trust them completely.<\/p>\n\n\n\n

That level of trust doesn\u2019t appear magically; it\u2019s built through training, repetition, and constant communication. You shout signals over the roar of the water \u2014 short, clear, unmistakable words: \u201cROPE FREE!\u201d \u201cON RAPPEL!\u201d No ambiguity. No ego. No sugarcoating.<\/p>\n\n\n\n

Engineering teams need that same kind of clarity. Honest, pragmatic communication is the rope that holds the group together.<\/p>\n\n\n\n

When something\u2019s wrong \u2014 technical debt, poor architecture, unrealistic deadlines \u2014 you can\u2019t whisper around it. You have to name it directly and respectfully. Teams that speak the truth early avoid disasters later.<\/p>\n\n\n\n

Psychological studies show that psychological safety<\/em> \u2014 the belief that it\u2019s safe to take risks or admit mistakes \u2014 is one of the strongest predictors of high-performing teams. It drives engagement, creativity, and innovation because people stop wasting energy on fear.<\/p>\n\n\n\n

When engineers feel safe to say, \u201cI don\u2019t know,\u201d \u201cI need help,\u201d or \u201cThis won\u2019t work,\u201d they behave like a canyoning team shouting through a waterfall \u2014 not afraid to be loud, because everyone\u2019s listening.<\/p>\n\n\n\n

5. Knowing When to Push, When to Retreat<\/h3>\n\n\n\n

In canyoning, sometimes the only safe decision is to stop. A sudden flood, a loose anchor, a thunderstorm above \u2014 and you must abort. It\u2019s not defeat; it\u2019s wisdom. The canyon will still be there tomorrow.<\/p>\n\n\n\n

Engineering has its own versions of flash floods \u2014 failed deployments, impossible deadlines, unsustainable workloads. The pressure to \u201cpush through\u201d can be intense, but knowing when to pause or pivot is often what keeps the team alive.<\/p>\n\n\n\n

As in the canyon, retreating isn\u2019t weakness; it\u2019s strategic survival. It\u2019s how you ensure the team has the energy and clarity to tackle the next descent.<\/p>\n\n\n\n

Pride kills more projects than risk.<\/strong> Pragmatism saves more lives \u2014 and careers \u2014 than heroism ever will.<\/p>\n\n\n\n

6. Adversity as a Catalyst for Innovation<\/h3>\n\n\n\n

The best canyoners I know are not those who never face problems \u2014 they\u2019re the ones who improvise when problems hit. A missing rope, a blocked pool, a waterfall stronger than expected \u2014 you adapt with what you have.<\/p>\n\n\n\n

That same spirit translates directly to engineering. Adversity forces creativity. A constraint becomes a challenge; a bug becomes an opportunity for learning.<\/p>\n\n\n\n

But for adversity to produce innovation instead of fear, the environment must feel safe. When a team trusts each other, challenges spark ingenuity. When fear dominates, they freeze.<\/p>\n\n\n\n

Research confirms this: teams with high psychological safety innovate more, learn faster, and recover from mistakes more effectively. (Open Psychology Journal, 2023<\/a>)<\/p>\n\n\n\n

In both canyoning and engineering, the mindset is the same: adversity isn\u2019t the enemy \u2014 it\u2019s the teacher.<\/p>\n\n\n\n

7. Building a Canyoning Mindset for Engineering Teams<\/h3>\n\n\n\n

When you\u2019re deep inside a canyon, surrounded by roaring water and slick volcanic walls, every move depends on teamwork.
No one gets out alone.<\/p>\n\n\n\n

That same principle applies to engineering. The deeper and more complex the project, the more you rely on trust, clarity, and shared discipline.
Over the years, I\u2019ve realized that the mindset that keeps a canyoning team alive is the same one that keeps an engineering team resilient.<\/p>\n\n\n\n

Here are the core lessons I carry between the waterfall and the codebase:<\/p>\n\n\n\n

1. Redundancy Saves Lives<\/strong><\/p>\n\n\n\n

In a canyon, you always back up your anchor \u2014 not because you expect it to fail, but because you know it could. <\/em>In engineering, redundancy means sharing knowledge, documenting systems, and cross-training.
If one person disappears, the team should still be able to keep moving. That\u2019s not bureaucracy \u2014 it\u2019s survival engineering.<\/p>\n\n\n\n

2. Check Your Teammates, Not Just Your Gear<\/strong><\/p>\n\n\n\n

Before every descent, we check each other\u2019s harnesses and knots. Not because we don\u2019t trust \u2014 but because we do.<\/em>
The same goes for teams: check on your people, not just their output.
Metrics and dashboards are great, but they don\u2019t tell you if someone\u2019s mentally exhausted or quietly burning out. Awareness is the rope that holds the group together.<\/p>\n\n\n\n

3. Clear Signals Over the Noise<\/strong><\/p>\n\n\n\n

Inside a canyon, the water is so loud that you can\u2019t hear full sentences. You rely on short, universal calls: \u201cROPE FREE!\u201d \u201cON RAPPEL!\u201d \u201cCLEAR!\u201d
Engineering teams need the same clarity. Replace vague communication with simple<\/strong>, direct<\/strong>, honest<\/strong> language.
You don\u2019t need motivational speeches \u2014 you need shared understanding.<\/p>\n\n\n\n

4. Trust Your Belayer<\/strong><\/p>\n\n\n\n

When you step off a 40-meter waterfall, you trust that the person managing your rope knows what they\u2019re doing.
In a team, that\u2019s psychological safety.<\/em> It\u2019s the belief that you can take risks, ask for help, or make mistakes without being punished.
Without that trust, no one will move \u2014 in a canyon or in a sprint.<\/p>\n\n\n\n

5. Know When to Stop<\/strong><\/p>\n\n\n\n

Sometimes the water rises too fast. The canyon floods. You call it.
Knowing when to stop, pivot, or refactor isn\u2019t weakness \u2014 it\u2019s maturity.
Courage in engineering isn\u2019t about pushing harder; it\u2019s about knowing when persistence turns into danger.<\/p>\n\n\n\n

6. Water Always Finds a Way<\/strong><\/p>\n\n\n\n

No matter the obstacle, water always flows. It adapts, carves, and reshapes its environment.
That\u2019s what great engineering teams do \u2014 they adapt to constraints.
Budget cuts, legacy systems, organizational silos? Flow around them. Creativity often starts where comfort ends.<\/p>\n\n\n\n

7. Everyone Descends Together<\/strong><\/p>\n\n\n\n

In canyoning, success isn\u2019t measured when the first person reaches the bottom \u2014 it\u2019s when everyone<\/em> does.
The same is true for engineering. A project isn\u2019t a win if it burns out half the team in the process.
Celebrate shared outcomes. Design success so that everyone gets out of the canyon, stronger than before.<\/p>\n\n\n\n

8. Final Descent: Leading with Awareness and Flow<\/h3>\n\n\n\n

A canyoning mindset isn\u2019t about adventure \u2014 it\u2019s about awareness.
It\u2019s about backing up your systems, reading the flow, trusting your team, and adapting when the water changes direction.<\/p>\n\n\n\n

The best engineering teams \u2014 like the best canyoning crews \u2014 don\u2019t measure success by how fast they move, but by how well they move together.<\/em>
They descend through uncertainty with trust, clarity, and respect for the current.<\/p>\n\n\n\n

So whether you\u2019re leading a team through code or through a canyon, remember this:
Redundancy keeps you safe. Awareness keeps you alive. And trust brings everyone home.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

There\u2019s a particular kind of conversation that happens in Costa Rica over coffee \u2014 the kind where someone unfolds a map on the table and points at a patch of green marked by nothing but contour lines and rivers. Someone inevitably asks, \u201cWhat\u2019s out there?\u201d That simple question is how most canyoning adventures begin. A…<\/p>\n","protected":false},"author":1,"featured_media":61,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[12],"tags":[9,8,11,10],"class_list":["post-60","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-leadership","tag-engineering-culture","tag-leadership","tag-psychology","tag-teamwork"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t