Subtle interactions in the embedded world - what bugs can teach us
Subtle interactions in the embedded world - what bugs can teach us
Posted Feb 24, 2012 2:54 UTC (Fri) by mhelsley (guest, #11324)Parent article: Subtle interactions in the embedded world - what bugs can teach us
The great thing about this method is I've already got context for this portion of the code without even reading it. I've used this code and know what behavior it produces (bug or not) -- often I even know enought about the data to help recognize variables and/or guess the likely control flow I care about. In fact, I suspect that adding a small feature is usually an easier route to start with the project's code. The problem is a small feature will not force me to gain a very deep understanding of the code like a difficult bug would -- so this is where it's critical to know my personal learning style and what I hope to get out of the experience (if anything more than an easy fix or small feature).
In contrast, without this context selecting a feature or fishing a bug out of bugzilla to get a cold read relies heavily on technical experience and conjecture to help me rapidly acquire context. For me hands-on experience with a project -- even non-technical hands-on experience -- really counts.
Of course this is also much harder if we're talking about code that's in lower layers of the "stack" (as with the kernel here). Those layers can often be reached with this method, a good packaging system (e.g. apt or yum on top of rpm or dpkg), and much patience.
