4 ms·
I see value in this article, but it seems to think about code as working in isolation. Snippets. You can see everything. Many times you’re working with librari
by alanfranz 4y ago
I see value in this article, but it seems to think about code as working in isolation. Snippets. You can see everything.
Many times you’re working with libraries or interacting with existing code, where not everything is so clear, the “specification” is fuzzy at most, and how the outcome state is achieved is far from obvious. So, code _can_ happen to you and you then need to dig the why.
- Doctor_Fegg 4y agoI find this particularly with UI frameworks with a large, ever-changing surface. Adobe Flex was absolutely terrible for it. iOS has some of the same issues. Trying to work out why some text has reflowed and bumped down your controls may not technically be "code happening to you", but it sure feels like it.
- lioeters 4y agoI agree with your point. In my experience, code happens to you more often than not because when you run something, most of the code that's running was not written by you. There could be a whole another article titled "Code Happens to You" about debugging other people's code, including dependencies and sometimes even the compiler.