Why is it always the setup that takes time, and not the actual programming, when doing projects...

When is this the case?

@j4cobgarby Always

Starting off with a wrong dev tools and then having to change it all midway through development. Costly.

*Give me six hours to cut a tree and I will spend the first four sharpening the axe*

- Abraham Lincoln

Try to use Ruby on Rails. It removes a lot of boilerplate code using convention over configuration.

@math-silva For some reason I've never ever tried Ruby. Though I'm wondering if it's the right time to learn a new language right now. But some time perhaps

@ScriptCoded give it a try when you have some time. It's very easy and fun to learn Ruby.

Once you work with a tool or framework or library enough, setting it up would be easier and faster every time. It's just that the few initial times you'd be slow. After that, you'd develop a system to get it quickly out of the way. I have a few skeleton apps for different setups handy with me. That makes setting up take less than a minute.

Keep working at it. It'll get better :)