Discussion
Honestly, if you have to write a lot of boilerplate code, it's most likely because your design isn't right yet.
I been tellin' geeks for three decades that they don't have to live like this.
"It is this way because we are building it this way. If we want it to be a different way, we have to build it a different way."
Or, put a little more succinctly: "You don't work for the code, the code works for you."
Something that I would love to see is a set of canonical simple projects that you can take and then modify. Just a "if you want to use this tech stack then here is the best way to start out"
Some languages have them but for a lot it's heavily volunteer based and hit or miss based on the language's community.
@GeePawHill I always look at what the purpose is of that boilerplate code, and give it a name. Then my other code can defer to it to accomplish that functionality.
Install bonfire.cafe
Get the full app experience
