|
You don't merge from the boilerplate. Once you've started, that's it. Boilerplates exist because, quite honestly, modern web/JS development is a hot mess. First, setting up a new project is the definition of analysis paralysis -- too many options and microdecisions. Second, there's a new library or a new, breaking update to your existing framework every other week. When you're busy actually working on a project, it's hard (and useless) to keep up with all the changes. So if you work on something for, say, 2 months, the next time you need to start something new, it's likely you'll have to spend some time updating your own project base and making sure dependencies work the way they're supposed to. Things will probably have changed in unclear ways. Unless you're reusing a stack that might be out of date/not maintained anymore, the time from "start project" to "start actually coding" when starting a new web project is terrible. Having a boilerplate to start from relieves you of all that stress, since you know it's more or less maintained and guaranteed to work out of the box. A few years ago I'd never have started from boilerplates. I'd look up examples for certain patterns, but always start from scratch, many times reusing some of my own stuff. Nowadays, my approach is the opposite: I take a boilerplate with the combination of things I need, and change it a bit, adding or removing things here and there. |