| Are you me? Programming feels like productive work, and indeed it is, up until just about the point you are at. Now it is not productive work any more, in fact, once the product is finished, programming is counter productive work. Other things need to be done and you don't know how to do them and if you do, are not in the habit of doing them. IOt is easy to get up in the morning and write code, harder to do unfamiliar things. --> self sabotage (deeply seated need to actually not succeed) --> fear of the unknown --> avoidance of a change in work habit - from programming to...... ? what does one do post launch --> fear of the likely outcome which is zero feedback, zero users Curious - how close are you to launch, what remains to be done, and what does the software actually do? Can I suggest perhaps be really ruthless about the remaining tasks - likely many of those launch tasks just are not important, even though the completionist in you thinks they are. For example - terms and conditions document? Ditch it until users are interested. Privacy document? Same. Purchase? Drop it. See what I mean? If people like what you have built and use it, then the world will not come to an end because you did not have those things... and user interest will motivate you to implement them. It's incredibly hard to work on something with no user interest. Just dump what you have built out there and see what happens. |
So many testers said they would try it out, never did and there was an insane amount of actual testers who wanted something slighty different. (Which i couldn't do, as I had spoken to the company, and doing certain automated style actions would have gotten me banned).