1
Most cited
Posts that commenters keep linking to, ranked by how many different people have cited them in Hacker News comments. 416 posts.
2
The CADT Model
In February 2003, a bunch of the outstanding bugs I'd reported against various GNOME programs over the previous couple of years were all closed as follows:
3
How To Become A Hacker
As editor of the Jargon File and author of a few other well-known documents of similar nature, I often get email requests from enthusiastic network newbies asking (in effect) "how can I learn to be a wizardly hacker?". Back in 1996 I noticed that there didn't seem to be any other FAQs or web documents that addressed…
4
How to Start a Startup (2005)
March 2005 (This essay is derived from a talk at the Harvard Computer Society.) You need three things to create a successful startup: to start with good people, to make something customers actually want, and to spend as little money as possible. Most startups that fail do it because they fail at one of these. A…
5
The illustrated guide to a Ph.D.
There's a bit more below, but I also wrote a follow-up 5 years after the illustrated guide which may be of interest -- HOWTO: Get tenure .
6
What We Look for in Founders
(I wrote this for Forbes, who asked me to write something about the qualities we look for in founders. In print they had to cut the last item because they didn't have room.) 1. Determination This has turned out to be the most important quality in startup founders. We thought when we started Y Combinator that the most…
7
"Dabblers and Blowhards" - hackers are nothing like painters [2005]
About two years ago, the Lisp programmer and dot-com millionaire Paul Graham wrote an essay entitled Hackers and Painters , in which he argues that his approach to computer programming is better described by analogies to the visual arts than by the phrase "computer science".
8
(How to Write a (Lisp) Interpreter (in Python))
Why does this matter? As Steve Yegge said , "If you don't know how compilers work, then you don't know how computers work." Yegge describes 8 problems that can be solved with compilers (or equally well with interpreters, or with Yegge's typical heavy dosage of cynicism).
9
Results of XKCD Color Survey
Who in the rainbow can draw the line where the violet tint ends and the orange tint begins? Distinctly we see the difference of the colors, but where exactly does the one first blendingly enter int…
10
The Joel Test: 12 Steps to Better Code (2000; Still relevant?)
Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a software team is. No, wait! Don’t follow that link! It will take you about six years just to understa…
11
Spolsky on "Commoditizing Your Complements"
When I was in college I took two intro economics courses: macroeconomics and microeconomics. Macro was full of theories like “low unemployment causes inflation” that never quite stood u…
12
13
14
Accelerando - Charlie's Diary
This free ebook edition is made available by kind consent of my publishers, Ace and Orbit, under a Creative Commons license with certain restrictions attached. In particular, you may not create derivative works or use the work for commercial gain .
15
How To Become A Hacker
As editor of the Jargon File and author of a few other well-known documents of similar nature, I often get email requests from enthusiastic network newbies asking (in effect) "how can I learn to be a wizardly hacker?". Back in 1996 I noticed that there didn't seem to be any other FAQs or web documents that addressed…
16
Implementing Regular Expressions
This page collects resources about implementing regular expression search efficiently.
17
Ideas are just a multiplier of execution
Derek Sivers official site. Thoughts on philosophy, culture, self-improvement. Author of Useful Not True, How to Live, Hell Yeah or No, Anything You Want.
18
Scott and Scurvy: How the cure for scurvy was lost
Writing about the first winter the men spent on the ice, Cherry-Garrard casually mentions an astonishing lecture on scurvy by one of the expedition’s doctors:
19
What Happened to Yahoo
August 2010 When I went to work for Yahoo after they bought our startup in 1998, it felt like the center of the world. It was supposed to be the next big thing. It was supposed to be what Google turned out to be. What went wrong? The problems that hosed Yahoo go back a long time, practically to the beginning of the…
20
The Top Idea in Your Mind
July 2010 I realized recently that what one thinks about in the shower in the morning is more important than I'd thought. I knew it was a good time to have ideas. Now I'd go further: now I'd say it's hard to do a really good job on anything you don't think about in the shower. Everyone who's worked on difficult…
21
22
Yosefk - My history with Forth & stack machines
My VLSI tools take a chip from conception through testing. Perhaps 500 lines of source code. Cadence, Mentor Graphics do the same, more or less. With how much source/object code?
23
My First BillG Review
In the olden days, Excel had a very awkward programming language without a name. “Excel Macros,” we called it. It was a severely dysfunctional programming language without variables (yo…
24
25
Fast. Easy. Clean. Shoelace Knot.
Tutorial for tying the “Ian Knot”, the world's fastest shoelace knot.
26
Ask HN: How do you solve hard problems if you can't make incremental progress?
Ron Jeffries attempts to create a sudoku solver - here , here , here , here and here . (You really ought to read these articles. They are u...
27
Tarsnap - The scrypt key derivation function and encryption utility
The scrypt key derivation function and encryption utility
28
29
Organic Startup Ideas
April 2010 The best way to come up with startup ideas is to ask yourself the question: what do you wish someone would make for you? There are two types of startup ideas: those that grow organically out of your own life, and those that you decide, from afar, are going to be necessary to some class of users other than…
30
Readme Driven Development
I hear a lot of talk these days about TDD and BDD and Extreme Programming and SCRUM and stand up meetings and all kinds of methodologies and techniques for developing better software, but it’s all irrelevant unless the software we’re building meets the needs of those that are using it. Let me put that another way. A…