5 ms·
My 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 whe
by agentultra 17y ago
My 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...
- bockris 17y agoI 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.
- arbitraryperson 17y agoSame here. I was kind of confused as to why anyone would start a project and think, first, "Well, we need a user registration system." Of course, I also become bored by these little details. So I wouldn't say it's any better, but it is certainly more fun to work on the interesting bits first.
- zsouthboy 17y agoI do exactly the same thing. So many projects I've finished to 80%, because I got the thing I set out to do achieved. That final 20% is documenting, finishing a UI, etc - and I'm not forcing myself to do (in my mind, the difficulty level) trivial, uninteresting things. Hell, I probably wouldn't want to do those last things for money, either!