markdown guide

Every time. Many times copy paste parts of previous projects plus modifications.

Most of the code I write is javascript outside frameworks, thus the need to do the bootstrapping myself.

Btw, it's not irritating it's fun.


To be honest, I don't scaffod a fresh web-app project often.

But I don't, specifically because the setup and configuration burden is one of the most awful I've been able to encounter, killing any motivation to work on some kind of web-based software.


So what do you do when you start a new web project


Tl;dr, since I have every theorical part already defined when times come to start a new project, I go for the solution I feel would make my life easier than others, and if setting it up takes too long (i.e. multiple modules to configure, for example), I just ditch it and go to the next candidate.

When I come to the point where I actually start a new web project, usually because I haven't found a better solution for the need said web project would fulfill, since I tweaked with a few different tools (svelte / vue / angular, different CSS libraries and approaches, etc), I usually take the one I feel the most "up" to fulfill this task, and try to create a project.

If I find something annoying / costly / hard to do, but I notice that it can be done in an easier / more natural / more documented way in another tool, I'll probably just throw the entire project away and start with that other one.

When I come to that point (which I stated earlier), I've usually drafted a rough outline of everything I want as a MVP, everything being UI / UX / logic / features / etc.

Edit: I feel that it's more fair to state that I'm a back-end / system developer, and not an expert in the web world, so my knowledge of the hundreds of tools that may come with any web project bootstrap is very limited.


IMHO this would give us a fixed set of templates and we do lose the fine grained control on what we want and we dont



It might not match what you want/need but you can ask the user to choose options and that is regularly used by template creators to allow fine grained control on output for things like technology options.

Sounds like you already have an idea for something though:)

Yup, will share once I make some progress on it


We were loosing a lot of time creating new Angular Apps at work and sometimes the newly generated app was already out of date when it was made by someone who didnt do his updates. So, I created a CLI App that generates a new project based on the answers of the user.


As a team, we had to do this too often. With every new project, it was getting more frustrating and felt like an utter waste of our time we were spending on configuration rather than solving the actual problems.

This lead us to creating Hix - a setup wizard injected into every new Ruby on Rails project flow.

So if you are thinking for doing something similar - highly recommended.


I've created a boilerplate for myself for this. Every webapp/PWA project needs almost the exact same base. Do you have a better solution maybe?


Not sure, if we can build a universal scaffolder where you just say what library, transpiler only with few config you care and it does all the heavy lifting


I often do that as I haven't yet figured the way out. However, it becomes so irritating and boring due to all of the configurations that might be involved. What is your idea?


Not sure, if we can build a universal scaffolder where you just say what library, transpiler only with few config you care and it does all the heavy lifting

Classic DEV Post from May 3 '19

What do you code to relax?

My projects have me jumping through hoops of a wide variety of technology, talkin...

Ameer Jhan profile image
Speaker, writer and totally into #JavaScript #cloud #devops #microservices 🤩

dev.to now has dark theme. 🌝

Go to the "misc" section of your settings and select night theme

P.S. It's the best move you can make for your dev career.