Balance Programming

Tag: books

  • The Law of Demeter

    I’ve been doing some more reading and came across the Law of Demeter and train wrecks again. The last time while while reading Clean Code. I’ve one book that tells me this is bad practice: And that I should do this instead: My feeling was to prefer the first as more compact here and it…

  • The Checklist Manifesto

    The Checklist Manifesto is a book from 2010 by author Atual Gawande, an American surgeon and public health researcher. I read it a while ago and it reinforces my belief that we all make mistakes. Unsurprisingly the book is all about checklists. It may not sound like much it can be a great help in…

  • Design Patterns

    Reviewing Game Programming Patterns inspired me to read the classic Design Patterns, Elements of Reusable Object-Oriented Software. My guess going in was that it would be more complete but not as nice to read, that’s pretty much how it was. However there were some unique patterns in each book so, if you like patterns, it…

  • Functional Programming in C++

    I remember functional programming being a niche aspect of computing science. Software engineering didn’t consider it at all. Now you can find discussion and books about using it in any major programming language. I read Functional Programming in C# but, to me, this oversold the technique while it lacking practical advice for day to day…

  • Rust

    I heard about Rust’s unusual approach to memory management and thought have a look. Programming Rust from O’Reilly is chunky at about 700 pages and has taken a while to get through but does seem to cover all the bases. I’ve not gone as far as coding in this language so this will just be…

  • Apples vs oranges

    In some of my recent reading I’ve been frustrated at authors making poor comparisons. The typical behaviour is to showcase an example of good coding with their preferred language / methodology against an example of bad coding with the competitor. It’s not, say, the language which is making the difference. It’s whether the code has…

  • Game Programming Patterns

    I wanted to cleanse my palette and decided to read Game Programming Patterns by Robert Nystrom. I’ve read it before so I knew what to expect. It’s a clearly written pattern book with simple example situation taken from the games industry. Don’t expect to get all the patterns here or advanced game programming knowledge. However…

  • Data-oriented design

    I read Data-Oriented Design by Richard Fabian but will mostly cover the methodology (DoD) not the book. Let’s get it out of the way and I’ll try not to belabour it: It’s about all the data Data-oriented design concentrates on the underlying data in any given system. Data tends to be stored in a very…

  • Less can be more

    I was listening to the podcast series Cautionary Tales and their episode Do nothing, Then Do Less. By all means listen to the whole thing but I’d like to highlight the crossover with The Happiness Lab starting 12 minutes 30 in. Bias for adding People are apparently biased towards adding things in order to solve…

  • Clean Code

    I’ve heard of some people following the Clean Code methodology and some people reacting against it. It’s not been on my reading list before so I got hold of Clean Code by Robert C. Martin. I think it has some good ideas and a few bad ideas. My biggest problem is that these are often…