## Pro tip

Best answer to any *general* [tag:tips] question. That is, candidates should be drawn from "Tips for golfing in X" questions (as opposed to specific "how do I shorten this piece of code" questions).

Some of the most useful content that we generate for other golfers is in our tips questions, so it would be nice to reward an exceptional golfing trick this way.

Candidates should be tips which show deep insight into the language, yet are applicable in wide range of situations. The exact amounts of bytes saved by the tip is not relevant.

##[Tips for Golfing in Brain-Flak](https://codegolf.stackexchange.com/a/109859/51785) by [Heeby Jeeby Man](https://codegolf.stackexchange.com/users/56656/heeby-jeeby-man)
**Nominated by Poke**

Brain-Flak only has two stacks on which to perform operations. The third stack is always present but not always made use of. The concept and application of the third stack is widely used when golfing brain-flak code as it allows for implicit re-use of certain values so they do not need to be computed again later. This can easily be seen in the [Hello World answer written in brain-flak](https://codegolf.stackexchange.com/a/92975/51785)

## [How on earth did llhuii output the Evil Numbers in 42 bytes of Python?](https://codegolf.stackexchange.com/a/144075) by [Dennis](https://codegolf.stackexchange.com/users/12012/dennis)

**Nominated by Ian Gödel**

A community effort to tie another user's submission from Anarchy Golf has turned into a great brain-storming, ending up at a staggering 39 bytes, beating the target solution by 3 bytes. Congratulations to all who participated, but the last answer has beaten them all, involving a lot of ingenuity and bit-fiddling!