Start In The Middle
coderoom.wordpress.com
Start In The Middle
1–10 of 18 posts
Re: Start In The Middle
#2My hard-drive is littered with projects where I did tackle the cool bits first. It's how I work. Most of them aren't finished though because I lose interest when I hit the boring bits.
The only way I get through boring code it would seem, is by getting paid to slog through it.
This will likely lead to premature aging and an early grave for me...
Re: Start In The Middle
#3I absolutely concur, at least with respect to my own motivations and habits. Every successful project I've built started in the middle; whereas every abandoned project started with grandiose organizational plans.
Re: Start In The Middle
#4I love how everything has a fancy name now. We've been doing StartInTheMiddle / MinimumViableProduct / Prototyping / GetSomethingOut / StepwiseRefinement for years:
Customer: I must have anything I want from the database without asking you.
Me, 1 hour later: No problem, here's your screen.
Customer: This only does does Customers. I want to pick any table.
Me, 1 hour later: No problem, now you can pick your table.
Customer: This dumps every column. I want to pick my own.
Me, 1 hour later: No problem. Now you can pick your columns.
Customer: This doesn't sort. I want it to sort.
Me, 1 hour later: No problem. Now you can sort.
Customer: But I want multiple sorts, some ascending, some descending.
Me, 1 hour later: No problem. Sort any way you want.
Customer: It dumps the whole table. I want to filter.
Me, 1 hour later: No problem. Now you can filter.
Customer: It only give me local columns. I want columns from other tables, too.
Me, 5 mins later: Give me an example.
Customer: Here. Give me these linked columns and accumulators, too.
Me, 2 days later: OK. I figured out how to give you all this data too.
Customer: OK. This will work. Why didn't you do all this in the first place?
Stepwise Refinement Method: Time to beta: 1 hour. Time to production: 3 days.
Waterfall Method: Time to beta: not applicable. Time to production: who knows?
Re: Start In The Middle
#5often the sum of all the boring bits is what distinguishes your product.
Re: Start In The Middle
#6Can't say that I've abandoned that many projects due to distraction of starting from scratch... I just haven't started that many, but I mostly agree with this line of thinking. I think programmers (myself included) tend to get distracted by optimizations and minutia which actually have no bearing on project/product success. That makes the boring, routine part much longer than it needs to be.
Re: Start In The Middle
#7My hard-drive is littered with projects where I did tackle the cool bits first. It's how I work. Most of them aren't finished though because I lose interest when I hit the boring bits. The only way I get through boring code it would seem, is by getting paid to slog through it. This will likely lead to premature aging and an early grave for me...
I started to write this exact comment this morning and then got distracted. Upvote for you.
Luckily, my current side project has someone offering feedback and is interested in turning into a real product. That is the motivation to handle the boring bits.
Re: Start In The Middle
#8I love how everything has a fancy name now. We've been doing StartInTheMiddle / MinimumViableProduct / Prototyping / GetSomethingOut / StepwiseRefinement for years: Customer: I must have anything I want from the database without asking you. Me, 1 hour later: No problem, here's your screen. Customer: This only does does Customers. I want to pick any table. Me, 1 hour later: No problem, now you can pick your table. Cus…
Not only that, but I'd imagine your customer felt more involved in the process and felt she had more ownership of the project because of it.
I have this problem: I like to start at the edges. One of the biggest hurdles for me when I code is to make myself do the MVP first, then iterate.
Re: Start In The Middle
#9This is exactly why I switch hobbies every few months. You spend so much time learning to do the thing before you actually try it. Like kayaking, or rock climbing, then you figure out that once you know what you are doing it just becomes repetitive. I wish there was a to just jump past the learning curve to experience things before you learn how to do them.
Re: Start In The Middle
#10I love how everything has a fancy name now. We've been doing StartInTheMiddle / MinimumViableProduct / Prototyping / GetSomethingOut / StepwiseRefinement for years: Customer: I must have anything I want from the database without asking you. Me, 1 hour later: No problem, here's your screen. Customer: This only does does Customers. I want to pick any table. Me, 1 hour later: No problem, now you can pick your table. Cus…
Not only that, but I'd imagine your customer felt more involved in the process and felt she had more ownership of the project because of it. I have this problem: I like to start at the edges. One of the biggest hurdles for me when I code is to make myself do the MVP first, then iterate.
"I'd imagine your customer felt more involved in the process and felt she had more ownership of the project because of it."
Either that or he wondered why he needed to tell you what to do every hour.