1. 16
  1.  

  2. 7

    For me, “Refactoring” was the best book I ever read, more because of the time I read it at then the actual applicability of the content to what I did back then (study). It showed me that code is nothing static. It is written. And then rewritten. Changed for new needs. It’s a rather flexible thing.

    I would like to add two texts that helped me a lot:

    1. Static Typing where possible, dynamic when needed

    https://www.ics.uci.edu/~lopes/teaching/inf212W12/readings/rdl04meijer.pdf

    I like how it deconstructs a lot of simple arguments that are often thrown around in programming language discussions (e.g. the point that most languages do support constructs similar to eval, which is said to be evil). The text isn’t perfect, but it gave me a lot of feel for programming language discussions.

    1. Fielding’s dissertation on REST

    http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

    Less because of REST being an important architectural style for a while, but because of the way he describes his thinking when constructing REST as a set of voluntary constraints to enable reasoning about the system. It still is the definition of architecture for me: voluntary restraint to enable reasoning.

    I’m very sad how often REST is used without reading up on this very understandable piece of thought.

    The best parts: http://www.ics.uci.edu/~fielding/pubs/dissertation/software_arch.htm http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1

    An architectural style is a coordinated set of architectural constraints that restricts the roles/features of architectural elements and the allowed relationships among those elements within any architecture that conforms to that style.

    (The markdown parser has a bug: in the source, the items are numbered correctly with 1 and 2)