[marblessubtext]

> If it's not the right path to a solution, they will decide, not you.

This is a dangerous position to take. I have a junior dev on my team frequently asking for help on Z when X is still a problem. If I actually answer his question, what he puts out is a disaster.'

Like he was having trouble with generating prime numbers. I could have answered his question, but why is he generating prime numbers? Long story short, to create an "optimal" number of threads to insert to a database because inserts were slow and he had 100k to do. Dude. Batch insert. Why are we threading, absolutely not, no. Stepping back Z, Y, X, and V and finding a better solution. 1/10th the code, 1/20th the time, better for the DB.

When you have someone on your team doing things like this, absolutely ask about X.