It’s clearly secondary to correctness: A program that is well-written but doesn’t work right is worthless. Many hairy balls of mud have shipped to great acclaim.
Human readability & comprehension is nice for maintenance, but you don’t get to maintain something that never worked right to begin with.
… Of course, Windows is existence proof that you can be successful with neither.
The point the post makes is that one can’t write (or ensure that) a piece of code is correct without understanding it in the first place.
It’s most important, above these, because you cannot ensure any of these other design goals without understandability. It has to come first
And I agree with that. Correctness is the goal, but making the code readable is the way: it comes first. Cutting corners there is a good way to shoot yourself on the foot.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
It’s clearly secondary to correctness: A program that is well-written but doesn’t work right is worthless. Many hairy balls of mud have shipped to great acclaim.
Human readability & comprehension is nice for maintenance, but you don’t get to maintain something that never worked right to begin with.
… Of course, Windows is existence proof that you can be successful with neither.
The point the post makes is that one can’t write (or ensure that) a piece of code is correct without understanding it in the first place.
And I agree with that. Correctness is the goal, but making the code readable is the way: it comes first. Cutting corners there is a good way to shoot yourself on the foot.
A program that works right but doesn’t solve the problem is also not very useful.