this post was submitted on 25 Nov 2023
41 points (95.6% liked)
Programming
16781 readers
106 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not OP, but I'm thinking about the example in vs code: https://code.visualstudio.com/docs/editor/userdefinedsnippets
Some boilerplate code for libraries and frameworks I constantly use.
I'd be more interested in syncing the VS code snippets as they are automatically available in a file for each language and have the autocomplete stops.
If a library or framework requires boilerplate code it's a bad library or a bad framework.
I think this take is uneducated and can only come from a place of inexperience. There's plenty of usecases that naturally lead to boilerplate code, such as initialization/termination, setting up/tearing down, configuration, etc. This is not a code smell, it's just the natural reflection of having to integrate third-party code into your projects.
It depends how much boilerplate you need - there's obviously some stuff that needs to be the same all over but if there's significant amounts of code you constantly need to replicate that's when it's a code smell for me. I probably could've been more precise in my initial statement.
Yes, in my experience, boilerplate typically comes into play when you're using two libraries that don't know about one another, or have no business touching each other's concerns. (Using Alpine's
x-cloak
with Tailwind comes to mind.)That and every single
*-pipelines.yaml
CI/CD config I've ever written.