I made a wiring error that left this power supply useless.
I started from scratch to build this replacement.
Cool! Now, build another one ’cause I need two. That are almost alike.
This one needs a wicked heat sink.
How will all those components fit on this board? Perhaps a different placement of the heat sink? It seems I need more space.
I don’t have to use the original board.
When you think, believe, act, or talk with limits to methods, behaviors, or actions, you also limit your possible solutions. See your world as if it always has fuzzy borders, as if the edges of your vision fades to a cloudy background full of possibilities, as if every challenge has multiple solutions.
As a tester, I am challenged frequently to scrutinize gherkin that describe what to build, software that was built using both knowledge, experience, and interpretation, and, most challenging of all, suggestions on what and how to test.
You start by stating you see things differently. Engage your peers in a conversation to nourish your gherkin into robust examples, to explore new and changed code frequently, to understand alternative viewpoints on what others want to learn about product behaviors.
Then, challenge (respectfully but with assertiveness). I say challenge because sometimes products are not as complex or interrelated as they seem, because a simpler test may lead to adventurous exploring, because you need to use your time wisely, and because the succeeding conversation may uncover the assumptions that have become hidden with familiarity or painful with production issues.
Uncover the perceived limits and unlock many potential solutions.