What does everyone use / do to help make the debugging process faster ?
-
-
In short, all tounges lead to lisp.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
+1. The biggest level-ups in my career have been: Leveraging good type systems Property checking Writing pure functions, then testing the hell out of 'em. Whenever possible, make algebra do the tricky bits for you.
-
Hey Adam, can you expand a bit on what you mean by good type systems? And any material you advise (beyond practise) to get good at these? Self-teaching myself programming so this type of knowledge is golden. Thanks!
- Show replies
New conversation -
-
-
Thanks!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Debugging an existing system: do a mental diff between broken state & last known good state. Helps isolate the bug
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This!!! The clutter folks pack into code in a bid to have it look cool
. Code should be functional not cool.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
And use TDD
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
every line of code is a potential bug
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"Write purely functional code whenever possible" is extremely difficult to do. Most developers don't understand how to achieve this.
-
I thought this was true until I picked languages and approaches that helped/enforced this. Using LISP(ish) languages like Clojure(script) accelerated everything and defect rates dropped (after a short learning curve). We learn things like object orientation too (unlearn first).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.