Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That’s a fair question. I honestly haven’t “fought” for my projects probably as much as I should.

Some of this is a result to how their criticisms are shared. Often, they will initially softly praise my efforts (“that’s a good idea, but we need to discuss it more before going live with it”).

Then, time passes, we put out other fires, other ideas for unrelated projects get discussed.

Often throughout, the problem that my (now on hold) project attempts to solve will come up multiple times. At some point, I remind them that I have a potential solution ready to go, but we still need to discuss it before going live, as they requested.

I get a “yes we will, soon” response once or twice, until finally they mention something superficially wrong and easily fixed about it (“the order of the form items need to be switched around” or “we should add a summary screen” type trivialities) and is then used as a reason why, instead of spending a day finishing the project up, we should instead focus our time on x, y, or z (none of which are even actionable projects yet).

At which point I cave. Every once in a while I get irritated to the point of blurting out something snarky when the problem presents itself (“you know, we could be done with problems like these if we had implemented my idea”) only for me to follow it up with some joke to smooth it over and not sound so bitter.

I’m sure there’s a better way for me to fight for these projects, and I hope as I become more inclined to leave, I’ll have more backbone to try them out and commit to it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: