How to have anxiety in production

A list of things to NOT do in production environment. This list is just for fun. If you do all of these (or even a few of these), I definitely guarantee a lot of anxiety with production environments.

1. Use a single server for all your production. Make sure your database is also running there for good measure. So, if one goes down, it ensures that everything goes down.
2. Never do backups for your database. If database gets corrupted, let it go down forever. We can always create a new database!
3. Do not use Elastic IP - Incase your server instance is down, you can boot up a new server instance and get a new IP address. Just configure the new IP address in the DNS configuration. Let your users wait while they do so! They have to learn to be patient.
4. Do not communicate your internal team members when doing a production deployment. Let your team members guess that a new production deployment has happened.
5. Treat your production instance as just another dev/test instance. And mix your environment variables for good measure. I say, manually copy and paste the new environment variables when you are doing a production deployment.
6. Do not use Github branches. You don’t need that headache. Just use one branch for all your development.
7. Just use WhatsApp for all your communication with team members. Let your team members miss important information. They need to learn to pay attention.
8. Never test your production environment. Just deploy the code and let it run. You can always let your users test for you!

What else do you think should be added to this list? Let me know in the comments below!