8

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

Comments
  • 1
    When is this the case?
  • 0
  • 5
    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
  • 1
    Try to use Ruby on Rails. It removes a lot of boilerplate code using convention over configuration.
  • 0
    @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
  • 1
    @ScriptCoded give it a try when you have some time. It's very easy and fun to learn Ruby.
  • 1
    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 :)
Add Comment