@ravibuilds
key ideas in paul graham's how to do great work
14 items
- 01curiosity chooses the field, not passion
- 02learn until you hit the edge of what's known
- 03notice the gaps everyone stepped over
- ··11 more entries
13801
the Joel test (2000)
joel spolsky's 12 yes/no questions from his 2000 blog post. read the original, it's five minutes
01
Do you use source control?
non negotiable. no excuse for skipping this in 2026 either
02
Can you make a build in one step?
03
Do you make daily builds?
we don't, and some weeks it shows
04
Do you have a bug database?
05
Do you fix bugs before writing new code?
the one we break the most if I'm honest
06
Do you have an up-to-date schedule?
07
Do you have a spec?
still true, even for a two person team
08
Do programmers have quiet working conditions?
open floor plans failed this one before they even started
09
Do you use the best tools money can buy?
10
Do you have testers?
if the answer is "the users," that's a no
11
Do new candidates write code during their interview?
12
Do you do hallway usability testing?
grabbed the office manager once, she found 3 bugs in 5 minutes
Or start a list of your own. Free, it takes a minute.