Underappreciated strategy for debugging a complex system: repeatedly strip away complexity, until you are left with either a working system or a minimal reproduction of your bug. Simple on paper, but it's often the opposite of what will most appeal to your pride as an engineer.

Mar 22, 2022 · 8:08 PM UTC

13
37
5
241
Replying to @gdb
Like @elonmusk says, "Sometimes the best part is no part."
1
Replying to @gdb
so true, similar to `git bisect` to find when a bug was introduced—never fails but feels unsatisfyingly like looking up a puzzle solution in the answer key. Also heard it called Ablation or Lobotomy Debugging neil.fraser.name/news/2015/1…
Replying to @gdb
Also works while working on building a system for a complicate problem. Baselines first, and slowly add complexity based on experimental results and hypothesis
Replying to @gdb
Bro, you speak my language. MVP. so gooood
1
Replying to @gdb
I hear backtracking questions are popular in interviews...
1
Replying to @gdb
Pray that the complex system was designed in a way that allows this
Replying to @gdb
Debugging is an under appreciated art
Replying to @gdb
Strange contradiction. Rendering an mvce reproduction of a complex system is the perfect distillation of what engineering is. What it appeals to least is the programmer in us, the way getting the dishwasher in the right place doesn't appeal to the architect in a structural eng.
Replying to @gdb
A thousand percent agree!🔥 Writing a minimal version of your problematic code is the easiest way to solve the🐞.
1
Replying to @gdb
Maybe the only way.
2
Load more