Writing

Posted 5 minutes ago · 42,363 reads

Legacy code is called legacy for a reason. It works. It's been tested in production. It's often the most reliable code in your system, even if it doesn't follow modern conventions.

Legacy code is called legacy for a reason. It works. It's been tested in production. It's often the most reliable code in your system, even if it doesn't follow modern conventions.

Know your tools deeply.

Code reviews are less about finding bugs and more about ensuring that the team understands why a decision was made. The review is a conversation, not a gate.

Type systems don't prevent bugs—they just catch certain categories of bugs earlier. The real benefit is the documentation they provide about what a function is supposed to do.

APIs are contracts. Once you publish one, changing it becomes expensive for everyone who depends on it. The cost of breaking changes compounds over time, which is why the boring, conservative choice is usually the right one.

Code reviews are less about finding bugs and more about ensuring that the team understands why a decision was made. The review is a conversation, not a gate.

Related

More on this topic

Type systems don't prevent bugs—they just catch certain categories of bugs earlier. The real benefit is the documentation they provide about what a function is supposed to do.

Your future self will thank you.

Code reviews are less about finding bugs and more about ensuring that the team understands why a decision was made. The review is a conversation, not a gate.