A solver answers a different question than a hint. Knowing which one you need is the whole skill.
A solver and a hint are often bundled in the same menu, and they answer different questions. A hint tells you something about where you are. A solver tells you what the shortest route is. Using one when you wanted the other is why people feel either spoiled or still stuck after asking for help.
The solver is at its best when you have finished the puzzle and want to know how far off your route was. That is a review question, not a playing question, and the answer is genuinely interesting: a route one rung longer than par is often a better solve than a route at par, because it took a decision the shortest path did not require.
It is also useful before you start, if you let it answer only one narrow question: how long is this ladder? Knowing that a puzzle is short changes how carefully you plan the opening. Knowing it is long changes how willing you are to explore. Neither use spoils the route.
Where the solver hurts is in the middle of a solve. At that point you have a plan, and the solver replaces the plan with the answer instead of improving it. The player learns nothing about the branch they were on, which is the branch that would have taught them something.
My own rule is simple. During a solve, I only take hints. After a solve, I am happy to browse the archive or check the solver and compare routes. If I break the rule and check mid-solve, I write down why, and the reason is usually impatience rather than confusion. That note is the useful part of the mistake.
If you want to see the difference in one session, browse the archive after finishing today's ladder and compare two or three routes in a row. The solver stops looking like a cheat the moment you use it as a compass for the map you already drew.