News for hackers. Stuff that matters.
Re:If coding is solved, what now?: Measuring the sloppiness ... by softwaredoug on Friday September 11, 2026 @10:19AM (#49658915)
Coding might be "solved" but coding still is the best way to build your own mental model of the solution space.

Which is more important to you: Velocity to a solution? Or velocity to understanding?

Re:If coding is solved, what now?: Measuring the sloppiness ... by nucleative on Friday September 11, 2026 @10:54AM (#49659545)
Interesting way to lay it out. For us understanding is obviously crucial for prod and repeatable business functions.

Velocity to solution is default for almost everyone else, especially one-off or low impact / low consequence of failure projects.

Re:If coding is solved, what now?: Measuring the sloppiness ... by timbaboon on Friday September 11, 2026 @11:34AM (#49660190)
Velocity to solution is default for senior management, that's for sure ;)
Re:If coding is solved, what now?: Measuring the sloppiness ... by hax0ron3 on Friday September 11, 2026 @11:31AM (#49660138)
I code to make money, and the kind of stuff I work on doesn't kill people or lose massive amounts of money if it has bugs, so to me velocity to a solution is much more important than velocity to understanding.
Re:If coding is solved, what now?: Measuring the sloppiness ... by greenowl on Friday September 11, 2026 @09:50PM (#49667844)
Velocity to a paycheck