Top 10 hacks to be a Bad developer
Top 10 hacks to be a BAD developer
- Code first, design later.
- If people can't understand your code, they are not smart enough
- Never write unit tests and when you are forced to write them, write short and easy ones
- The only job of test coverage is to please engineering managers
- Take all suggestions in code reviews personally
- Always avoid documentation. Only work on it long after your project is complete.
- Logging, Metrics & Alerts are just there to add more story points. Your code is always reliable.
- Just get things to work once and push them to production quickly. Never actively monitor your changes in production.
- Don't read software documentation, only rely on internet blogs
- Never think about the end user, you are an engineer not a product freak
Of course, above is meant for what you should not do at you job.
Credits : Shivam Gupta