<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joseph Santamaría Castro on Medium]]></title>
        <description><![CDATA[Stories by Joseph Santamaría Castro on Medium]]></description>
        <link>https://medium.com/@josephsantacastro?source=rss-272da6d6a089------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*A4J8cStAJx8lflHI</url>
            <title>Stories by Joseph Santamaría Castro on Medium</title>
            <link>https://medium.com/@josephsantacastro?source=rss-272da6d6a089------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:29:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josephsantacastro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What This Apprenticeship Actually Changed]]></title>
            <link>https://medium.com/@josephsantacastro/what-this-apprenticeship-actually-changed-1a38c3832ef4?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a38c3832ef4</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 17:42:54 GMT</pubDate>
            <atom:updated>2026-06-12T17:42:54.665Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*nhpWppszdIimSp_E.jpg" /></figure><p><em>The most important lessons are not always the technical ones.</em></p><p>When I started this apprenticeship, I expected to learn technical skills.</p><p>And I did.</p><p>I worked with Git and GitHub workflows, user stories, Scrum, Kanban, testing, code smells, refactoring, documentation, and Ruby. I spent hours reading, building, reviewing, and practicing concepts that are part of modern software development.</p><p>But looking back, those are not the lessons that stayed with me the most.</p><p>The biggest change was not technical.</p><p>It was how I started thinking about work.</p><h3>Learning Is Not the Same as Accumulating Knowledge</h3><p>One thing I realized very quickly is that learning is not simply collecting information.</p><p>Most developers know that they should write tests.</p><p>Most know what documentation is.</p><p>Most understand concepts like code quality, estimations, or agile methodologies.</p><p>The challenge is not knowing they exist.</p><p>The challenge is understanding why they matter.</p><p>Throughout the apprenticeship, I found myself asking that question repeatedly.</p><p>Why are we documenting this?</p><p>Why are we estimating this way?</p><p>Why are we following this process?</p><p>Why does this quality standard exist?</p><p>The more I asked those questions, the more I realized that professional growth has less to do with memorizing concepts and more to do with developing judgment.</p><h3>Quality Is Intentional</h3><p>Another lesson that stayed with me is that quality rarely happens by accident.</p><p>Good documentation is intentional.</p><p>Good communication is intentional.</p><p>Good testing is intentional.</p><p>Even good teamwork is intentional.</p><p>Before, I often thought of quality as the final result.</p><p>Now I see it differently.</p><p>Quality is built through hundreds of small decisions that nobody notices at the moment.</p><p>A clear message.</p><p>A thoughtful question.</p><p>A well-defined requirement.</p><p>A test case that prevents a future issue.</p><p>Individually, they seem small.</p><p>Together, they define the outcome.</p><h3>Leadership Starts Earlier Than Most People Think</h3><p>One idea that became stronger during this experience is that leadership has very little to do with titles.</p><p>Leadership appears when someone takes ownership.</p><p>When someone helps create clarity.</p><p>When someone improves a process.</p><p>When someone shares knowledge that helps others move faster.</p><p>I have always believed that influence does not begin when a title is assigned.</p><p>It begins when people consistently create value around them.</p><p>This apprenticeship reinforced that belief.</p><h3>My Direction Became Clearer</h3><p>Something else happened that I did not fully expect.</p><p>My professional direction became clearer.</p><p>Over the last few years, I have invested a significant amount of time learning about Artificial Intelligence.</p><p>Reading, experimenting, building, studying, and following the evolution of the field.</p><p>Throughout this apprenticeship, and especially through experiences outside of it, I became even more certain that AI Engineering is the path I want to pursue.</p><p>Not because it is trending.</p><p>Not because it is popular.</p><p>But because it is one of the few areas that continuously keeps me curious.</p><p>And I have learned that curiosity is often one of the strongest indicators of where you should invest your energy.</p><h3>What I Take With Me</h3><p>If someone asked me what I gained from this apprenticeship, I could list technologies, methodologies, and tools.</p><p>But that would not be the complete answer.</p><p>What I really gained was perspective.</p><p>A deeper appreciation for quality.</p><p>A stronger sense of ownership.</p><p>A better understanding of how teams create value.</p><p>And more clarity about the kind of professional I want to become.</p><h3>Closing Thought</h3><p>When I started this apprenticeship, I expected to improve technical skills.</p><p>And I did.</p><p>But the biggest change was learning to think differently about work.</p><p>To look beyond the task.</p><p>To question the purpose behind decisions.</p><p>To understand that quality is intentional.</p><p>To recognize that leadership exists long before a title does.</p><p>And to leave with more certainty than ever about the direction I want to pursue.</p><p>For me, that has been the most valuable lesson of all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a38c3832ef4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being Around AI Engineers Made Me More Certain About My Future]]></title>
            <link>https://medium.com/@josephsantacastro/being-around-ai-engineers-made-me-more-certain-about-my-future-340806dc63e1?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/340806dc63e1</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Fri, 29 May 2026 15:29:35 GMT</pubDate>
            <atom:updated>2026-05-29T15:29:35.160Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Sometimes the most valuable part of an experience is not what you achieve, but what it confirms.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*azXDhHUPbgSCF5yj.jpg" /></figure><p>Recently, I participated in an AI hackathon.</p><p>My team ended up winning, and while that was exciting, it was not what stayed with me the most.</p><p>What I keep thinking about is the environment.</p><p>For an entire event, I was surrounded by people building AI products, discussing models, debating ideas, sharing experiences, and thinking deeply about the future of the field.</p><p>And something felt surprisingly natural.</p><h3>The Difference Between Interest and Passion</h3><p>Throughout my career, I have worked in different roles and across different areas of technology.</p><p>But AI has always been different.</p><p>It is not something I study because I have to.</p><p>It is something I study because I genuinely enjoy it.</p><p>It is the topic I read about after work.</p><p>The topic I spend weekends learning more about.</p><p>The topic that keeps pulling my attention even when nobody is asking me to learn it.</p><p>That kind of curiosity is difficult to fake.</p><p>And over time, I realized it was more than curiosity.</p><p>It was direction.</p><h3>Feeling at Home</h3><p>One of the things I enjoyed most about the hackathon was the quality of the conversations.</p><p>Not because everyone agreed.</p><p>Quite the opposite.</p><p>People challenged ideas.</p><p>Questioned assumptions.</p><p>Compared approaches.</p><p>Discussed trade-offs.</p><p>The conversations were technical, but they were also thoughtful.</p><p>And what stood out to me was how comfortable those discussions felt.</p><p>I wasn’t thinking about keeping up.</p><p>I wasn’t trying to prove anything.</p><p>I was simply enjoying being part of the conversation.</p><p>That feeling is difficult to describe, but I think many people experience it at some point in their careers.</p><p>You find yourself surrounded by people who are deeply interested in the same things that motivate you.</p><p>And suddenly, you realize you are exactly where you want to be.</p><h3>Clarity Is Sometimes More Valuable Than Validation</h3><p>The hackathon did not change my goal.</p><p>If anything, it reinforced it.</p><p>I’ve spent a lot of time learning about AI, experimenting with tools, following new developments, and trying to understand how the field is evolving.</p><p>The experience simply gave me more clarity.</p><p>It reminded me that this is the direction I want to continue pursuing.</p><p>Not because AI is popular.</p><p>Not because it is growing rapidly.</p><p>But because it is one of the few areas that consistently makes me want to learn more.</p><p>The more I study it, the more curious I become.</p><p>And I think that is usually a good sign.</p><h3>The Importance of Being Around the Right People</h3><p>Something else I took away from the experience is how important environment can be.</p><p>Growth is often associated with courses, books, certifications, and technical practice.</p><p>Those things matter.</p><p>But the people around you matter too.</p><p>Being around ambitious people raises your standards.</p><p>Being around curious people pushes you to think differently.</p><p>Being around experts helps you see possibilities you might not have considered before.</p><p>Sometimes growth comes from learning something new.</p><p>Other times, it comes from being reminded of what excites you in the first place.</p><h3>Closing Thought</h3><p>Winning the hackathon was a great experience.</p><p>But the biggest takeaway was not the result.</p><p>It was the confirmation that I am moving in a direction that genuinely excites me.</p><p>There is something powerful about finding yourself in a room full of people who share the same curiosity, the same energy, and the same passion for a field.</p><p>Not because it tells you where you are today.</p><p>But because it reminds you where you want to be tomorrow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=340806dc63e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cost of Overengineering]]></title>
            <link>https://medium.com/@josephsantacastro/the-cost-of-overengineering-2a51f239eac5?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a51f239eac5</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Thu, 14 May 2026 21:09:43 GMT</pubDate>
            <atom:updated>2026-05-14T21:09:43.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*sugXlomIZlzRZEbc.jpg" /></figure><p><em>Not every problem needs a complex solution. Sometimes the hardest skill is knowing when simplicity is enough.</em></p><p>One thing I’ve started noticing more in technical environments is how easy it is to confuse complexity with quality.</p><p>A solution looks more impressive when it has more layers.<br>More abstractions.<br>More architecture.<br>More “flexibility.”</p><p>And sometimes, those things are necessary.</p><p>But not always.</p><h3>Complexity Has a Real Cost</h3><p>In theory, overengineering usually sounds reasonable.</p><p>You prepare for future scenarios.<br>You make the system “scalable.”<br>You add flexibility for possibilities that might appear later.</p><p>The problem is that every layer of complexity creates a cost.</p><p>More things to maintain.<br>More things to explain.<br>More things that can fail.</p><p>And in many cases, the future problems we prepare for never actually arrive.</p><p>But the complexity stays.</p><h3>I’ve Seen How Small Decisions Accumulate</h3><p>Something I’ve noticed in documentation, QA processes, and technical workflows is that unnecessary complexity rarely appears all at once.</p><p>It accumulates slowly.</p><p>A process gets added “just in case.”<br>An extra step becomes permanent.<br>A rule stays even after the original problem disappears.</p><p>At first, none of it seems dangerous.</p><p>But over time, teams start spending more energy maintaining the process than benefiting from it.</p><p>That is when work starts feeling heavier than it should.</p><h3>Simplicity Requires More Thinking</h3><p>One thing I’ve learned is that simple solutions are not always easier to create.</p><p>In many cases, they require more understanding.</p><p>To simplify something correctly, you need to understand:</p><ul><li>what actually matters</li><li>what can be removed</li><li>what risks are real</li><li>and what complexity is unnecessary</li></ul><p>That requires judgment.</p><p>Because simplicity is not about doing less work carelessly.</p><p>It is about removing what does not create value.</p><h3>Good Work Is Not Measured by Complexity</h3><p>I think there is pressure in technical environments to make solutions look impressive.</p><p>But in real teams, the best solutions are often the ones that:</p><ul><li>are easy to maintain</li><li>easy to explain</li><li>easy to adapt</li><li>and easy for others to work with later</li></ul><p>Not because they are simplistic, but because they are intentional.</p><h3>The Future Also Matters</h3><p>One thing overengineering often ignores is the future experience of the team.</p><p>Every unnecessary abstraction becomes something another person has to understand later.</p><p>Every extra layer becomes another place where confusion can appear.</p><p>And eventually, someone has to maintain all of it.</p><p>That is why simplicity is not only a technical decision.</p><p>It is also a collaborative one.</p><h3>Closing Thought</h3><p>Building complex systems is not always the sign of strong engineering.</p><p>Sometimes, strong engineering is knowing when complexity is unnecessary.</p><p>Because good work is not about adding as much as possible.</p><p>It is about solving the problem clearly, intentionally, and without creating weight that the future team will have to carry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a51f239eac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Waiting for Perfect Information Is a Decision Too]]></title>
            <link>https://medium.com/@josephsantacastro/waiting-for-perfect-information-is-a-decision-too-bfbf36eba76f?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfbf36eba76f</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 20:52:41 GMT</pubDate>
            <atom:updated>2026-04-29T20:52:41.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*maNX3YpSgURVX-4U.jpg" /></figure><p><em>In professional environments, waiting for certainty can be more expensive than moving forward with what you already know.</em></p><p>One thing I’ve started to notice more in real work is how often decisions need to be made without having the full picture.</p><p>Requirements are not always complete.<br>Context is sometimes unclear.<br>Priorities shift while you are still trying to understand the original task.</p><p>At first, that feels uncomfortable.</p><p>The natural reaction is to pause.</p><p>Wait for more details.<br>Wait for confirmation.<br>Wait until things feel more certain.</p><p>It feels responsible to wait.</p><p>But in practice, it is not always the best choice.</p><h3>Waiting Has a Cost</h3><p>Something I didn’t fully appreciate before is that waiting is not neutral.</p><p>When you wait, progress slows down.<br>Other people depend on your work.<br>Conversations get delayed.<br>Momentum disappears.</p><p>And sometimes, by the time you finally have “clear” information, the situation has already changed.</p><p>I’ve seen tasks stay in that state where they are not blocked, but not moving either.</p><p>Everything is almost ready, but nothing actually moves forward.</p><p>And that state is more expensive than it looks.</p><h3>Decisions Create Movement</h3><p>What I’ve been learning is that progress in a team often depends on someone being willing to move forward with what is available.</p><p>Not guessing blindly.<br>Not ignoring risks.<br>But making a decision with the context you have.</p><p>Even if it is not perfect.</p><p>Because once a decision is made, something important happens.</p><p>Movement.</p><p>Others can react.<br>Adjustments can be made.<br>Work can continue.</p><p>Without that, everything stays in a loop of waiting for clarity that may never fully arrive.</p><h3>Context Matters More Than Certainty</h3><p>The quality of a decision is not defined by having perfect information.</p><p>It is defined by how well you understand what is already available.</p><p>What do we know for sure?<br>What assumptions are we making?<br>What are the risks if we move forward?<br>What are the risks if we don’t?</p><p>Those questions help you move from uncertainty to intention.</p><p>And intention is usually enough to make a reasonable decision.</p><h3>You Can Adjust, But You Can’t Move Without Deciding</h3><p>One thing that helped me feel more comfortable with this is understanding that most decisions are not permanent.</p><p>They can be adjusted.<br>They can be improved.<br>They can be revisited.</p><p>But none of that happens if the decision is never made.</p><p>I’ve realized that sometimes people are not afraid of making the wrong decision.</p><p>They are afraid of being responsible for it.</p><p>But avoiding that responsibility usually creates bigger problems later.</p><h3>Responsibility Is Also About Moving Things Forward</h3><p>In many cases, being responsible is not only about doing things correctly.</p><p>It is also about making sure things keep moving.</p><p>That means recognizing when you have enough context to act.</p><p>And being willing to move forward, even if things are not completely clear.</p><p>Not perfectly.</p><p>But intentionally.</p><h3>Closing Thought</h3><p>Perfect information rarely arrives.</p><p>Work still needs to move forward.</p><p>And in many cases, the difference is not who knows more.</p><p>It is who is willing to decide with what they have.</p><p>Because progress is not built on certainty.</p><p>It is built on decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfbf36eba76f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Engineers Build Features. Great Ones Understand Why]]></title>
            <link>https://medium.com/@josephsantacastro/good-engineers-build-features-great-ones-understand-why-4abd5374e044?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/4abd5374e044</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 17:04:09 GMT</pubDate>
            <atom:updated>2026-04-14T17:10:51.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*mLotQPc-9Xq1Bm7W.jpg" /></figure><p><em>Understanding how to execute is important. Understanding why something should exist is what creates real impact.</em></p><p>This weekend, I attended a professional class focused on leadership.</p><p>The session was well structured. It focused on execution, decision-making, and how to guide teams effectively. There was a strong emphasis on doing things correctly, following processes, and delivering results.</p><p>From a technical and operational perspective, it was solid.</p><p>But as I listened, something stood out to me.</p><p>Most of the conversation was centered around how to do things.<br>Very little attention was given to why those things matter.</p><p>And that made me reflect on something I’ve been applying consistently in my own work.</p><h3>Leadership Starts with Context</h3><p>One of the biggest differences I’ve noticed between execution and leadership is context.</p><p>Anyone can follow a process and get a result.</p><p>But leadership requires understanding whether that result actually makes sense.</p><p>Why are we doing this?<br>What problem are we solving?<br>What happens if we don’t do it?<br>Is this the best way to approach it?</p><p>Without those questions, work can look correct from the outside, but still fail to create real value.</p><p>That is where the “why” becomes critical.</p><h3>The “Why” Defines the Quality</h3><p>This is something I apply constantly, especially when working on documentation.</p><p>Every time I write something, I ask myself:</p><p>Why does this need to exist?</p><p>Who is going to use this?<br>What decision will they make based on it?<br>Does this actually help, or does it just look complete?</p><p>Because I’ve learned that documentation is not valuable because it exists.</p><p>It is valuable when it helps someone move faster, understand better, or make a decision with confidence.</p><p>Without that, it becomes noise.</p><h3>I’ve Seen It Clearly in QA</h3><p>This becomes even more visible in QA.</p><p>When reviewing something, I don’t only look at whether it works.</p><p>I try to understand why it is being tested that way.</p><p>Is this test actually improving quality?<br>Is it covering something meaningful?<br>Or are we just repeating steps without understanding their purpose?</p><p>Because I’ve seen what happens when that question is missing.</p><p>Small decisions that don’t fully make sense start to accumulate.<br>Processes become heavier.<br>And over time, the team spends more effort maintaining things that should have been questioned from the beginning.</p><p>At that point, someone has to step in and fix what was never properly understood.</p><h3>Execution Without Context Has Limits</h3><p>One of the risks I keep noticing is how easy it is to confuse execution with impact.</p><p>You can complete tasks, follow processes, and deliver exactly what was requested.</p><p>And still miss the point.</p><p>Because if the underlying problem is not fully understood, the solution will always have limitations.</p><p>That is why understanding the “why” is not just a nice-to-have.</p><p>It is what allows better decisions.</p><p>Sometimes it leads to simpler solutions.<br>Sometimes it avoids unnecessary work.<br>Sometimes it changes the direction completely.</p><p>But in every case, it improves the outcome.</p><h3>Understanding “Why” Is Preventive Work</h3><p>Another thing I’ve learned is that asking “why” is not slowing things down.</p><p>It is preventing problems.</p><p>It reduces rework.<br>It keeps processes clean.<br>It forces decisions to be intentional instead of automatic.</p><p>And more importantly, it shifts your mindset.</p><p>You stop doing things just to complete them.<br>You start doing them because they make sense.</p><h3>Closing Thought</h3><p>Good engineers can build what is asked.</p><p>Great ones take a moment to understand why it is being built.</p><p>Because in the end, the value of the work is not defined by how well you follow a process.</p><p>It is defined by whether the result actually solves the right problem.</p><p>And that starts by asking a simple question early.</p><p>Why?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4abd5374e044" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Don’t Need a Title to Create Impact]]></title>
            <link>https://medium.com/@josephsantacastro/you-dont-need-a-title-to-create-impact-7f0bf7c1a629?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f0bf7c1a629</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 18:01:11 GMT</pubDate>
            <atom:updated>2026-03-27T18:05:52.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*M0Z0Qw6shzn4z9hG.jpg" /><figcaption><em>of the most meaningful leadership is not assigned. It is practiced.</em></figcaption></figure><p>I’ve never believed that leadership depends on a title.</p><p>Even before working in more structured roles, it was clear to me that influence comes from how you act, not from what position you hold. Titles can give you responsibility, but they do not automatically create impact.</p><p>Recently, working from a more engineering-focused role, I had the chance to see that idea from a different angle.</p><p>Not as something conceptual, but as something that happens naturally in everyday work.</p><h3>Influence Does Not Wait for Permission</h3><p>While working through a certification that I found genuinely useful, I shared it with some teammates.</p><p>There was no plan behind it. I was not trying to lead anything. I simply thought it could help.</p><p>Later, one of them completed it and thanked me for recommending it.</p><p>It was a small moment, but it reinforced something I’ve always believed.</p><p>Influence does not need permission.<br>It does not need structure.<br>And it definitely does not need a title.</p><p>It just needs intention.</p><h3>Leadership Is Visible in Small Actions</h3><p>Leadership is often associated with bigger responsibilities.</p><p>Driving decisions.<br>Managing people.<br>Defining direction.</p><p>But in practice, a lot of impact happens in much smaller ways.</p><p>Sharing something valuable.<br>Helping someone move forward.<br>Creating small improvements in how others work.<br>Taking a moment to guide instead of staying silent.</p><p>These actions may seem minor, but over time they shape how a team grows.</p><p>They create momentum.</p><h3>Seeing It From Another Perspective</h3><p>What changed for me was not the belief itself, but the perspective.</p><p>From roles closer to leadership, influence is expected. It is part of the responsibility.</p><p>From an individual contributor perspective, you see how influence actually spreads.</p><p>Through conversations.<br>Through small suggestions.<br>Through actions that are not planned, but still move things forward.</p><p>And something I found interesting is that these moments often feel more authentic.</p><p>There is no pressure to lead.<br>No expectation to drive.<br>Just the opportunity to contribute.</p><p>And that is where a lot of real impact happens.</p><h3>Influence Also Creates Responsibility</h3><p>Something else I’ve been thinking about is that influence, even when informal, still carries responsibility.</p><p>When you recommend something, people might follow.<br>When you share an idea, others might build on it.<br>When you speak with confidence, it can shape decisions.</p><p>That means influence is not just about helping, but also about being intentional.</p><p>About making sure what you share adds value.<br>About being aware of how your actions affect others.</p><p>Even small moments can have a ripple effect.</p><h3>Growth That Extends Beyond You</h3><p>Something I value a lot is when growth does not stay individual.</p><p>When you find something useful and share it.<br>When someone else takes it and improves because of it.<br>When that continues to move forward.</p><p>That is when growth becomes collective.</p><p>And collective growth is much harder to achieve through authority alone.</p><p>It comes from behavior.</p><h3>Closing Thought</h3><p>You do not need a title to create impact.</p><p>You do not need a role to influence others.</p><p>And you do not need permission to contribute to someone else’s growth.</p><p>Leadership is not something you wait for.</p><p>It is something you practice.</p><p>Every day, in small decisions, often without anyone noticing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f0bf7c1a629" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Respect Shows Up in How You Use Other People’s Time]]></title>
            <link>https://medium.com/@josephsantacastro/respect-shows-up-in-how-you-use-other-peoples-time-c0f801b168cc?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0f801b168cc</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Fri, 13 Mar 2026 02:50:01 GMT</pubDate>
            <atom:updated>2026-03-13T02:50:01.083Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*mub03DdC5BB-cOI2.jpg" /><figcaption><em>In professional environments, respecting someone’s time is one of the clearest forms of professionalism.</em></figcaption></figure><p>In technical work, it is easy to focus only on solving problems.</p><p>We think about writing better code, designing better systems, or learning new tools. Those things matter, of course. They are part of becoming better engineers.</p><p>But something I have started to notice is that professionalism also shows up in something much simpler.</p><p>How we use other people’s time.</p><p>In teams, time is one of the most valuable resources. Everyone is responsible for different parts of the system, different tasks, and different decisions. When collaboration is needed, the way we approach that interaction can either make things easier for everyone or unintentionally create friction.</p><h3>Preparation Is a Form of Respect</h3><p>Recently, while working with the team, we had to prepare a set of questions related to QA processes.</p><p>Instead of simply asking things as they came up, we decided to organize our doubts first. We wrote them down, grouped them, and tried to understand what information was really necessary before reaching out.</p><p>The goal was simple: avoid interrupting people multiple times for things we could have clarified on our own.</p><p>Later, we even created a small document so that when people in QA join the process, they can quickly see the most common questions and the context behind them. That way they can move faster and avoid having to ask the same things repeatedly.</p><p>It was a small effort, but it made collaboration smoother.</p><p>And it made me realize something important.</p><p>Preparation is a form of respect.</p><h3>Good Questions Save Time</h3><p>Another thing I’ve learned is that the quality of the questions we ask matters.</p><p>A vague question can lead to a long conversation that still leaves things unclear. A well-thought-out question, on the other hand, often leads directly to the answer that is needed.</p><p>Before asking for help, it helps to pause and think:</p><p>What exactly am I trying to understand?<br>What information do I already have?<br>What part is actually unclear?</p><p>When questions are precise, the conversation becomes faster and more productive for everyone involved.</p><h3>Small Habits Create Better Collaboration</h3><p>None of this requires extraordinary effort.</p><p>It often comes down to simple habits.</p><p>Preparing before asking for help.<br>Grouping questions instead of sending them one by one.<br>Documenting answers so others do not have to ask again later.<br>Giving people enough context to respond quickly.</p><p>Individually, these actions may seem small. But in a team environment, they add up quickly.</p><p>They reduce interruptions.<br>They reduce repeated explanations.<br>They help everyone stay focused on their work.</p><p>Over time, those habits make collaboration much more efficient.</p><h3>Respect Is Visible in the Details</h3><p>In many ways, professionalism is not only about what we produce, but also about how we interact with others while producing it.</p><p>Respecting someone’s time shows that you value their work, their focus, and their responsibilities.</p><p>It also shows that you understand something important about teamwork: progress rarely depends on one person alone.</p><p>It depends on how well people coordinate, communicate, and support each other.</p><h3>Closing Thought</h3><p>Technical skills help us solve problems.</p><p>But the way we collaborate determines how smoothly those solutions come together.</p><p>Sometimes professionalism appears in large decisions or complex systems.</p><p>Other times, it appears in something much simpler.</p><p>Taking a moment to prepare before asking for someone else’s time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0f801b168cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Silence Is Expensive in a Team]]></title>
            <link>https://medium.com/@josephsantacastro/silence-is-expensive-in-a-team-90b7c6eeaa76?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/90b7c6eeaa76</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 22:22:08 GMT</pubDate>
            <atom:updated>2026-02-26T22:22:08.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwH3Q4yh2WTGIF7EfoDFQg.png" /><figcaption><em>In professional environments, silence is rarely neutral. It usually costs someone something.</em></figcaption></figure><p>There is a common belief in technical work that mistakes are the most expensive thing a team can make.</p><p>They are not.</p><p>Silence is.</p><p>Silence about a blocker.<br>Silence about confusion.<br>Silence about unrealistic timelines.<br>Silence about a decision you are not fully confident in.</p><p>At first glance, staying quiet can feel responsible. You do not want to interrupt. You do not want to look unprepared. You do not want to slow the team down.</p><p>But in reality, silence rarely protects the team. It protects ego.</p><p>And ego is expensive.</p><h3>The Cost of Not Speaking Early</h3><p>In every team, there are small moments that define whether things move smoothly or start to accumulate friction.</p><p>A requirement that was not fully clear.<br>A task that feels bigger than expected.<br>A dependency that might delay progress.<br>A concern about quality under pressure.</p><p>When those things are not communicated early, they do not disappear. They compound.</p><p>What could have been a five-minute clarification becomes a week of rework.<br>What could have been a quick alignment turns into frustration.<br>What could have been a small risk becomes a missed commitment.</p><p>The cost is not just technical.</p><p>It is emotional.</p><p>Uncertainty spreads. Trust weakens. Stress increases.</p><p>All because someone stayed silent for a little too long.</p><h3>Communication Is a Form of Ownership</h3><p>Speaking up is not about being loud. It is about being responsible.</p><p>It means saying:</p><p><em>“I need clarification before moving forward.”<br>“This timeline might be tighter than it looks.”<br>“I’m blocked and need help.”<br>“I think this approach could create technical debt later.”</em></p><p>Those conversations are not always comfortable. But they are necessary.</p><p>Clear communication is not an extra skill on top of technical ability. It is part of delivering quality work.</p><p>Because quality is not only what you build.<br>It is also how predictable and transparent your process is.</p><h3>Silence Creates Hidden Risk</h3><p>One of the most dangerous things in a team is invisible risk.</p><p>Work appears to be moving.<br>Updates sound positive.<br>No one raises concerns.</p><p>Until suddenly something breaks.</p><p>In many cases, the issue was not complexity. It was hesitation.</p><p>Hesitation to ask.<br>Hesitation to disagree.<br>Hesitation to admit uncertainty.</p><p>Professional maturity is not measured by how rarely you struggle. It is measured by how early you surface the struggle.</p><p>The earlier the signal, the smaller the impact.</p><h3>Protecting the Team Over Protecting Yourself</h3><p>There is a subtle shift that happens when you move from focusing on how you look to focusing on how the team performs.</p><p>You stop asking, “Will this make me look inexperienced?”<br>You start asking, “Will staying quiet make this harder for everyone later?”</p><p>That shift changes behavior.</p><p>You communicate earlier.<br>You document decisions clearly.<br>You confirm expectations.<br>You flag risks before they become explanations.</p><p>It is not dramatic. It is disciplined.</p><p>And discipline builds reliability.</p><h3>Closing Thought</h3><p>In professional environments, silence is rarely harmless.</p><p>It may protect comfort in the short term.<br>But it often creates cost in the long term.</p><p>The teams that scale well are not the ones that avoid mistakes.<br>They are the ones that surface uncertainty early.</p><p>Because speaking up is not a sign of weakness.</p><p>It is a sign that you care more about the outcome than about your ego.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90b7c6eeaa76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No One Is Coming to Remind You]]></title>
            <link>https://medium.com/@josephsantacastro/no-one-is-coming-to-remind-you-23c0f4c697b5?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/23c0f4c697b5</guid>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 20:20:42 GMT</pubDate>
            <atom:updated>2026-02-15T00:13:32.575Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Freedom in a professional environment is not the absence of control. It is the presence of trust.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*TgFImTbYdfDgXsixGAfaqw.png" /></figure><p>There is a moment in your professional life when something subtle changes.</p><p>No one reminds you about the deadline.<br>No one checks if you understood the task.<br>No one follows up to see if you are on track.</p><p>And that silence is not accidental.</p><p>It is trust.</p><p>When I started working in more structured professional environments, I noticed something interesting. The less I was reminded, the more I was expected to own.</p><p>No one was chasing me.<br>No one was micromanaging.<br>No one was hovering.</p><p>That absence was not a lack of attention.</p><p>It was responsibility being handed over.</p><h3>Freedom Is Not Relaxation</h3><p>It is easy to misunderstand autonomy.</p><p>Autonomy does not mean “work at your own pace.”<br>It means “manage your impact.”</p><p>There is a difference.</p><p>You are trusted to raise risks before they become problems.<br>To ask questions before assumptions turn expensive.<br>To prepare before meetings instead of improvising during them.</p><p>No one is going to remind you to do those things.</p><p>And that is exactly why they matter.</p><h3>Ownership Looks Boring From the Outside</h3><p>Ownership rarely looks dramatic.</p><p>It looks like sending an update before someone has to ask for it.<br>It looks like writing down a decision so the team does not revisit the same conversation next week.<br>It looks like clarifying a requirement early, even if it feels uncomfortable.<br>It looks like saying “I’m blocked” quickly, instead of staying silent and hoping it resolves itself.</p><p>These are small actions, but they change the emotional climate of a team.</p><p>They reduce uncertainty.<br>They reduce rework.<br>They reduce surprise.</p><p>They make other people’s work easier.</p><h3>The Shift From Doing Work to Owning Work</h3><p>There is a visible difference between someone who completes tasks and someone who owns their role.</p><p>The first one waits for clarity.<br>The second one creates it.</p><p>The first one reacts to deadlines.<br>The second one anticipates them.</p><p>The first one explains why something failed.<br>The second one flags risk before it becomes failure.</p><p>Ownership is rarely loud.<br>It is visible in patterns.</p><p>In how early you communicate.<br>In how clear your documentation is.<br>In whether your updates reduce anxiety or create it.</p><h3>Responsibility Is Built in Small Behaviors</h3><p>No one celebrates:</p><ul><li>A well-written update.</li><li>A realistic estimation.</li><li>A documented decision.</li><li>A proactive follow-up.</li><li>A clean handoff that saves someone else an hour.</li></ul><p>But teams depend on those things more than they depend on brilliance.</p><p>Technical skill builds systems.<br>Personal responsibility builds trust.</p><p>And trust is what makes teams scalable.</p><h3>The Real Test of Professional Maturity</h3><p>At some point, growth stops being about what you know.</p><p>It becomes about how much supervision you need.</p><p>If someone has to chase you for updates, remind you about commitments, or clarify what you already agreed to, the issue is not capacity.</p><p>It is ownership.</p><p>The highest form of responsibility is not doing more work.</p><p>It is becoming someone who requires less monitoring.</p><h3>Closing Thought</h3><p>In professional environments, no one is coming to remind you.</p><p>Not because no one cares.</p><p>But because you are expected to care first.</p><p>And the day you understand that,<br>you stop being managed<br>and start being trusted.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23c0f4c697b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staying a Learner When Comfort Is an Option]]></title>
            <link>https://medium.com/@josephsantacastro/staying-a-learner-when-comfort-is-an-option-3dd509da74f7?source=rss-272da6d6a089------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dd509da74f7</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Joseph Santamaría Castro]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 19:19:18 GMT</pubDate>
            <atom:updated>2026-01-29T19:19:18.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9sCa8X42VBgOphXwLt6cYQ.png" /><figcaption>Learning happens long before the work becomes visible.</figcaption></figure><p>There’s a moment in every technical career when learning becomes optional.</p><p>Not because there’s nothing left to learn, but because you already know enough to be comfortable.</p><p>And comfort, in this field, is rarely neutral.</p><p>When I started my apprenticeship at Pernix, I quickly understood that the program wasn’t designed to teach me how to code or introduce me to software development from zero. I already had a foundation. What it challenged instead was something more demanding:</p><p><strong>how intentional I am with the experience I already carry.</strong></p><h3>Experience Is Only Valuable When It’s Questioned</h3><p>Most of the early activities were familiar: reading <em>Clean Code</em>, working with Git and GitHub workflows, defining user stories, applying Scrum and Kanban, refactoring code smells, writing tests, tracking time, documenting decisions.</p><p>None of that was new.</p><p>What <em>was</em> new was the expectation behind it.</p><p>The expectation wasn’t speed.<br>It wasn’t output.<br>It was <strong>judgment</strong>.</p><p>I could have rushed through many of these tasks thinking, “I’ve done this before.”<br>Instead, I chose to work with a single guiding question:</p><blockquote>If someone inherits this work, will they trust my decisions, or have to undo them?</blockquote><p>That question quietly changes everything.</p><h3>Learning as a Professional Obligation</h3><p>One thing became clear very early: at Pernix, learning is not treated as a phase. It is treated as an obligation that comes with responsibility.</p><p>Tracking time with Clockify wasn’t about control. It was about awareness.<br>Pull requests weren’t about approval. They were about accountability.<br>Refactoring wasn’t about elegance. It was about respect for the future.</p><p>This type of learning is not about acquiring fundamentals. It is about sharpening judgment, reducing risk, and making choices that scale beyond the present moment.</p><h3>Quality Is Built Where No One Is Looking</h3><p>What impressed me most is how much importance is placed on small, well-executed decisions.</p><p>Clean READMEs.<br>Clear branch names.<br>Focused commits.<br>Explicit scenarios.<br>Honest estimations.</p><p>None of these are difficult in isolation.<br>What’s difficult is doing them consistently, especially when no one is watching.</p><p>That’s where professionalism lives.</p><p>As I prepare to work on projects like the Ruby Tic-Tac-Toe, the real challenge isn’t making the game work. It is making decisions I can stand behind months later. Decisions that make the code easier to trust, extend, and maintain.</p><h3>Learning and Leadership Share the Same Root</h3><p>One of the strongest signals I’ve seen is that learning and leadership are not opposites. They are built from the same root.</p><p>Documenting decisions.<br>Exposing work to review.<br>Writing openly about what can be improved.</p><p>These are not signs of insecurity.<br>They are signs of reliability.</p><p>Choosing to remain a learner when comfort is available doesn’t make you smaller. It makes you safer to work with.</p><h3>Closing Thought</h3><p>I’m not here to relearn what I already know.<br>I’m here to take responsibility for how I use it.</p><p>In this industry, comfort is easy to earn and expensive to keep.</p><p>Staying a learner is how I choose to pay that cost.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dd509da74f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>