Me: I have been doing really similar tasks I'm going to spend some time making a template for it.

Supervisor: ok just don't spend to much time on it we have a lot to do.

Me: shouldn't take too long

1 hour later.

Supervisor : how's the work going.

Me: almost done with the template.

Supervisor: this is taking you way to long I need you to just get back to work.

Me: ok

He leaves and I continue work on the template.

30 mins later.

Show him the template.

Me: I cut my time on this specific task by 80%

Supervisor: good job glad I knew you should do it.

WTF YOU WERE TELLING ME NOT TO.

A nice word to all developers who say stuff like "I know I write bad code, but what does it matter.":
Please try to think in a logical way about what this part you are about to write has to do. It is much more difficult to rewrite code, the longer you wait after you started to code.
Bad code can have big impacts on different levels.
For example financially: Bad coding style or program structure can lead to thousands or much more in losses because of nasty bugs, bad performance, expandability or maintainability.
Think about quality over quantity.

A little example: I had to work together with other coders to meet a fucking tight deadline. The last day we coded like crazy and these dudes started to apply styling changes (CSS) directly as inline styles to the HTML code, instead of taking a few minutes more to find where in the CSS files they had to make the changes.
At the end of the deadline we had more stylingbugs than before. It took us another whopping 3 hours to fix what they had done.

So next time you code: Thinking before coding is mostly faster than just straightahead coding and fixing at the end. 😉