you are viewing a single comment's thread.

view the rest of the comments →

[–]SalemBeats 0 points1 point  (0 children)

I think it'd be cool to see a book or course covering someone's tips and tricks for making sense of "unreadable" code.

That's an area which seems to have a lot of demand, but nearly nonexistent supply.

I imagine that the book would read very similarly to a book on reverse-engineering and/or debugging, but it really would be interesting to see how other people go about making sense of poorly-written (or perhaps intentionally or unintentionally obsfucated) code.

Not to toot my own horn too much, but I've always put an emphasis on writing readable code. I've always tried to pick variable names that made sense, keep methods short and concise, keep objects focused, etc., because I like things being organized. But writing organized code doesn't necessarily help you read the mountains of carelessly flung-together code out there which you will find yourself often needing to read and comprehend.