Jonathan Bennett

What makes code “good”?

So if working code isn’t the goal—what is?

Here’s my take:

  1. Does it solve today’s problem?
  2. Can it be adapted to tomorrow’s problem?

If your code checks both boxes, congrats—it’s good. Maybe not perfect. Maybe the test suite is thin. Maybe cyclomatic complexity is creeping up. Those are potential problems for future-you, sure—but not dealbreakers today.

The code doesn’t need to be pretty, it needs to be practical. Solve the problem. Don’t block future progress. That’s enough.