Public Notes


Recent Activity

  • Sean shared from 21st Century C: C Tips from the New School by Ben Klemens
    The manual type involves malloc and free, and is where most of your segfaults happen. This memory model is why Jesus weeps when he has to code in C.
  • Sean shared from Consider Phlebas (Culture) by Iain M. Banks
    It was the Culture’s fault. It considered itself too civilized and sophisticated to hate its enemies; instead it tried to understand them and their motives, so that it could out-think them and so that, when it won, it would treat them in a way which ensured they would not become enemies again. The idea was fine as long as you didn’t get too close, but once you had spent some time with your opponents, such empathy could turn against you. There was a sort of detached, non-human aggression required to go along with such mobilized compassion, and Balveda could feel it slipping away from her.
  • Sean shared from Consider Phlebas (Culture) by Iain M. Banks
    “Empathize with stupidity and you’re halfway to thinking like an idiot,”
    Note: The power of empathy.
  • Sean shared from Why Programs Fail: A Guide to Systematic Debugging by Andreas Zeller
    Test cases make problem reports obsolete. If a problem occurs during development, do not enter it into the problem-tracking system. Instead, write a test case that exposes the problem.
    Note: Interesting approach. Express bugs-found-in-devo as test cases.
  • Sean shared from Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin
    When Kent showed me the code, I was struck by how small all the functions were. I was used to functions in Swing programs that took up miles of vertical space. Every function in this program was just two, or three, or four lines long. Each was transparently obvious. Each told a story. And each led you to the next in a compelling order. That’s how short your functions should be!3
    Note: That's how short your functions should be.
  • Sean shared from HBase: The Definitive Guide by Lars George
    B+ trees work well until there are too many modifications, because they force you to perform costly optimizations to retain that advantage for a limited amount of time. The more and faster you add data at random locations, the faster the pages become fragmented again. Eventually, you may take in data at a higher rate than the optimization process takes to rewrite the existing files. The updates and deletes are done at disk seek rates, rather than disk transfer rates.
    Note: A key concept of RDBMS performance.
  • Sean shared from Pirate Cinema by Cory Doctorow
    But it didn’t cost me much to try and fail. If you want to double your success rate, triple your failure rate. That’s what I always say. And sometimes, you’ve just got to be crazy about it.
    Note: "If you want to double your success rate, triple your failure rate."
  • Sean shared from Eloquent Ruby (Addison-Wesley Professional Ruby Series) by Russ Olsen
    method names, is bad. In Ruby it’s a complete disaster. Since bad Ruby code does not have the last resort crutch of type declarations to lean on, bad Ruby code can be very bad indeed. The only solution is to not write bad Ruby code.
    Note: The first rule of tautology club is the first rule of tautology club.
  • Sean shared from Eloquent Ruby (Addison-Wesley Professional Ruby Series) by Russ Olsen
    The first is that code should be crystal clear—good code tells the reader exactly what it is trying to do. Great code shouts its intent. The second idea is related to the first: Since there is a limit to how much information you can keep in your head at any given moment, good code is not just clear, it is also concise. It’s much easier to understand what a method or a class is doing if you can take it all in at a glance.
    Note: Great code shouts its intent.
  • Sean shared from The Rapture of the Nerds: A tale of the singularity, posthumanity, and awkward social situations by Cory Doctorow, Charles Stross
    She might actually be a communicant, he realizes in absolute horror. She might actually have a Facebook account! She’s mad enough.… These days, tales of what Facebook did with its users during the singularity are commonly used to scare naughty children in Wales.
    Note: Facebook cautionary tales.
(SEATTLE, WA)
Sean Blakey