Public Notes

Recent Activity

  • Kenrick shared from The Clean Coder: A Code of Conduct for Professional Programmers (Robert C. Martin Series) by Robert C. Martin
    We can avoid pressure by keeping our systems, our code, and our design as clean as possible. This does not mean that we spend endless hours polishing code. It simply means that we don’t tolerate messes. We know that messes will slow us down, causing us to miss dates and break commitments. So we do the best work we can and keep our output as clean as we can.
  • Kenrick shared from The Clean Coder: A Code of Conduct for Professional Programmers (Robert C. Martin Series) by Robert C. Martin
    I was the development manager telling the programmers who worked for me that they had to work more and faster. I was one of the 80-hour guys, writing 3,000-line C functions at 2 AM while my children slept at home without their father in the house. I was the one who threw the pens and shouted. I got people fired if they didn’t shape up. It was awful. I was awful. Then came the day when my wife forced me to take a good long look in the mirror. I didn’t like what I saw. She told me I just wasn’t very nice to be around. I had to agree. But I didn’t like it, so I stormed out of the house in...
  • Kenrick shared from Starting Strength by Mark Rippetoe
    At this point, you will see the whole purpose of this exercise: the bar is now heavier, so what do you have to do? You jump harder. This is why we clean.
  • Kenrick shared from a Personal Document
    Joe Armstrong, Erlang’s creator, compares the equals sign in Erlang to that used in algebra. When you write the equation x = a + 1, you are not assigning the value of a + 1 to x. Instead you’re simply asserting that the expressions x and a + 1 have the same value. If you know the value of x, you can work out the value of a, and vice versa. His point is that you had to unlearn the algebraic meaning of = when you first came across assignment in imperative programming languages. Now’s the time to un-unlearn it.
    Note: Erlang and Elixir are awesome!
  • Kenrick shared from The Rails 4 Way (3rd Edition) (Addison-Wesley Professional Ruby Series) by Obie Fernandez, Kevin Faustino
    For those interested in REST, the canonical text is Roy Fielding’s dissertation, which you can find at In particular, you’ll probably want to focus on chapters 5 and 6 of the dissertation, which cover REST and its relation to HTTP. You’ll also find an enormous amount of information—and links to more—on the REST wiki at
    Note: Reminder to self: here's some fun, recreational reading to really understand REST