Elementary, Mr. Watson: 3,340 pins, a $110,000 Mistake, and Lessons for Life
At the start of every PCB design course, I tell my students something that usually catches them off guard: “I'm no smarter than anyone sitting in this classroom. The only difference between you and me is that I have more experience.”
After more than four decades in the electronics industry, I've certainly collected plenty of experience. I've worked with talented engineers and designers, watched technology evolve, and been part of some amazing projects. But some of my greatest lessons didn't come from the projects that went right. They came from the ones that went terribly wrong.
That leads to the second thing I tell my students: “One of the reasons I'm qualified to teach at all is simply because I've already made most of the mistakes you're about to make.” That usually gets a laugh, but unfortunately, it's close to the truth. Some mistakes were small, easily corrected, and quickly forgotten. Others made my stomach drop, my blood pressure rise, and my career flash before my eyes. You know those moments when you stare at a design and think, “Well, this is going to be an interesting meeting.”
Anyone who's spent enough time in engineering knows what I mean. PCB design gives us plenty of opportunities to get things wrong. A misplaced decimal point, an incorrect footprint, a reversed connector, or one innocent assumption can turn months of work into an expensive paperweight. To prevent these disasters, we rely on ERC, DRC, simulations, design reviews, and countless verification procedures.
Yet despite these safeguards, mistakes still slip into our designs. After all, engineering is a human endeavor, and even the most experienced among us can overlook a detail or make an incorrect assumption. No matter how sophisticated our tools become, nothing replaces careful judgment, attention to detail, and a willingness to question our own decisions.
I remind my students that some of life's most valuable lessons aren't found in textbooks or lectures. They're learned the hard way, usually when something goes wrong, and we wish we could turn back the clock 24 hours. But there's a catch: A mistake only becomes a lesson if we're willing to take it to heart. Otherwise, we're just getting better at making the same mistakes. There's a big difference between having 40 years of experience and having one year of experience repeated 40 times. Experience isn't simply measured in years, but by what we've learned and how those lessons have changed us.
I certainly have an entire library of stories to prove it. One involved a complex $30,000 AMD Versal Premium XCVP1402 FPGA chip with 3,340 pins; it was a $110,000 mistake, and a lesson I'll never forget. The design required 18-layer, high-density routing, multiple power and ground planes with controlled impedance, high-speed signals, differential-pair length matching, and thousands of connections that needed precise pin assignments.
Managing the pin assignments and ensuring every signal reached its intended destination was no small task. The schematic was completed, the PCB laid out, and the design released for fabrication and assembly. Everything appeared to be progressing as planned. Unfortunately, appearances can be deceiving.
We didn't discover the FPGA was wired incorrectly until the boards were fabricated and assembled. By then, the components were soldered in place, the money was spent, and correcting the problem had become considerably more expensive. What would have been a relatively simple design correction became a $110,000 mistake. Apparently, our FPGA wasn't the only thing with crossed wires. If you've ever had to explain to management how a design made it through fabrication and assembly before someone discovered a problem, you know that's a meeting nobody volunteers for.
Lesson Learned #1
When things go wrong, you need to own the mistake. It's tempting to blame someone or start making excuses. When you're staring at $110,000 worth of assembled boards that don't work as intended, that temptation can be overwhelming. But assigning blame doesn't fix the connections. The important questions are, "How did we get here, and what are we going to do about it?"
Accepting responsibility is easier to discuss than to practice. Nobody enjoys admitting they made a costly mistake, especially with their professional reputation on the line. My first reaction was a sinking feeling, followed by the hope that we'd overlooked a simple explanation. But worrying about how bad things looked wasn't helping. The boards were sitting there, the problem was real, and someone needed to figure out what came next. I had to put my pride aside and look for a solution.
That's when the distinction between responsibility and problem-solving becomes important. Owning the mistake is the first step, but taking action is what makes the difference. Instead of dwelling on the $110,000 already spent, I needed to focus on what we could save. Could we correct the FPGA connections through reprogramming? Could we rework the boards? Would we have to start over? We could examine later how the mistake occurred and what needed to change in our design process. For now, our priority was finding a way forward. Feeling terrible about a mistake shows you care, but it won't get a circuit board working again.
Lesson Learned #2
Don't let the mistake's size grow bigger than your ability to solve it. It's easy to become so focused on the consequences that you lose sight of the problem itself. A $110,000 mistake certainly gets your attention, but staring at that number doesn't bring you closer to a solution. Neither does imagining how you'll explain it at the next management meeting. One of the most important things an engineer can do is separate emotion from engineering. The mistake has happened, and worrying won't change that. But we can influence what happens next.
After the initial shock, I reminded myself of something I've told countless students: Engineering is fundamentally about solving problems. Rather than viewing this as one enormous $110,000 disaster, we needed to break it into manageable questions. What exactly was wired incorrectly? Which connections were affected? What could be corrected, and what couldn't?
Most importantly, what options remained before declaring the boards a total loss? By addressing one question at a time, we could replace uncertainty with facts and frustration with a plan. Surely, somewhere among those 3,340 pins, there had to be a solution. The challenge was finding it before someone suggested dumping the entire project.
Lesson Learned #3
Once a failure has occurred, we can't change the mistake, but we can control our response. We can let it define the outcome or use what we learned to challenge our assumptions and find a way forward. Sometimes the hardest part is moving beyond the embarrassment and returning to what engineers do best: solving problems. In the words of engineer and author Henry Petroski. “Failure is central to engineering.”
As it turned out, the solution wasn't where we initially expected to find it. That's a story for my next column, where I'll share how we tackled a 3,340-pin nightmare, what it took to get those boards working, and how a $110,000 mistake became one of the most valuable engineering lessons of my career.
This column originally appeared in the November 2026 issue of I-Connect007 Magazine.