Sometimes we get tips questions from a first-time contributor asking for help golfing a particular piece of code that they wrote. Often these question don't fare so well. Can we do anything here?
There's many ways for these questions to go wrong. A benign one is for answerers to treat it as a standard code golf challenge. Except, it's limited to a single language and often unclear on what the task is exactly, so it would be closed as a normal challenge. The answers are often just "X bytes" and some golfed code without explanation, which isn't really giving tips for the asker.
Another failure mode is the that asker says answers won't work for them because of some unmentioned rule like that the code has to fit in one line or run within two seconds. We have pretty liberal rules about I/O and things that can lead to improvements that the asker can't use. Conversely, they might have allowances we don't know about like free imports.
Finally, a number of these questions seem to just be attempts to cheat at an ongoing outside competition, which leaves a bad taste in my mouth.
I think questions like this are important to handle well. We have users coming in with an existing interest in golfing and drive to improve, and they might stay as long-time productive contributors. How can we make these types of questions work out better?