Piatti del giorno 66

End of a long week.

• Information Modeling in SketchUp - IFC in Sketchup. Prediction: Sketchup’s brilliantly plain-vanilla object model will click very well with the federated nature of smaller construction and become the poster app for low-road building information modelling. (h/t Jared Banks).
• Faulkner’s Nobel banquet speech - “I believe that man will not merely endure: he will prevail. He is immortal, not because he alone among creatures has an inexhaustible voice, but because he has a soul, a spirit capable of compassion and sacrifice and endurance.” (h/t Michael Lopp).
• What is concurrency? - “If you build your program out of small components that have well-described inputs and outputs, control the use of mutable shared variables, and use the right synchronization primitives for the job (shared memory, compare-and-set, concurrent collections, message queues, STM, etc.), your code can go faster.” Done. (h/t Phillip Bowden).
• Year Of Code & The Myth Of The Programmer Shortage - “Gold rushes, like the dotcom boom of the late 1990’s, tend to flood the market with average or below-average programmers. And, since the bar is set dangerously low in our profession, ‘average’ really means ‘not competent’” (h/t Katrina Owen).
• Quick and dirty fix to ManOpen - Making ManOpen work on Mavericks.
• Building JavaScript projects with Make - It’s not at all clear to me why Grunt exists.
• Single Responsibility Principle & iOS - “Using #pragma mark - is indicative of a failure to adhere to the Single Responsibility Principle and is a signpost for poor code.” (h/t Jonathan Penn).
• Git tips from the trenches - Liking help.autocorrect so far.
• The email line that’s client repellent. - tl;dr: send emails that your client can respond to with “sounds good.” (h/t Chris Nicola).
• Source Code Typography - Seems relevant in the aftermath of the goto fail bug. (h/t James Coglan).
• direnv - unclutter your .profile - Automatically EXPORT into your shell’s environment when you enter a directory and unset it when you leave. Slick.
• Code is not literature - Peter Seibel proposes that we don’t read code because one can’t really read code, at least not in the way that’s implied by the word “read.” It’s far denser than literature. Instead, we dissect and reassemble it either mentally or in an editor: “Rather, interesting pieces of code are specimens and we are naturalists.”