How I write back ends

Re:How I write back ends by williamdclt on Wednesday January 22, 2020 @07:18AM (#22116869)

Using templates, boilerplates and generators.

Creating a new project is simply "make generate" from our generator, then answering a bunch of questions about what tech stack you need. This works mostly with templating (using Plop) and a sprinkle of automation for shell tasks (eg `pipenv install`)

[ Parent | on HN ]

Re:How I write back ends by say_it_as_it_is on Wednesday January 22, 2020 @07:31AM (#22116932)

Thanks for clarifying. What used to take 4 days to set up a new server can now be done in <1hr. How often is that being taken advantage of? "Any time we need a new server" is determined by a policy determining whether to bolt onto additional servers or not. Curious about that policy..

[ Parent | on HN ]

Re:How I write back ends by jwdunne on Wednesday January 22, 2020 @05:13PM (#22122630)

Is your generator hand rolled or do you use something in particular? We’re working towards a similar solution where we want to layer/compose different tech choices based on what’s mandated by project requirements!

[ Parent | on HN ]