As a consultant, and as a developer, one of the most useful things you can do is to take a step back. If someone asks you a question about a detail of a solution they are working on, it's often worth finding out what problem they were originally trying to solve.

For example, if someone asks you for tips on how to bang a nail in with a shoe, the best response is not to demonstrate an effective arm-action for swinging the shoe. The best response is to find out what they actually want: They want the nail to be in the wood. So, they should get a hammer and solve the easier problem of banging a nail in with a hammer. 

They might not have even known that hammers exist. As an experienced consultant/developer, that is the kind of thing that you do know. It's where you can add value over a mere implementer. It's what is known as the X Y problem and is always worth keeping in mind.