Have you ever received a task in the format 'here is the goal — here is the result, how to do it — no difference'?

Yes, such a situation has occurred. It is when a task is formulated through the end result or goal, and the method of solution is left to the discretion of the performer.

In such cases, it is important to:

• Clearly understand the requirements and success criteria.
• Independently design the architecture and choose the tools.
• Justify the chosen approach and be prepared to discuss alternatives.

For example, in a Go project, I was given the task "to ensure high performance and stability of the service," without instructions on how to do it. Then I analyzed bottlenecks, selected suitable patterns and optimizations, and then demonstrated the results.