4 ms·
My mise en place is very similar to the authors - set up whatever I need to get fast and clear feedback before anything. If it’s a web service, set up a hello
by sudhirj 4y ago
My mise en place is very similar to the authors - set up whatever I need to get fast and clear feedback before anything.
If it’s a web service, set up a hello world / health check to auto-deploy with migrations if applicable, after automatically running the build.
If it’s a library, set up a build and CI, and any version bumping and release scripts, docs autogeneration.
Basically set yourself up for success and handle a lot of the non-project related heavy lifting. That makes a great foundation off which to launch and iterate quickly.
- makapuf 4y agoI also when I setup an api like to create a zero API (with hardcoded answers) and deploy it to production if possible. That makes sure that flows are opened, everyone is clear with ci, ... then code the tests and the functions. That may raise earlier integration issues that will happen.
- bstpierre 4y agoSimilarly, I sometimes generate dummy output up front. It’s especially handy when multiple teams are going to be processing some pipeline.