Quotes from Jeff Atwood

most developers don't test at all! They key in a few values at random and click a few buttons. If they don't get any unhandled exceptions, that code is ready for QA!

Writing code? That's the easy part. Getting your application in the hands of users, and creating applications that people actually want to use—now that's the hard stuff.

As we know, There are known knowns. There are things we know we know. We also know There are known unknowns. That is to say We know there are some things We do not know. But there are also unknown unknowns, The ones we don't know We don't know.

Despite popular assertions to the contrary, science tells us that money can buy happiness. To a point.

1. Buy experiences instead of things

Good thing you're tagging all those "Low Priority" tasks. God forbid you'd ever lose track of shit that's not worth doing.

The proper monitoring attitude is not to be distrustful, but instead, to show interest in their work.

4. Buy less insurance

Reading self-help advice from other people, however well-intentioned, is no substitute for getting your own damn work done. The

Brevity of code Featurefulness Speed of execution Time spent coding Robustness Flexibility

Obviously we want to succeed. But on some level, success is irrelevant, because the process is inherently satisfying. Waking

That's not to say that all software project management books are crap. Just most of them. One of the few that I've found compelling enough to finish is Johanna Rothman's "Behind Closed Doors: Secrets of Great Management." She co-wrote it with Esther Derby.

5. Pay now and consume later

Innovation is not about saying yes to everything. It's about saying no to all but the most crucial features.

If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea.

7. Beware of comparison shopping

In software, we rarely have meaningful requirements. Even if we do, the only measure of success that matters is whether our solution solves the customer's shifting idea of what their problem is.

Writing code? That's the easy part. Getting your application in the hands of users, and creating applications that people actually want to use - now that's the hard stuff.

We have to stop optimizing for programmers and start optimizing for users.