Hacker News new | ask | show | jobs
by BinaryIdiot 4068 days ago
> I can trace the code all the way down to the kernel.

Maybe you can but do you? This requires not only figuring out how to compile your ENTIRE stack but also doing it AND figuring out how to debug each piece (since generic debugging tools are not the best). I understand there may be major issues that require this level of insanity but the rarity is so incredibly high and so few have enough domain knowledge to do it effectively that I don't buy this argument at all.
2 comments
scott00 4068 days ago
There's a level of understanding and debugging possible from reading the source without compiling/debugging that's not possible with access only to binaries. I'm a .NET/Windows developer mostly, and I've found myself consulting the .NET library reference source dozens of times over the past year. This has been useful, despite the fact I've never compiled it. Five years ago I would never have thought my work would require that level of understanding. You may be surprised how fast you can find yourself in areas where the internet doesn't provide ready answers when you start working on unusual stuff. You may also be surprised how fast you can figure out code that once seemed impenetrable when it's the next logical step in fixing an issue you desperately want solved.
link
BinaryIdiot 4068 days ago
> There's a level of understanding and debugging possible from reading the source without compiling/debugging that's not possible with access only to binaries. I'm a .NET/Windows developer mostly,[...]

I certainly agree with you but the claims of tracing the flow of execution down to the kernel? That's extreme in my opinion. Obviously there are times that's useful but for the majority of developers I can't imagine that's even as frequent as a rare occurrence. At least in my personal experience I only know maybe 2 people in my past experience who could actually do this. I just don't think the majority of developers know how to step outside of a few frameworks or languages.

At least Microsoft released the debug symbols for .Net back in 2012 so you've been able to at least trace through your framework's source for a while now :)

link
devicenull 4068 days ago
Yes, I have to do this maybe a couple times a year (tracking down weird KVM bugs, or figuring out poorly documented features)
link