Low-level design 0/39

Low-level design

Design principles

Information hiding, small interfaces, simple over easy and making invalid states unrepresentable. These are the reasons an interviewer gives when they prefer one class layout to another.

0 / 9 solved

Reading

WhiteBox lessons3

Papers and essays3

  1. On the Criteria To Be Used in Decomposing Systems into Modules(opens in a new tab)

    Parnas 1972 Communications of the ACM 30 min

    Information hiding: start from the design decisions that are difficult or likely to change, and give each module one of them to hide, instead of making each step of a flowchart a module. Two decompositions of the same keyword-in-context (KWIC) index program show the difference.

  2. No Silver Bullet: Essence and Accidents of Software Engineering(opens in a new tab)

    Brooks 1987 IEEE Computer 45 min

    Brooks separates the essential difficulty of software, which comes from the problem a program must solve, from the accidental difficulty of expressing it with current tools. Because high-level languages and time-sharing had already removed much of the accidental part, he argues that no single technique would improve productivity tenfold within a decade.

  3. Write code that is easy to delete, not easy to extend(opens in a new tab)

    tef 2016 Essay 25 min

    An essay on arranging code so parts can be thrown away cheaply, told as a sequence of steps that starts with writing no code and copying code before turning it into a library, and ends with separating the parts that change often from the parts that rarely change, with an easy-to-use layer over an easy-to-extend one.

Videos8

Classic Talks on Software Design Various speakers 8 videos