Are You Carrying Baggage Into Technical Decisions?
I hesitated to write about this because "baggage" has such a negative connotation. No one likes to think they're bringing unnecessary history into a conversation. But the truth is, especially in tech, we often let our past dictate our actions.
Every project, every frustrating bug, every misguided company policy leaves a mark. We collect experiences—some good, some bad—and those experiences shape how we approach problems, make decisions, and interact with teammates.
The question is: Is your experience helping you make better decisions, or is it limiting your perspective?
Your past is a tool, not a rule. Knowing when to apply it—and when to let it go—is an underrated skill in software engineering. Let's unpack what that means.
How We Accumulate "Baggage"
Every engineer has a history. Past projects, team dynamics, and technical decisions shape how we approach new challenges. Sometimes, that history helps us make smarter decisions. Other times, it traps us in old thinking.
You've probably heard (or even said) things like:
- "That won't work. We tried it five years ago."
- "This new framework is garbage—just like the last one."
- "We don't need a PM, every PM I've worked with has been useless."
These statements don't come from out of the blue. They come from experience. However, experience without reflection leads to rigid thinking.
How Baggage Turns Into Bias
Here's what happens:
- You have a poor experience with a tool, process, or approach.
- You carry that experience forward, assuming history will repeat itself.
- Instead of assessing the present situation, you react based on the past.
The result? You shut down ideas before giving them a fair shot.
Tech moves fast. Just because something failed before doesn't mean it will fail again. The landscape changes—tools improve, teams mature, and business needs evolve. If you're still arguing against a decision because of something that happened years ago, ask yourself:
Am I responding to what's in front of me, or just reacting to the past?
When Your Experience Helps vs. When It Hurts
Experience should be an asset, not a barrier. But the line between applying what you've learned and letting past experiences limit you can be blurry.
When Experience Adds Value
Your perspective is helping when it:
- Provides relevant context – You highlight risks that others might overlook.
- Prevents past mistakes from repeating – Instead of saying "this won't work," you explain why and suggest alternatives.
- Strengthens decision-making – You use past experiences to weigh pros and cons, not as an automatic veto.
For example, if your team is considering a new tool and you've used it before, your insights can help refine the discussion. Maybe you ran into scaling issues last time—great, bring that up! But also ask: Has the tool improved? Was the problem a product limitation, or how was it implemented?
When Experience Holds You Back
Your perspective is hurting when it:
- Shuts down ideas prematurely – "We tried that before, and it didn't work." There is no discussion, no exploration—just a dead-end statement.
- Applies outdated assumptions – What failed five years ago might succeed today. Are you evaluating the present or just reacting to the past?
- Creates resistance to change – The tech industry rewards adaptability. If you always default to "the way we've always done it," you might miss a better solution.
Think about how you react in discussions. Are you helping the team think critically about decisions or dismissing new ideas based on old frustrations?
A useful gut check: Would you accept your reasoning from someone else? If another engineer rejected an idea just because it failed in the past, would that seem like solid logic—or stubbornness?
|
|
Wondering If a Startup Is Right for You?
Big Creek Growth Company shares what it’s really like to work in a startup and what founders are looking for when hiring.
|
|
How to Carry Your Experience the Right Way
Your experience is valuable, but only if you use it wisely. The best engineers aren't the ones who cling to the past—they're the ones who know when to apply their knowledge and when to rethink their assumptions.
Here's how to make sure your experience works for you, not against you.
Unpack Before You Speak
Before shutting something down, ask yourself:
- Is this still true?
- Has anything changed since the last time I saw this fail?
- Am I rejecting this because of past experience or because of real risks?
It's easy to assume that something that failed before will fail again. But context matters. The people, the technology, and the needs may be completely different now.
Challenge Your Own Assumptions
If your argument against an idea is based on past experience, be specific.
- What exactly went wrong last time?
- Was the issue the tool, the process, or how it was implemented?
- Is there new information that changes the equation?
Engineers value logic, but sometimes we hold onto beliefs that aren't as rational as we think. The best way to test your reasoning is to be as critical of your own assumptions as you are of new ideas.
Listen Before You React
If your first instinct is to say no, stop and listen.
- Ask why someone believes this approach is worth trying.
- Consider what they know that you might not.
- If you still disagree, explain your concerns in a way that moves the discussion forward.
Dismissing an idea without engaging makes you look rigid. Offering insights and asking questions makes you look experienced. One shuts down progress; the other shapes it.
The Future Belongs to Those Who Learn
Your past experiences are an invaluable resource. The best engineers don't just rely on what they've seen before; they use it to inform, not dictate, their decisions.
Before shutting down an idea, ask yourself:
- Am I responding to the present or just reacting to the past?
- Is my experience guiding the discussion, or is it limiting it?
- Would I accept this reasoning if someone else used it?
The tech industry rewards adaptability. New tools, methods, and ways of thinking constantly reshape how we work. The engineers who stay relevant are the ones who know when to let go of old assumptions.
So, here's a challenge: What's one outdated belief you're still holding onto? It could be a tool you refuse to revisit, a process you think will never work, or a team role you've written off. Take a second look—you might be surprised at what's changed.