Link Post: The 7 Rules for Writing Software That Won’t Die When You Do
Similarly, it is important to know when you are writing bad software. Here’s a few questions that will help us diagnose if you are writing bad software.
- Does pushing updates to the software take a lot of time and effort?
- Does the whole system go down when you push a very small change?
- Have you ever pushed broken code to production, and didn’t realize until your users started complaining?
- Do you know what exactly to do when your system goes down — how to dig into backups, and deploy them?
- Are you spending more time on things like moving between environments, or running the same commands again and again, or running small utilities than actually making the software?
If you answered yes to any of these questions, this post is for you. Read all the way through, at least twice.
https://medium.com/@karan/the-7-rules-for-writing-software-that-wont-die-when-you-do-38ef0a925650
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
RSS
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows