Comments on: First things first http://rapidsignal.com/blog/2005/06/19/first-things-first/ Rapid Signal: a micro-ISV venture Wed, 07 Jan 2009 00:37:00 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Dimitris Giannitsaros http://rapidsignal.com/blog/2005/06/19/first-things-first/comment-page-1/#comment-33 Dimitris Giannitsaros Tue, 21 Jun 2005 08:08:28 +0000 http://rapidsignal.com/blog/2005/06/19/first-things-first/#comment-33 No problem at all! No problem at all!

]]> By: Michael Sica http://rapidsignal.com/blog/2005/06/19/first-things-first/comment-page-1/#comment-32 Michael Sica Tue, 21 Jun 2005 03:55:42 +0000 http://rapidsignal.com/blog/2005/06/19/first-things-first/#comment-32 Hey buddy, I started to reply to your last comment but it got kind of long. Check out my latest blog post. Please don't take offense to my disagreement! I put it on my web site because I've been meaning to do a write up about prototypes, but I just haven't been able to put it together. This little discussion really got my thoughts in order. Keep working hard man! Your fellow microISV-working-into-the-night-trying-to-live-his-dream-blog-guy, -michael. Hey buddy, I started to reply to your last comment but it got kind of long. Check out my latest blog post.

Please don’t take offense to my disagreement! I put it on my web site because I’ve been meaning to do a write up about prototypes, but I just haven’t been able to put it together. This little discussion really got my thoughts in order.

Keep working hard man!

Your fellow microISV-working-into-the-night-trying-to-live-his-dream-blog-guy,
-michael.

]]> By: Dimitris Giannitsaros http://rapidsignal.com/blog/2005/06/19/first-things-first/comment-page-1/#comment-31 Dimitris Giannitsaros Tue, 21 Jun 2005 00:34:40 +0000 http://rapidsignal.com/blog/2005/06/19/first-things-first/#comment-31 Well, I guess it all depends on your school of thought. Although I don't like extremes, I prefer this line of thought: http://www.37signals.com/svn/archives/001050.php over this: http://www.joelonsoftware.com/articles/fog0000000036.html (or your approach which is closer to the 2nd) I have thought (and written) about who (and how) will use my application. I have documented what features will go in v1.0 and what will be left for later (and even this list changes often). But I can't really commit to paper what I will be developing in say six months. I need to see things on screen, test them and often go back to the drawing board... Well, I guess it all depends on your school of thought. Although I don’t like extremes, I prefer this line of thought:
http://www.37signals.com/svn/archives/001050.php
over this:
http://www.joelonsoftware.com/articles/fog0000000036.html
(or your approach which is closer to the 2nd)

I have thought (and written) about who (and how) will use my application. I have documented what features will go in v1.0 and what will be left for later (and even this list changes often). But I can’t really commit to paper what I will be developing in say six months. I need to see things on screen, test them and often go back to the drawing board…

]]> By: Michael Sica http://rapidsignal.com/blog/2005/06/19/first-things-first/comment-page-1/#comment-30 Michael Sica Tue, 21 Jun 2005 00:02:07 +0000 http://rapidsignal.com/blog/2005/06/19/first-things-first/#comment-30 Ah! The link broke because I didn't paste last character of the file. Correct link: http://www.michaelsica.com/ataraxissoftware/2005/06/taking-step-back-defining-users-uses.html Ah! The link broke because I didn’t paste last character of the file. Correct link:

http://www.michaelsica.com/ataraxissoftware/2005/06/taking-step-back-defining-users-uses.html

]]> By: Michael Sica http://rapidsignal.com/blog/2005/06/19/first-things-first/comment-page-1/#comment-29 Michael Sica Tue, 21 Jun 2005 00:01:22 +0000 http://rapidsignal.com/blog/2005/06/19/first-things-first/#comment-29 Hey Dimitris, allow me to bask in some shamless self-promotion. http://www.michaelsica.com/ataraxissoftware/2005/06/taking-step-back-defining-users-uses.htm Please do your self a favor. Before you write another line of code, site down and start defining who will interact with your application. Write a story about how they will use the application, make a wireframe and a prototype (GUI mockups) BEFORE you write more code. The coding is the easy part. You know how to program. What you need to know is WHAT are you programming. Don't fall into the same trap I did of, "It's all in my head. I know what I'm building. It's what I'd want to use." Good luck man! Hey Dimitris, allow me to bask in some shamless self-promotion.

http://www.michaelsica.com/ataraxissoftware/2005/06/taking-step-back-defining-users-uses.htm

Please do your self a favor. Before you write another line of code, site down and start defining who will interact with your application. Write a story about how they will use the application, make a wireframe and a prototype (GUI mockups) BEFORE you write more code.

The coding is the easy part. You know how to program. What you need to know is WHAT are you programming. Don’t fall into the same trap I did of, “It’s all in my head. I know what I’m building. It’s what I’d want to use.”

Good luck man!

]]>