all lines of code should be covered by a test or explicitly excluded from test coverage.
How did Uber go from a 450,000 lines monolithic Python application to more than 1,000 microservices?
Untargeted feedback. Things you can't impact. Things you didn't do. Unspecific feedback. Only positives. The feedback sandwich.
Taking inspiration from Dieter Rams' ten principles for good design, here are the ten principles of good code.
Maslow's pyramid can help us think about what great code reviews look like.
Grow the team. Maintain a vision. Manage projects. Organize. Code.
It's demanding. Empathy is required. You should keep coding. It's easy to make a difference. You can and should disconnect. You will grow through mentoring and feedback. It's incredibly rewarding.
Let's take pride in our software engineering craft.
A list of resources to learn programming.
An engineer's job is not to write code - it is to solve business problems.
How to visualize your code's profile with qcachegrind.
Why taking the time to learn Vim is a smart investment.
Some quotable quotes about functional specs.