The Pragmatic Craftsman :: Simplicity from complexity ::

Archive for the 'Quotes' Category

Spolsky on Writing Specs August 18th, 2005
Brooks on Good Judgement June 29th, 2005
Tate on Developers June 20th, 2005
Monnox on Software Engineer June 6th, 2005
McConnell on Code Documentation March 15th, 2005
Fowler on Good Code February 4th, 2005
Holub on Simplicity December 8th, 2004
Ambler on Best Programmers November 29th, 2004
Booch on Software-Eng November 16th, 2004
Stas Kubasek on Learning New Technologies October 13th, 2004

Spolsky on Writing Specs

The reason you write a spec is not to solve every possible problem in advance: the reason you write a spec is to solve as many problems as you possibly can in advance so that you minimize the number of surprises that come up during development.
–Joel Spolsky
- talking about Copilot.com spec

Reference:Blog entry about The Project Aardvark Spec by Joel Spolsky

Related:The original spec (pdf) by Joel Spolsky

Brooks on Good Judgement

Good judgement comes from experience, and experience comes from bad judgement.
–Frederick P. Brooks

Tate on Developers

You can be a good developer by studying successful patterns and best practices, but if you want to become a great developer, you’ve got to know a technology’s limits.
–Bruce Tate
in preface of BitterEJB, 2003

Monnox on Software Engineer

A software engineer understands that self-improvement and continous learning are fundemental activities for an IT professional.
–Alan Monnox
in preface of Rapid J2EE Development, 2005

McConnell on Code Documentation

Good code is its own best documentation. As you’re about to add a comment, ask yourself, ‘How can I improve the code so that this comment isn’t needed?’ Improve the code and then document it to make it even clearer.
–Steve C McConnell

Fowler on Good Code

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
–Martin Fowler

Holub on Simplicity

Simple systems are easier to build, easier to maintain, smaller, and faster than complex ones. … Simplicity is often not an easy goal to achieve. Programmers love complexity, so they have a strong tendency to over complicate their work. It’s often easier to quickly build an overly complex system than it is to spend the time required to make the system simple.
–Allen Holub
in his recent book, Holub on Patterns, 2004

Ambler on Best Programmers

… best programmers think through the design of their code before they actually write it.
–Scott W. Ambler

Booch on Software-Eng

Parse error: syntax error, unexpected T_STRING in /srv/www/kubasek.com/public_html/wp-content/plugins/php-execution-plugin/includes/class.php_execution.php(273) : eval()’d code on line 1

Stas Kubasek on Learning New Technologies

I don’t skate where the puck is, I always skate where the puck is going to be
–Wayne Gretzky
the best hockey player.

How about that? That’s a great quote!On a similar note, here is my approach on learning new technologies:

I don’t learn technologies that are popular today, I learn technologies that are going to be popular and widely used in the future.
–Stas Kubasek

What does that mean? That means I always want to stay ahead of the game. I think that’s a pretty good strategy for the future. Strategy to be successful. We’ll see. :-)

Favorite Quote

Topics

Tags

Archive

Currently Reading

Shelfari: Book reviews on your book blog

:: The Pragmatic Craftsman recommends

:: The Pragmatic Craftsman book reviews

Info

© 2001-2010 Stanley Kubasek About me :: Contact me

Recent Entries