> In the end, all that matters is the business logic...to the user. If you're trying to build a side business and a side project to support that business, you

> In the end, all that matters is the business logic...to the user. If you're trying to build a side business and a side project to support that business, you are 100% correct. If you're trying to build a side project for your own learning, then the user is the developer, the primary interface is the codebase, and all that matters the developer experience. But you should start by understanding what developer experience you are trying to achieve and design from that. Trying to get yourself set up with a good red-green TDD loop? Adding Jenkins from the start is probably a mistake because it won't help you with your local dev environment. However, if you're starting out learning node then getting webpack configured will probably help you. But here too there is a trap: you want to avoid just collecting a list of tools you don't know and trying to assemble them into a dev environment all at once without guidence. I once spent a week trying to do that with gulp and it was nuts. This is one area where talking with someone who is experienced with the language's ecosystem will help you. At best, that person can point you to a recommended setup. The very least, that person can point out that some tool is 2 years old and doesn't play well with the others because it is out of date.