News for hackers. Stuff that matters.
Re:Why Isn't Debugging Treated as a First-Class Activity? by dsfyu404ed on Wednesday July 11, 2018 @09:21AM (#17506610)
>Programming is not a write-only operation

A lot of people would take issue with that statement.

Most devs probably wouldn't notice that their backspace key went missing until they were fine tuning the phrasing of an email about why the best way to solve their spaghetti is to make the same spaghetti slingers port the codebase to $FAD_OF_THE_WEEK.

Edit: It should be obvious that this is a joke but if it's not you should probably check if your backspace key still works.

Re:Why Isn't Debugging Treated as a First-Class Activity? by commandlinefan on Wednesday July 11, 2018 @11:18AM (#17507575)
> check if your backspace key still works.

Back in the late 90's, when Java was still sort of new, my employer insisted that I install an IDE to do my Java development that I had been doing mostly in vi. The one they picked (for some reason) was Symantec's Visual Cafe. I found that I could reliably, reproducibly, crash the IDE by pressing the backspace key. Maybe that was their way of pushing a "no mistakes" philosophy?

Re:Why Isn't Debugging Treated as a First-Class Activity? by hinkley on Wednesday July 11, 2018 @11:10PM (#17511909)
In that era no IDE ran stable across its whole feature set. Crashing debuggers were very common. VisualAge had the most stable debugger but would crash just typing in code.

Jetbrains was the first one that was reliable. Slow, but not as slow as VA.

Re:Why Isn't Debugging Treated as a First-Class Activity? by aplummer on Wednesday July 11, 2018 @09:39AM (#17506724)
I think you’re wrong about most (seniorish) developers but I loved the way you said it haha.
Re:Why Isn't Debugging Treated as a First-Class Activity? by bennylope on Wednesday July 11, 2018 @10:21AM (#17507123)
Maybe they're just deleting code in command mode...