Coding block
-
How do you guys overcome coding block? I've pushed back the due date two time already in two weeks. I keep on promising, but then not delivering. What do you think is wrong with me? I'm usually not like this. Thanks for any free advice
-
How do you guys overcome coding block? I've pushed back the due date two time already in two weeks. I keep on promising, but then not delivering. What do you think is wrong with me? I'm usually not like this. Thanks for any free advice
-
How do you guys overcome coding block? I've pushed back the due date two time already in two weeks. I keep on promising, but then not delivering. What do you think is wrong with me? I'm usually not like this. Thanks for any free advice
I think the kind of block your talking about likely comes from trying to develop software organically, rather than making all/most of the decisions up front and then implementing against a plan. Years and years ago I sometimes had the kind of malaise your talking about, but invariably it was due to a lack of good solid planning up-front, and then trying like crazy to make design decisions 1/2 way through coding (while the client is simultaneously modifying the goal). Planning is tough, no question. You have to enforce that discipline on your client almost more than yourself, and everyone has to agree on the goal, and the importance of clearly identifying what it is up-front. All that being said my recommendation to you now is to identify the absolute minimum required to actually make the software work (minimum feature set, etc.) and get the thing done. Don't allow your client to expand the scope, and if you can, try and reduce the feature set if possible. Then regroup, plan, and go at it again for v1.1
-
How do you guys overcome coding block? I've pushed back the due date two time already in two weeks. I keep on promising, but then not delivering. What do you think is wrong with me? I'm usually not like this. Thanks for any free advice
We've had the same problem recently. I (unfortunately) have been one of the worse offenders! Quite a few of us have had deadlines pushed back - although the final deadline for getting our product out to customers has to stand. Consequently, there will be less time for testing. My error was committing to do too much work in the first place. I will be more realistic next time
-
I think the kind of block your talking about likely comes from trying to develop software organically, rather than making all/most of the decisions up front and then implementing against a plan. Years and years ago I sometimes had the kind of malaise your talking about, but invariably it was due to a lack of good solid planning up-front, and then trying like crazy to make design decisions 1/2 way through coding (while the client is simultaneously modifying the goal). Planning is tough, no question. You have to enforce that discipline on your client almost more than yourself, and everyone has to agree on the goal, and the importance of clearly identifying what it is up-front. All that being said my recommendation to you now is to identify the absolute minimum required to actually make the software work (minimum feature set, etc.) and get the thing done. Don't allow your client to expand the scope, and if you can, try and reduce the feature set if possible. Then regroup, plan, and go at it again for v1.1
I agree with this entirely. At least, it's happened to me before
-
I think the kind of block your talking about likely comes from trying to develop software organically, rather than making all/most of the decisions up front and then implementing against a plan. Years and years ago I sometimes had the kind of malaise your talking about, but invariably it was due to a lack of good solid planning up-front, and then trying like crazy to make design decisions 1/2 way through coding (while the client is simultaneously modifying the goal). Planning is tough, no question. You have to enforce that discipline on your client almost more than yourself, and everyone has to agree on the goal, and the importance of clearly identifying what it is up-front. All that being said my recommendation to you now is to identify the absolute minimum required to actually make the software work (minimum feature set, etc.) and get the thing done. Don't allow your client to expand the scope, and if you can, try and reduce the feature set if possible. Then regroup, plan, and go at it again for v1.1
Thanks for the suggestions everyone! I'm not too sure what you "organically" means, but I think I get the point though -- make a plan! I think I'm trying to overwhelm myself with too many design details. I should probably think of the "minimum feature set" as you've suggested and get that accomplished first and add things on later. The only fear I have with this approach is that my design of the minimum feature set might not be expand well when I add the other features that are required, and have to rewrite the code over again. But I assume that's what most people do anyways to get a good design. Code and redesign and recode until you like it, without fear of throwing away the prototype code. Thanks again
-
Thanks for the suggestions everyone! I'm not too sure what you "organically" means, but I think I get the point though -- make a plan! I think I'm trying to overwhelm myself with too many design details. I should probably think of the "minimum feature set" as you've suggested and get that accomplished first and add things on later. The only fear I have with this approach is that my design of the minimum feature set might not be expand well when I add the other features that are required, and have to rewrite the code over again. But I assume that's what most people do anyways to get a good design. Code and redesign and recode until you like it, without fear of throwing away the prototype code. Thanks again
Perhaps you could think about add-ins? It's sort of complex, but look at http://www.codeproject.com/dll/plug-in.asp if you're interested
-
How do you guys overcome coding block? I've pushed back the due date two time already in two weeks. I keep on promising, but then not delivering. What do you think is wrong with me? I'm usually not like this. Thanks for any free advice