# \[Suggestion/FR\] Projucer Templates **URL:** \ **Category:** The Projucer\ **Created:** [February 7, 2018, 10:03am UTC](https://forum.juce.com/t/suggestion-fr-projucer-templates/26293 "2018-02-07T10:03:45Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![ttg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ttg/32/14456_2.png) [@ttg](https://forum.juce.com/u/ttg)\ **Post date:** [February 7, 2018, 10:03am UTC](https://forum.juce.com/t/suggestion-fr-projucer-templates/26293/1 "2018-02-07T10:03:46Z")
A few weeks ago I saw this thread: > [@\#1 most common programming mistake that we see on the forum](https://forum.juce.com/t/1-most-common-programming-mistake-that-we-see-on-the-forum/26013): > > This post is here so that we have something we can link to when this same issue comes up, because the JUCE team is getting very bored of spending time replying again and again to the same damned problem! This isn’t a JUCE bug - there’s nothing we can do in our codebase that would stop people making it, which makes it painful for us to watch beginner after beginner come along and fall headfirst into the same trap! It’s also understandable that people will post a new topic when they hit it, beca… One interesting discussions was regarding boiler-plate code. I guess especially for plug-ins each developer/company got its own boiler-plate needed to be add. It would be nice to have the ability to create “custom” templates. - That way non-newbies could remove a lot of first-timers helpful comments. - Set default modules. What happens if JUCE change / deprecate something? It will break. but since the templates are the user responsibility that’s expected. just as ButtonListener was gone… code is always changing and breaking. 🙂