I have to disagree. Writing your own boilerplate can be a great way to learn a new stack, but I think seasoned developers should use (and contribute to) project

I have to disagree. Writing your own boilerplate can be a great way to learn a new stack, but I think seasoned developers should use (and contribute to) projects that are maintained by the community. Whenever I come back to a boilerplate project, they're usually using the most recent versions of libraries, or they have some great new features. Examples: * Rails Composer, for Rails apps: https://github.com/RailsApps/rails-composer https://github.com/RailsApps/rails-composer * Ignite, for React Native: https://github.com/infinitered/ignite https://github.com/infinitered/ignite I do have one hand-written script that I use for all of my static sites. It copies all the static files into a build directory, gzips HTML/CSS/JS, syncs everything to an S3 bucket, then makes an API request to Cloudflare to purge the cache. But I'm planning to move all my static sites to Netlify [1], so I won't need that script for much longer. [1] https://www.netlify.com https://www.netlify.com