News for hackers. Stuff that matters.
Re:Write code that is easy to delete, not easy to extend by lmm on Sunday February 14, 2016 @02:12PM (#11099543)
> Consider the task of debugging any arbitrary error where you have little more than a line number to go by. You now need to refactor the line just to find out which method invocation is causing the error.

That's a tooling issue. The right thing is to enhance the stack trace to give more than a line number, and the debugger to allow a more specific breakpoint.

> There are also readability issues with lines like these.

Maybe, but the biggest readability issue by far is when a class or function spills beyond a single screen. Avoiding that is worth a lot of cramped lines.

Re:Write code that is easy to delete, not easy to extend by mathgeek on Sunday February 14, 2016 @02:18PM (#11099560)
At this point this is boiling down a subjective argument on readability and tradeoffs in tooling, so no point in continuing. Have a great day!