| «« UnsupportedOperationException | First Week »» |
|
About
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
Projects
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005 » Former committer for RadRails (now Aptana) » I also have a few Rails side-projects in development: 1. wheretogoinTO.com Toronto nightlife 2. Hey Heads Up! TODO list and sharing 3. Layered Genealogy family history research 4. foos for foosball scoring 5. fanconcert for music fans (on hold) Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada »» Email: rails AT ryanlowe DOT ca
BulletBlog
Now hosted on Hey! Heads Up -- check it out!
Syndication
Pings
Recent
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
blog@ryanlowe.ca no more Forging Email Headers: Good, Bad or Ugly? Sarcastic Dictionary (Part 1 of Many) Tags Hierarchies Twisting Rails is Risky Business Risky Business? My Take on Early Alphas Whoa, it's August 2007 Closing Comments A Postscript to "Growth at the grassroots" »» All Blog Posts
Linkage
del.icio.us/ryanlowe
technorati/ryanlowe.ca/blog Aurora Roy Jim Andrew Trasker Travis Kibbee Karen Dr. Unk Ayana Van Bloggers Joel Spolsky Robert Scoble Tim Bray Dave Winer Raymond Chen James Robertson Ruby/Rails Bloggers rubyonrails.org weblog David Heinemeier Hansson Dave Thomas James Duncan Davidson Mike Clark Jamis Buck Signal vs. Noise Tobias Luetke Amy Hoy: (24)slash7 Jeremy Voorhis Eclipse Bloggers Planet Eclipse EclipseZone Luis de la Rosa Eclipse Foundation Kim Horne Billy Biggs Ian Skerrett Mike Milinkovich Bjorn Freeman-Benson Denis Roy
Archives
|
Hackers and Painters
I just read a great article by Paul Graham entitled Hackers and Painters. There were a lot of great quotes and ideas in it but here are two I liked most: Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design-- deciding too early what a program should do. When a piece of code is being hacked by three or four different people, no one of whom really owns it, it will end up being like a common-room. It will tend to feel bleak and abandoned, and accumulate cruft. The right way to collaborate, I think, is to divide projects into sharply defined modules, each with a definite owner, and with interfaces between them that are as carefully designed and, if possible, as articulated as programming languages. His ideas about a loosely typed language allowing for increased changability made sense but I wonder if that wouldn't just increase problems at debugging time instead of compile time. Probably not if you had good tests. Posted at May 08, 2003 at 09:23 PM ESTLast updated May 08, 2003 at 09:23 PM EST Comments
If you've read Descartes. Then the second block is really nothing knew. That concept has been around for hundreds for years...probably thousands. It's always best to have the core of the idea and design done by one, and only one person who knows what he/she is doing....you don't wanna have too many cooks in the kitchen. I often find myself baffled by these "new" ideas. They're not new. It's just people tend to think that Techies are special or something. Meh. » Posted by: roy at May 8, 2003 11:58 PMThe ideas aren't new but sometimes it's good just to have all of these ideas assembled together and related in an organized way. This article did that well, I think. » Posted by: Ryan at May 9, 2003 12:48 AMTrue dat. We *all* need to be reminded sometimes :-) » Posted by: roy at May 9, 2003 11:18 AM |