Clean Code Developer
Today, I replaced the red Clean Code Developer bracelet the orange bracelet. To admit, I once had to switch the red bracelet from the right arm to the left because I was unable to fully make a root cause analysis: We, some friends and I, have a Linux server that is connected to a ZyWall2 plus router. The router itself is connect in bridge-mode to a DSL modem. That also means, the router sends DNS requests to the modem and gets the answers from the ISP. With that configuration we were able to nslookup domain names but failed using telnet or other network services; the resolution always failed with the message “temporary unavailable.” After two days of Internet research we gave up and hard-coded a public name-server address in the ifcfg-eth0 file.
The new principles of the orange bracelet are:
- One level of abstraction per method
- Single responsibility principle (there should never be more than one reason to change a class)
- Separation of concerns (overlap of functionality between classes should be as little as possible)
- Coding conventions (Checkstyle ftw!)
- Use issue tracking
- Create automated integration tests
- Read, read, read
- Review
