---
title: "Comment by Bruce Wells on \"The Problem-Solving Traps I Fell Into as a Junior Engineer\" | Hashnode"
description: "Great article and insights. I find the most important thing is understanding the problem you are trying to understand. You can't solve I a problem you don&#"
url: "https://hashnode.com/posts/the-problem-solving-traps-i-fell-into-as-a-junior-engineer/626ee8b2a2d355d4df440fc8/comment/627686a6317fc95a74ca8299"
---

[Discussion](https://hashnode.com/posts/the-problem-solving-traps-i-fell-into-as-a-junior-engineer/626ee8b2a2d355d4df440fc8)

Comment [The Problem-Solving Traps I Fell Into as a Junior Engineer](https://hashnode.com/posts/the-problem-solving-traps-i-fell-into-as-a-junior-engineer/626ee8b2a2d355d4df440fc8)

[Bruce Wells](https://hashnode.com/@PHPFUI)

[May 7, 2022](https://hashnode.com/posts/the-problem-solving-traps-i-fell-into-as-a-junior-engineer/626ee8b2a2d355d4df440fc8/comment/627686a6317fc95a74ca8299)

Great article and insights.

I find the most important thing is understanding the problem you are trying to understand. You can't solve I a problem you don't understand.

Talking with end users is also key. Often product managers are often not good at understanding or communicating the problem.

Next, understand your current tech stack, probably 50% of what you need to do is already done.

And finally, the simpler the solution is better. KISS. Don't over engineer.