Code reviews are part of almost all development workflows. How you write them, read them, and respond to them says a lot about a team’s culture. It’s also a way to adjust a team’s culture. How you use them is up to you.
Don’t just review it, review it BEFORE you show it to anyone. It’s good for you, it’s good for them, and it’s good for your code.
Where you are influences not just what you see, but how you see it.
When you say you want quality software, what are you really asking for, and how can you get it?
You can write bad code in any language. You can write good code in any language. The choice is yours.
Why do students pass or fail tests, but software tests pass or fail?
Perhaps oddly, perhaps not, the traits of an effective software engineer have nothing to do with software
You can rubber duck too much, but please, take a moment to think about the problem before you give up trying.
We aspire to uncouple with clear boundaries, but we need to work together