5 ms·

Oh, it is the same for programmers! As soon as we have an idea we immediately open up an IDE, and then get a GIT repository going, and get Yarn to prepare all

Oh, it is the same for programmers! As soon as we have an idea we immediately open up an IDE, and then get a GIT repository going, and get Yarn to prepare all the libraries we need, and get a quick little back end database api set up, and then a quick little front end framework and then we are... finally ready to start experimenting.

eropple 8y ago
You can, for the most part, do that once and never again, though. `cp -R` is a thing.
- imhoguy 8y ago
  Not in "modern" web dev where a cool lib/tool/stack released today gets deprecated or not-cool tomorrow ;)
  - eropple 8y ago
    I've been using the same modern dev stack for HTML5/JS for two years now. I've been using permutations on the same dev stack for backend stuff for--well, before I wrote a new one[1], about five years. This sort of middlebrow thing isn't good or helpful. [1] - https://github.com/modern-project/modern-ruby https://github.com/modern-project/modern-ruby
- Drdrdrq 8y ago
  I find setting up the environment a nice warm up routine that I wouldn't want to skip. Also, it takes just a few minutes, which is probably less than searching for that "template project" that I prepared those weeks / months ago. I guess everyone has their own creative process... :)
- 1wheel 8y ago
  I highly recommend setting something like this up. So nice to type a command and be ready to start sketching 3s later. Mine: ` alias initblock='function __initblock() { mkdir $1 && cd $1 && degit 1wheel/d3-init && gistup -m $1 --private --no-open && subl . && hot-server; unset -f __initblock; }; __initblock' ` https://github.com/1wheel/d3-init https://github.com/1wheel/d3-init
- mindcrime 8y ago
  or git clone https://github.com/myaccount/proj_template.git newproj
  - deleted 8y ago
    [deleted]