Skip to main content

Matt Perez

Matt Perez's Public Library

  • When something is going wrong with our systems at any place along the line, this script should halt new commits. So if the CI server runs a build and even one test breaks, the commit script should prohibit new code from being added to the repository. In subsequent steps, we’ll add additional rules that also “stop the line,” and therefore halt new commits.
  • attempting to build a complex deployment system like that from scratch is a bad idea.

  • When you buy a book, you establish a property right in it, just as you do in clothes or furniture when you buy and pay for them. But the act of purchase is actually only the prelude to possession in the case of a book. Full ownership of a book only comes when you have made it a part of yourself, and the best way to make yourself a part of it — which comes to the same thing — is by writing in it.


    Why is marking a book indispensable to reading it? First, it keeps you awake — not merely conscious, but wide awake. Second, reading, if it is active, is thinking, and thinking tends to express itself in words, spoken or written. The person who says he knows what he thinks but cannot express it usually does not know what he thinks. Third, writing your reactions down helps you to remember the thoughts of the author.


    Reading a book should be a conversation between you and the author. Presumably he knows more about the subject than you do; if not, you probably should not be bothering with his book. But understanding is a two-way operation; the learner has to question himself and question the teacher, once he understands what the teacher is saying. Marking a book is literally an expression of your differences or your agreements with the author. It is the highest respect you can pay him.”

    • Write the way you talk. Naturally.
    • Use short words, short sentences and short paragraphs.
    • Never use jargon words like reconceptualize, demassification, attitudinally, judgmentally. They are hallmarks of a pretentious ass.
    • Never write more than two pages on any subject.
    • Check your quotations.
    • Never send a letter or a memo on the day you write it. Read it aloud the next morning — and then edit it.
    • If it is something important, get a colleague to improve it.
    • Before you send your letter or your memo, make sure it is crystal clear what you want the recipient to do.
    • If you want ACTION, don’t write. Go and tell the guy what you want.

  • Teachers for example, would forego tuition in exchange for a dividend in their student’s future productivity.

in list: Magic w/o Tricks

  • The only thing Summer of Code does, that's revolutionary… is it pairs up an experienced open source developer who's used to working remotely with other people with a neophyte developer. That's the remarkable thing because in the end that student can always go to their mentor and they can say, 'I'm having a problem.' Or the mentor can watch the incoming change list and say, "You're having a problem. If you do this and this, you're be doing good. If you do this and this, you're going to be doing bad." You don't even get that in most jobs!
1 - 20 of 1834 Next › Last »
20 items/page

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo