How to design a poor system

There could be multiple ways to achieve this

1. start development and define specs later
2. be inconsistent with database schema design
3. have complex initialization program
4. unable to test individual component
5. be in hurry to complete a task without knowing this consequences
6. miss deleted_at column in db and use hard delete instead
7. do not optimize read and write
8. between services , use synchronous calls using http and wait for response to come. so fastest http client could not help
9. do not show interest in adoptation of best practices, instead go for quick temporaru solution without making full plan
10. go for product and services launches without doing basis minimum optimization
11. Very complex initialization chain with complex dependencies which can be initialized quickly

If you make your services hell, then other will have chance to grow using your mistake.

There are 1000’s of bad practice and we can not eliminate. This is better to be aligned on day 1. Once you start development with good plan and have flexibility , it will be automatically adjusted to upcoming need.

Example of bad practices and resolution with better one will be continued .