Writing code is not production, it's not always craftsmanship though it can be, it's design. — Joel Spolsky Copy Share Image
If you are a programmer working in 2006 and you don’t know the basics of characters, character sets, encodings, and Unicode, and… — Joel Spolsky Copy Share Image
Last week I was listening to a podcast on Hanselminutes, with Robert Martin talking about the SOLID principles … they all sounded… — Joel Spolsky Copy Share Image
“Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules.… — Joel Spolsky Copy Share Image
There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think… — Joel Spolsky Copy Share Image
Not having a schedule is OK if it's your PhD and you plan to spend 14 years on the thing, or if… — Joel Spolsky Copy Share Image
Software development takes immense intellectual effort. Even the best programmers can rarely sustain that level of effort for more than a few… — Joel Spolsky Copy Share Image
We just have to come in every morning and somehow, launch the editor. — Joel Spolsky Copy Share Image
Common programmer thought pattern: there are only three numbers: 0, 1, and n. — Joel Spolsky Copy Share Image
A user interface is well-designed when the program behaves exactly how the user thought it would. — Joel Spolsky Copy Share Image
“When you're designing for extremes with software, the three most important "extremes" to remember are: 1. Design for people who can't read.… — Joel Spolsky Copy Share Image
Watching nonprogrammers trying to run software companies is like watching someone who doesn’t know how to surf trying to surf. Even if… — Joel Spolsky Copy Share Image
“Usability, fundamentally, is a matter of bringing a bit of human rights into the world of computer-human interaction. It's a way to… — Joel Spolsky Copy Share Image
If your goals is to produce something of permanent value, you start to think differently about you want on the site. — Joel Spolsky Copy Share Image
Remember, just because Microsoft can do something, doesn't mean you can. Microsoft makes their own gravity. Normal rules don't apply to them. — Joel Spolsky Copy Share Image
“If you can’t understand the spec for a new technology, don’t worry: nobody else will understand it either, and the technology won’t be that… — Joel Spolsky Copy Share Image
So if you want to get things done, you positively have to understand at any given point in time what is the most important… — Joel Spolsky Copy Share Image
Not having a schedule is OK if it's your PhD and you plan to spend 14 years on the thing, or if you're a… — Joel Spolsky Copy Share Image
If you are a programmer working in 2006 and you don’t know the basics of characters, character sets, encodings, and Unicode, and I catch… — Joel Spolsky Copy Share Image
“In any case, even if a usability test resolves a dispute, it doesn't do it in any kind of a statistically valid way. Unless… — Joel Spolsky Copy Share Image
“The confidence you get from knowing about every crash, anywhere in the world, is crucial to delivering a high-quality product that needs to be… — Joel Spolsky Copy Share Image
“Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think… — Joel Spolsky Copy Share Image
Beware of Methodologies. They are a great way to bring everyone up to a dismal, but passable, level of performance, but at the same… — Joel Spolsky Copy Share Image
![“There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. [...] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It's harder to read code than to write…” quote by Joel Spolsky](https://sms4smile.com/quotes/img-quotes/f99/joel-spolsky-15347_cardinals_there-s-a-subtle-reason-that-programmers_814251.jpg)
