I can understand how boilerplating can e a bummer when starting a project. I do, however, keep it as a step 0 in every project rather than keeping a skeleton (though I do involve a lot of copy/pasting from previous works).
You know... Stuff goes on, one learns new things with this and that project and, in the end, in the next project we set up, I like to think my boilerplating has somehow a bunch of new stuff, like other scripts, dependencies I hadn't been using and now find useful (not depending on the project), etc.
Thanks for your comment! I agree that the boilerplate will change with the real project, and really it's perfectly okay to put together the boilerplate for the actual project right from the start.
I've found that it can be helpful, especially when using a technology for the first time, to use a starter project, but it isn't absolutely necessary. For me it's kind of a way to do "self-hacking": Knowing that I will need to clone the repo helps to motivate me to automate things. I think in general that's a good goal to have for a project - to have the fewest possible manual steps required to get a clean repo installed and running.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can understand how boilerplating can e a bummer when starting a project. I do, however, keep it as a step 0 in every project rather than keeping a skeleton (though I do involve a lot of copy/pasting from previous works).
You know... Stuff goes on, one learns new things with this and that project and, in the end, in the next project we set up, I like to think my boilerplating has somehow a bunch of new stuff, like other scripts, dependencies I hadn't been using and now find useful (not depending on the project), etc.
Thanks for your comment! I agree that the boilerplate will change with the real project, and really it's perfectly okay to put together the boilerplate for the actual project right from the start.
I've found that it can be helpful, especially when using a technology for the first time, to use a starter project, but it isn't absolutely necessary. For me it's kind of a way to do "self-hacking": Knowing that I will need to clone the repo helps to motivate me to automate things. I think in general that's a good goal to have for a project - to have the fewest possible manual steps required to get a clean repo installed and running.