(
This is a snapshot of my old weblog. New posts and selected republished essays can be found at
raganwald.com
.)
Monday, December 18, 2006
Never stop learning
I think every program you write should be the hardest you’ve ever written.
Steve Yegge
Labels:
passion
¶
7:54 AM
Comments on “
Never stop learning
”
:
Assuming that we're not giving up the constraint that you actually
succeed
at writing each program, then this is a recipe for happiness, success and growth that would work quite handily for me.
I tend to be a titch
beyond the success curve
, though....
#
posted by
Chalain
: 10:24 AM
I have given up the success constraint. Luckily, I am still able to be happy and experience growth.
In fact, my definition of hard
requires
some uncertainty of whether I'll succeed. That's part of what makes such projects an opportunity for growth.
#
posted by
Reginald Braithwaite
: 10:27 AM
It's not always the result which count but the way to get it, especially when the problem is not very hard.
Many not-so-hard problem are good test-bed for using powerful new abstraction and the mind expansion that goes with it.
Expanding one's mind is hard (and is a strange feeling).
If the goal is to get better, that what we are after.
Sadly most control-freak work environment are not very friendly toward this kind of behavior.
One minute of silence for all the frustrated coders.
#
posted by
Lionel Barret
: 12:18 PM
<< Home
Reg Braithwaite
Recent Writing
Homoiconic Technical Writing
/
raganwald.posterous.com
Books
What I‘ve Learned From Failure
/
Kestrels, Quirky Birds, and Hopeless Egocentricity
Share
rewrite_rails
/
andand
/
unfold.rb
/
string_to_proc.rb
/
dsl_and_let.rb
/
comprehension.rb
/
lazy_lists.rb
Beauty
IS-STRICTLY-EQUIVALENT-TO-A
/
Spaghetti-Western Coding
/
Golf is a good program spoiled
/
Programming conventions as signals
/
Not all functions should be object methods
The Not So Big Software Design
/
Writing programs for people to read
/
Why Why Functional Programming Matters Matters
/
But Y would I want to do a thing like this?
Work
The single most important thing you must do to improve your programming career
/
The Naïve Approach to Hiring People
/
No Disrespect
/
Take control of your interview
/
Three tips for getting a job through a recruiter
/
My favourite interview question
Management
Exception Handling in Software Development
/
What if powerful languages and idioms only work for small teams?
/
Bricks
/
Which theory fits the evidence?
/
Still failing, still learning
/
What I’ve learned from failure
Notation
The unary ampersand in Ruby
/
(1..100).inject(&:+)
/
The challenge of teaching yourself a programming language
/
The significance of the meta-circular interpreter
/
Block-Structured Javascript
/
Haskell, Ruby and Infinity
/
Closures and Higher-Order Functions
Opinion
Why Apple is more expensive than Amazon
/
Why we are the biggest obstacles to our own growth
/
Is software the documentation of business process mistakes?
/
We have lost control of the apparatus
/
What I’ve Learned From Sales
I
,
II
,
III
Whimsey
The Narcissism of Small Code Differences
/
Billy Martin’s Technique for Managing his Manager
/
Three stories about The Tao
/
Programming Language Stories
/
Why You Need a Degree to Work For BigCo
History
06/04
/
07/04
/
08/04
/
09/04
/
10/04
/
11/04
/
12/04
/
01/05
/
02/05
/
03/05
/
04/05
/
06/05
/
07/05
/
08/05
/
09/05
/
10/05
/
11/05
/
01/06
/
02/06
/
03/06
/
04/06
/
05/06
/
06/06
/
07/06
/
08/06
/
09/06
/
10/06
/
11/06
/
12/06
/
01/07
/
02/07
/
03/07
/
04/07
/
05/07
/
06/07
/
07/07
/
08/07
/
09/07
/
10/07
/
11/07
/
12/07
/
01/08
/
02/08
/
03/08
/
04/08
/
05/08
/
06/08
/
07/08
/