| «« In Through the Out Door | Mysterious Presents »» |
|
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
|
Ask: Why do you want to do that?
People often ask "how do i do this?" I'm getting into the habit of first asking them right back "why do you want to do that?" Sometimes the solution they are asking about is not suited to the problem they are trying to solve. The bad thing about that is they may not know enough about the solution to know it's unsuited. So I find that a good thing to do is to dig dig dig until you get all the way down to the intent. Once you know intent you are in a better position to give your opinion. Intent itself is unbiased by a solution, which gives you more creativity and flexibility in your own suggestion for a solution. This relates to software development in many ways but a common one is user feedback. A customer/user may not be very technically inclined but asks you to implement some specific feature or enhancement. They fall into the common feedback trap and phrase the request in the form of a solution rather than a problem. Consider their suggested solution but also dig down to the intent of the problem, so you can integrate an intent-based solution into the current software architecture. You are responsible for maintaining the architecture and making sure everything fits, not them. Posted at December 23, 2004 at 07:28 AM ESTLast updated December 23, 2004 at 07:28 AM EST Comments
That's a really great point. » Posted by: Jim at December 23, 2004 09:20 AMYip, really good point! Try telling that to the last mob I worked for. Instead of breaking down a user request, we just got told to do it by the project manager whether we agreed with it or not. Not a good way to work. » Posted by: Matthew Lang at December 23, 2004 10:35 AMI experienced that exact same thing with a customer last week. They were asking for a very complex solution to a problem they were having but when I pressed them about it, it turned out that they were mis-stating their problem. The required solution turned out to be much simpler than their original request. » Posted by: will at January 31, 2005 10:12 PM |