37signals: Bad call, great apology. It should be something we all learn as children, that our culture should encourage, but somehow, that’s not the case, and so this speaks to us a special lesson.
YouTube: “Jim Joyce Tearfully Accepts Lineup Card From Galaraga”:
If you make a mistake, admit it. It doesn’t make you a mistake. By admitting it you can learn from it. Others can learn from it. And hopefully, there is growth.
Nodeload is a stress test utility built on node.js.
O’Reilly Radar: Mike Loukides: “What is Data Science?”
Media Shift: Marc Glaser: “Why Journalists Should Learn Computer Programming”
Rafe Colburn: “Why journalists should learn to program” – with a suggestion on what really to be digging into – and I agree.
Resource: Hacks/Hackers
Consumerist: “Debtors Increasingly Thrown In Jail. Wait, What?”
ACM Queue: Ken Arnold: “Programmers are People, Too”
Communications of the ACM: “API Design Matters”
JavaWorld: “Joshua Bloch: A conversation about design”
InfoQ: Joshua Bloch: “Joshua Bloch: Bumper-Sticker API Design”
InfoQ: Video: Joshua Bloch: “How to Design a Good API & Why it Matters” (and a good thread on Hacker News).
Possible Resource: APIDesign Wiki
Good move on Google’s part. Nieman Journalism Lab: “Google News experiments with human control, promotes a new serendipity with Editors’ Picks”
Mashable: “Google News and Why Human Editors Still Matter”
Previously: Techmeme: “Guess what? Automated news doesn’t quite work.”
I am guilty as charged and with Richelle’s help, changing my ways: NYTimes: “The Risks of Parenting While Plugged In”:
…children in higher socioeconomic homes hear an average of 2,153 words an hour, whereas those in working-class households hear only about 1,251; children in the study whose parents were on welfare heard an average of 616 words an hour.
Part of the reason the children in affluent homes she studied developed larger vocabularies by the time they were 3 is that “parents are holding kids, the kids are on their lap while the parent is reading a book,” Dr. Hart said. “It is important for parents to know when they’re talking to kids, they’re transferring affection as well as words. When you talk to people, there’s always an implicit message, ‘I like you,’ or ‘I don’t like you.’ “
Hopefully you’ve read the docs and know that you can override settings and implement your own extensions rather easily:
Create a Lisp file under ~/.emacs.d/ specific to your username ($USER-NAME.el) or system ($SYSTEM-NAME.el) that Emacs with emacs-starter-kit will load automatically at startup.
I’ve created mine specific to my user name – ~/.emacs.d/kmarti05.el. You can determine the value of your user-name in emacs by issuing C-h-v user-login-name.
Here is the contents of my ~/.emacs.d/kmarti05.el file:
;; visible bell (setq visible-bell nil) ;; allow selection deletion (delete-selection-mode t) ;; make sure delete key is delete key (global-set-key [delete] 'delete-char) ;; turn on the menu bar (menu-bar-mode 1) ;; have emacs scroll line-by-line (setq scroll-step 1) ;; set color-theme (color-theme-zenburn) (defun my-zoom (n) "Increase or decrease font size based upon argument" (set-face-attribute 'default (selected-frame) :height (+ (face-attribute 'default :height) (* (if (> n 0) 1 -1) 10)))) (global-set-key (kbd "C-+") '(lambda nil (interactive) (my-zoom 1))) (global-set-key [C-kp-add] '(lambda nil (interactive) (my-zoom 1))) (global-set-key (kbd "C-_") '(lambda nil (interactive) (my-zoom -1))) (global-set-key [C-kp-subtract] '(lambda nil (interactive) (my-zoom -1))) (message "All done!")
E.W. Dijkstra ACM Turing Lecture 1972: “The Humble Programmer”:
Automatic computers have now been with us for a quarter of a century. They have had a great impact on our society in their capacity of tools, but in that capacity their influence will be but a ripple on the surface of our culture, compared with the much more profound influence they will have in their capacity of intellectual challenge without precedent in the cultural history of mankind. Hierarchical systems seem to have the property that something considered as an undivided entity on one level, is considered as a composite object on the next lower level of greater detail; as a result the natural grain of space or time that is applicable at each level decreases by an order of magnitude when we shift our attention from one level to the next lower one. We understand walls in terms of bricks, bricks in terms of crystals, crystals in terms of molecules etc. As a result the number of levels that can be distinguished meaningfully in a hierarchical system is kind of proportional to the logarithm of the ratio between the largest and the smallest grain, and therefore, unless this ratio is very large, we cannot expect many levels. In computer programming our basic building block has an associated time grain of less than a microsecond, but our program may take hours of computation time. I do not know of any other technology covering a ratio of 1010 or more: the computer, by virtue of its fantastic speed, seems to be the first to provide us with an environment where highly hierarchical artefacts are both possible and necessary. This challenge, viz. the confrontation with the programming task, is so unique that this novel experience can teach us a lot about ourselves. It should deepen our understanding of the processes of design and creation, it should give us better control over the task of organizing our thoughts. If it did not do so, to my taste we should not deserve the computer at all!
It has already taught us a few lessons, and the one I have chosen to stress in this talk is the following. We shall do a much better programming job, provided that we approach the task with a full appreciation of its tremendous difficulty, provided that we stick to modest and elegant programming languages, provided that we respect the intrinsic limitations of the human mind and approach the task as Very Humble Programmers.
It has some decent defaults (I needed just a few overrides), and it has a layout that makes it easy to extend. You can get a copy from Github here.