Software Development Workflow: the long walk
Hey, its Ricardo again 👋. Don’t miss out on the latest articles! Subscribe to the newsletter today or hit the clap button. Really appreciate it. Stay tuned for more.
Throughout my years of experiences, I had the pleasure to contribute to different kinds of projects: solid products with already a development workflow in place, projects in which CI/CD was not prioritised due to time constraints, products in which software development was still on a very early stage, you name it. Different levels of maturity, different complexity of development workflows. Can you relate it?
Gathering all experience from those projects, I could get an idea of which actions could potentially be used on products that are giving the very first steps. My main goal is to give a source of inspiration on products that you are developing or contributing to. Of course, the perfect development workflow for me will most probably not be the best for you. Different use cases suggest different actions. So, bear with me and embrace this (long) walk with me 🤓
- Why linting?
- First custom eslint rule
- Testing: From 0 to ∞
- TDD on serverless
- Documentation: the burden
- Schema validation
- Leverage your code security
Feel free to pop out any comments about different, and perhaps more sophisticated actions. Lets build the perfect development workflow together.
Nonetheless, stay tuned for more 🙏.
