For most of my career I learned the way most of us do, reading docs, watching talks, building things, breaking them, coming back, and slowly getting better.

These days I lead technical curriculum teams. And until recently, we built curriculum for that same kind of learner: a human.

That learner is no longer the only one in the room.

A new colleague has joined the workforce, quietly, without an onboarding session. It doesn’t sit through the course. It doesn’t watch the video. It reads our material in milliseconds and acts on it before the human has finished their coffee.

We call them agents. Increasingly, they behave like digital employees.

And that changes everything about how we teach.

The New Learner: In the Workflow, Not in the Classroom

Digital employees are already doing the work. Writing code. Querying data. Drafting the first version of almost everything.

But something is different about how they learn.

They don’t move through a path. They don’t build intuition over weeks. They load context, act, and move on.

• They learn at the moment of need, not in advance
• They don’t retain a course; they retrieve a fact
• They don’t ask clarifying questions; they fill gaps with guesses
• They’re only as good as the material we make readable to them

This isn’t learning in the way we’ve always meant it. It’s closer to instant, literal absorption — with no room for a human that has to read between the lines.

Why Traditional Curriculum Falls Short

For years we’ve shaped technical education around human strengths and human limits:

• Video courses
• Hands-on labs
• Learning paths
• Certifications

These still matter for the people on our teams. But they assume a learner who watches, reflects, and remembers.

An agent does none of those things.

You can’t hand a machine a two-hour course and expect understanding. It doesn’t watch. It parses. And when our best knowledge is locked inside formats only a human can open, the agent is left to guess — confidently, and sometimes wrongly.

The gap isn’t intelligence. It’s format.

Serving the Digital Employee

Teaching this new learner doesn’t start with new content. It starts with a new shape for the content we already have.

Make knowledge machine-readable The same expertise, structured so an agent can load it directly, not buried in a video transcript no machine will ever play.

Teach at the point of action Agents learn inside the tool, in the flow of the work. Curriculum has to meet them there, not in a separate portal they’ll never visit.

Give it the context a human already has The LLMs shows up with general knowledge, not your conventions, your data, or your edge cases. That gap is ours to close, we can hand the agent that context directly, and it will use it. The work is naming what a person picks up from being here, and putting it where the agent can reach it.

Treat correctness as the product A wrong answer delivered instantly, at scale, is worse than no answer at all. Precision is the whole job now.

What This Asks of Us

The learner changed. That’s the part worth sitting with.

For most of the history of technical education, getting better meant a human getting better: slowly, with practice, over time. Now a real share of the learning happening around our work belongs to systems that absorb in an instant and act without pausing to wonder.

They will learn from something. The only open question is whether it’s from us, built with intent, or from whatever they assemble on their own.

For the first time, our teaching will be judged not only by what people come to understand, but by what machines get right. The craft is the same at heart: make hard things clear. The audience is what’s new.

The last few years have quietly reshaped how people show up at work.

Not through a single disruption, but through a constant stream of them.
War headlines that never quite leave the news cycle.
Economic pressure that shows up in grocery bills and mortgage rates.
Layoffs across the tech industry that remind everyone how fragile stability can be.

Even when none of these events directly affect someone’s role, they affect their attention. Their energy. Their sense of safety.

And that changes everything about work.

The New Reality: People Are Present, But Not Fully There

People are still showing up. Delivering. Attending meetings. Hitting deadlines.

But something has shifted.

There is a growing disconnect between physical presence and emotional presence.

• People are thinking about their families more
• Re-evaluating life decisions more frequently
• Carrying low-grade anxiety into everyday work
• Protecting their energy in ways they didn’t before

Work is no longer the center of identity for many. It’s a pillar, but one that competes with everything else happening in their lives.

This isn’t disengagement in the traditional sense. It’s redistribution of attention.

Why Traditional Engagement Tactics Are Failing

For years, organizations have relied on familiar tools to drive engagement:

• Team events
• Recognition programs
• Performance incentives
• Career growth frameworks

These still matter—but they assume a level of emotional availability that many people simply don’t have right now.

You can’t “optimize engagement” when someone is quietly worried about:

• Job security
• Cost of living
• Global instability
• Personal priorities shifting beneath them

The gap isn’t about motivation.
It’s about cognitive and emotional bandwidth.

Reconnecting Teams in a Distracted World

Reconnection doesn’t come from bigger initiatives.
It comes from small, consistent signals.

Make space for real check-ins

Not just “How’s the project?” but “How are you actually doing?”

Normalize fluctuating capacity

High performance is no longer linear.
Create room for intensity and recovery.

Reduce unnecessary load

Every meeting, every process, every update competes with mental bandwidth.

Reinforce shared purpose

In chaotic times, people need to know:

Why does this work matter beyond the task itself?

The Hard Truth

You can’t eliminate the chaos outside of work.

You can’t fully control how people feel walking into their day.

But you can shape what happens once they’re inside your team.

And that matters more than ever.

As the year closes, I’ve been thinking about a truth that sits at the heart of effective teams in tech: high performance and resilience go hand-in-hand, but even the most resilient teams don’t last forever. They are living systems — shaped by context, change, and the people within them.

Across the stories I’ve shared this year, from empathy-driven leadership to reflections on “Team #1,” the invisible network of peers that sustains us, one theme keeps returning: the delicate balance between stability and change.

Resilience Is Not Immortality

Resilience is often spoken of as if it guarantees longevity: a team that is resilient should persist through disruption. But what I’ve learned — and what I’ve seen in teams I’ve led or partnered with — is that:

• Resilience helps teams absorb stress and adapt — but that adaptation is not about staying the same. It’s about evolving.
• High performance reflects context alignment — the team fits its environment, goals, and constraints. When the environment shifts drastically (market, product, leadership, personal lives), that alignment dissolves.
• People change, and so do priorities — a team member who once thrived within one set of expectations may find that their trajectory no longer fits as the team or company’s needs evolve.

Put bluntly: resilience buys time and adaptability, not permanence.

Fine-Tuning as a Continuous Discipline

In stable times, team performance feels like tuning a high-performance engine — small adjustments, calibrations, iterative improvements. But in times of change, the tuning becomes continuous — not optional:

• Organizational shifts (strategy pivots, scaling phases, restructuring) often require rebalancing responsibilities, interfaces, and expectations.
• Personal transitions — promotions, life events, evolving career goals — change how each individual contributes and perceives growth.
• Leadership changes outside the team can ripple inward, forcing a realignment of purpose and practices.

This is familiar territory: the idea that expectations, communication patterns, and psychological safety must be continually revisited and reshaped as circumstances change.

When “Forever” Is a Liability

There’s a quiet expectation in many tech organizations: “If we build a high-performing team, it should last.” But the reality is richer and more humane:

• Teams transform rather than endure unchanged.
• Performance plateaus or degrades not always because of failure — but because the team’s form no longer matches its function.
• Resilience without reflection can generate inertia; performance without recalibration can burn out talent.

What keeps a team healthy is intentional tuning — not just resilience. It’s a cycle of diagnose → adjust → validate → adjust again.

A Reflection for 2025

As we step into a new year:

• Celebrate the resilience your teams demonstrated this year.
• Acknowledge the changes — both professional and personal — that altered team dynamics.
• Recognize that high performance is not a fixed state, but a dynamic equilibrium requiring continuous tuning.

In leadership, in teams, and in culture, the real work is not building something that lasts forever, but something that can evolve well — something that adapts without losing sight of purpose, belonging, and growth.

Leadership extends beyond managing teams and projects—it’s also about mentoring the next generation, both as professionals and parents. This week, I had the unique opportunity to blend these roles during the "Bring Your Kid to Work" day, an initiative of some schools in Ireland. I brought my eldest daughter, Beatriz, along with two of her school friends, to MongoDB, where they dove into the world of databases and application development.

A Day at MongoDB

Our day began with an introduction to MongoDB and an overview of what my team—the Education Team—does to build technical curriculum for our customers and future customers alike. The goal was to demystify how technologies that power popular applications like TikTok, Netflix, and e-commerce platforms are created and maintained.

Teaching Young Minds

The highlight of the day was the exercise where Beatriz and her friends stepped into the shoes of instructors. They tackled the challenge of explaining how MongoDB can be used to build apps, applying it to contexts familiar to them like social media and online shopping. Watching them understand and then convey complex concepts was not just rewarding—it was a glimpse into the potential of young minds when given the right tools and encouragement.

Reflections on Leadership and Parenting

The experience reinforced my belief that as leaders, our influence can and should extend into educational realms. By opening doors to learning and demystifying the tech world, we can spark curiosity and ambition in young people. The joy and pride evident in the teens’ presentations reminded me of the crucial role we play, not just in guiding our direct reports but in shaping future innovators.

Conclusion

As we wrapped up our day, I was left with a renewed sense of purpose both as a tech leader and a parent. The intersection of these roles provides a powerful platform to influence and inspire, proving that the workplace can also be a classroom. It’s a reminder that in the quest to build better technology, we’re also tasked with building better futures.

As we wrap up another year, it’s a perfect time for reflection on the subtle yet profound lessons of leadership within the tech industry. One of the most impactful insights I’ve gained this year revolves around the concept of Team #1—the group of peers and fellow leaders—and it’s role compared to the team we directly manage.

The Dual Dynamics of Leadership

Leaders in tech often find themselves drawn back into the weeds with the teams they lead, especially given our technical backgrounds. It’s easy to become the de facto tech lead, diving into the details and solving problems directly. However, this year has taught me the significant value of stepping back and investing in Team #1, my peers and fellow leaders, to foster a broader impact.

Team #1 vs. The Teams We Lead

The distinction between supporting our peers (Team #1) and leading our direct reports is crucial yet often overlooked. While the immediate pull to assist our direct teams is strong, especially in high-pressure tech environments, I've learned that strengthening ties with my peers can enhance our collective effectiveness. This approach helps navigate and synchronize interdependencies and integrated processes more smoothly, benefiting all involved teams.

Lessons from Building Team #1 Spirit

Fostering a solid Team #1 spirit is indispensable. When leaders collaborate and support each other effectively, it sets a powerful example and creates a ripple effect, enhancing teamwork across all levels. This collaboration is especially critical in tech, where projects and processes are highly integrated across different teams. By aligning more closely with my peers, we’ll be able to tackle larger challenges more cohesively, ensuring that our teams operate in concert rather than in silos.

Implementing the Change

This shift in focus involves intentional efforts to build stronger relationships with my fellow leaders, regular sync-ups to discuss our teams’ overlaps and dependencies, and a collective strategy toward common goals. The outcome will be clear project flows, quicker resolution of cross-team issues, and a more unified leadership front.

Conclusion

As this year ends, my reflection on the importance of prioritizing Team #1 has reaffirmed my commitment to this leadership approach. Going forward, I will continue to strengthen these essential relationships, knowing that the success of the teams we lead is significantly amplified by the unity and support among their leaders.

Traditionally, my birthdays are a no-work zone—reserved strictly for escapades into the realms of personal experiences with my family & friends: travelling, nice food, or headbanging to heavy metal. However, this year’s celebration took a sharp, interesting, detour into something quite unprecedented: working on my birthday during an offsite with my new team, and, shockingly, not minding it one bit!

A New Tradition with New Teammates

Being the newbie leader on the block and flying out to another country for a team offsite could sound like the opening scene of a quirky, culture-clash film. Instead, it became a highlight of my year. The team went all out with birthday fun—there was cake (really good and chocolaty 😋!), gifts, and a dinner (delicious!) that would make any food-loving Portuguese happy. It wasn’t just a party; it was a crash course in community building, led by people who were quickly becoming more than colleagues.

The Power of Team Community

This warm initiation was more than just fun; it reinforced my belief in fostering a community within the team. When people feel genuinely connected—not just in the 'please fix this bug by EOD' way—it transforms collective output. Yes, agile frameworks talk about transparency and servant leadership, but nothing preaches it better than a team that knows when you desperately need a caffeine fix before a meeting 😉.

Finding Common Ground

Beyond strategic discussions and project planning, we bonded over shared loves: from Tattoos, Sports, to exchanging parenting survival hacks. Finding out that you’re not the only heavy metal/hard rock enthusiast at work is oddly comforting. These moments of connection, often peppered with dark, geeky humour, are what build the foundations of a resilient team.

🎂🥳

What began as a “reluctant” birthday at work turned into another memorable one. It was a reminder that leadership is as much about building genuine relationships as it is about steering the ship—or the Starship, if you will. This team showed me that even when you’re far from home, the right crew can make you feel like you’ve never left.

Transitioning into a new role can be as exciting as it is daunting, especially because building trust with a new team is fundamental. Recently, I shifted from Developer Relations to leading a team focused on Curriculum — two areas deeply intertwined with enablement and education of developers. After almost two weeks of onboarding journey, during this period and through conversations with my new team, I found myself reflecting once again on the true essence of effective leadership in a global setting. These discussions not only deepened my understanding of our collective strengths but also, quite unexpectedly, drew parallels with, of all things, Star Trek. (And for those who aren’t fans or familiar with Star Trek, bear with me — there’s a reason for this seemingly odd analogy!)

The Dialogue that Sparked Reflection

During one of these early interactions, a team member questioned what I intended to change about our current approach. My response was that I wouldn’t change what’s already working but would instead focus on areas where evolution is necessary, based on team feedback. This conversation stayed with me, leading to some unexpected musings on Star Trek of all things.

Star Trek: A Metaphor for Global Team Leadership

Star Trek might seem far from the real-world dynamics of a global team, but it offers a compelling model of collective effort. The Borg, with their single hive mind, represent one extreme of uniformity, sacrificing individuality for the sake of unity. Starfleet, on the other hand, exemplifies how a collective can thrive precisely because of its diversity — each member’s unique perspectives and skills enhance the group’s capability and resilience.

This Starfleet approach is closer to my vision for our team. We are not to be a group that simply follows orders or moves in unison; instead, we are a mosaic of individuals whose distinct abilities create a robust whole.

Leadership Approach in a Diverse Team

Adopting this Starfleet-inspired philosophy, I aim to build upon the existing strengths of our already established team:

• Empowerment: I am committed to fostering personal and professional growth, recognising and amplifying the unique talents that each team member already brings to the table.
• Collaboration: By enhancing the ways we interact and work together, I focus on respecting and utilising our diverse backgrounds to forge stronger, more innovative outcomes.
• Evolution: My approach is to refine and expand upon the effective practices already in place, focusing on incremental improvements that boost creativity and productivity, rather than implementing sweeping changes.

Looking Ahead

As I onboard into the organization and familiarise myself with the team, my role is not to reinvent but to enrich and extend our existing framework. I am dedicated to creating an environment where every individual feels valued and integral to our mission. Much like the exploratory voyages of the Starship Enterprise, my entry into this team is about continuous learning and discovery, leveraging our collective expertise to venture into new educational frontiers together.

After several years of strategic roles and management responsibilities, the craving to get back into the nitty-gritty of coding often hits hard. For tech leaders, the shift from high-level oversight to hands-on development can be rejuvenating. This time, my journey back to coding was complemented by an intriguing twist—pairing up with an AI companion available in the Cursor IDE, which transformed my coding experience by blending the best of human creativity with AI efficiency.

The Need for Hands-On Challenges

Every few years, I hit a professional plateau where strategic management no longer stimulates me as it once did. To reignite my passion for technology and maintain my edge, I dive back into coding. It’s not just about keeping my skills sharp; it’s about reconnecting with the core of what made me love tech in the first place. This periodic return to coding is crucial for my personal and professional growth.

Building with an AI Companion

I’m constantly brainstorming ways to automate or enhance my personal life through software. Recently, I was inspired by a common dilemma: tweaking recipes based on the limited ingredients available at home or adjusting them for guests with dietary restrictions. This sparked the idea for "BiteByte," a React web app powered by Spring AI and MongoDB, designed to transform culinary experiences. "BiteByte" not only customizes recipes based on available ingredients or dietary needs but also allows users to easily share these adaptations with friends and family. Among its features are AI-driven recipe customization, user security, and live cooking classes, all within a user-friendly interface.

The Role of AI in Development

Pairing with Cursor, transformed the development process. As a backend developer more comfortable with server-side logic, I often find front-end tasks challenging. Cursor’s assistance proved invaluable, especially in streamlining front-end development and offering insights where I was less experienced. This collaboration underscored the potential of AI to serve not just as a tool but also as an integral team member.

The architecture of BiteByte includes:

• Backend: A modular monolithic powered by Spring Boot, Spring AI and MongoDB. divided into modules for seamless AI integration.
• Frontend: Developed using React and managed through Vite, which optimizes building and serving processes, ensuring the application is both responsive and dynamic.

Github for BiteByte

Dedicating personal time to a cool project with hands-on coding and AI collaboration has been a powerful reminder of the dynamic nature of tech and the continuous learning it demands. This project not only refreshed my technical skills but also deepened my appreciation for the potential of AI, making it easier to develop.

Coming back from a summer break is like hitting the refresh button. You expect a smooth reboot, but sometimes it feels more like you’ve launched straight into a system update that’s taking longer than expected. As a tech leader, the challenges don’t wait for you to catch up—they start right where you left off.

Resilience Amid Routine Resets

Every tech leader knows that behind the sleek interface of any successful project, there are countless hours of debugging and patching. Post-break, it feels like the bugs have multiplied, each one testing our strategies and patience. This part of the job is about maintaining the codebase of your team’s morale and productivity—ensuring that every function returns the right output.

Advocating for Vision in Variable Scopes

Having a vision is one thing, but getting everyone on board? That’s like trying to get consensus on tabs vs. spaces—possible, but it requires patience and persistence. I’ve found myself re-explaining and redefining the roadmap to my strategies more times than I’ve refactored legacy code. It’s a process of aligning various stakeholders, each with their own parameters and priorities.

Bridging Byte-Sized Roles

Navigating between Developer Relations and Marketing is like translating between two different programming languages. Both are crucial yet each with its own syntax and use cases. The challenge lies in optimizing functions in one language without causing errors in the other. It’s about ensuring that tech-speak doesn’t get lost in marketing messages and that the engine of distribution exists to successfully reach the developer communities.

Continuous Integration of New Patches

As a woman in tech and a mom, my life is a constant beta test—balancing feature releases at work with patch updates at home. Proving your worth sometimes feels like you’re perpetually stuck in a commit loop, pushing updates to show continuous improvement and relevance.

Conclusion

This article sounds like me ranting, but it’s not. I am just in a constant loop of updates, patches, and sometimes, hard resets. But with each cycle, I refine strategies, improve systems, and prepare for the next surge.

In a global environment, the ability to maintain a cohesive team is more crucial than ever. This challenge is particularly pronounced in diverse teams, where differences in language, culture, and communication styles can easily lead to misunderstandings. As a leader of such teams, I’ve come to rely on three core values—integrity, transparency, and respect—to navigate these complexities and build a strong, unified group.

The Importance of Core Values

Integrity: Integrity in leadership means consistency in actions, values, methods, measures, principles, expectations, and outcomes. In a global team, this consistency helps establish a reliable foundation. It means that every team member, no matter where they are from, knows what to expect from their leaders and what is expected of them.

Transparency: Transparency is about being open in our communications and sharing necessary information. This ensures that all team members, regardless of their location or native language, are on the same page. Remember, when communicating via platforms like Slack, things can easily become out of context, so always be ready to jump on a call to clarify it.

Respect: Respect is the acknowledgement of the dignity of each team member, which includes respecting their cultural backgrounds and beliefs. In a global team, respect involves a willingness to learn from these differences and use them to enrich the team’s culture rather than allowing them to divide (Note: Of course, this goes both ways).

Navigating Cultural and Linguistic Differences

Misunderstandings can arise in any team, but in a global context, they are more prevalent due to the varied linguistic and cultural backgrounds of team members. For example, a message written in less-than-perfect English might be misconstrued, not due to a lack of effort but simply because of linguistic limitations. Here, the values of respect and transparency come into play, encouraging a culture where team members feel safe to seek clarification (Note: Don’t judge or jump into conclusions without trying to clarify it 1st)

Personal Reflections on Leadership Challenges

Recently, I was reminded of how crucial it is to consistently apply these values, especially when facing challenging situations that test our principles. While details are confidential, the experience underscored the importance of always leading with integrity, transparency, and respect to ensure that every team member feels valued and understood.