4 ms·
Dear Anon192, I noticed several wordings and sentences in your post that make it seem like you're identifying yourself too much with your company: > very promi
by ivan_ah 8y ago
Dear Anon192, I noticed several wordings and sentences in your post that make it seem like you're identifying yourself too much with your company:
> very promising startup [...]
> [...] that will hurt our chances of raising more funding
This is a big red flag for me (been there done that), and I want to recommend you spend some time reflecting on why you have become so "attached" to your startup. Are you deriving your sense of achievement, happiness and self-worth due to the work you're currently doing?
If you are, you need to quickly snap out of it because this is not good for you. Your worth as a human being is not tied to the code quantity, quality, and test coverage. Sure it feels great to be useful and achieve something technical, but it is not good to depend on this for your feelings and self-worth because such "coupling" to the job can come back and bite you big time.
Let me explain. When your self feeds on the "achievement buzz" you experience from getting good things done on the job ("Yey I'm a great person because I achieved A, B, C today and they are perform really well"). This sounds like a good thing—why shouldn't you be able to take pride in your work and derive personal good feelings from you hard work? The problem is that it's not always going to be good: negative feedback from the job world will hit you really hard ("Oh I suck, because X doesn't work, Y is slow, and Z never shipped"). The only way to avoid this job->personal problems is to avoid the "tight coupling" and not identify so strongly with your job/startup. The next time something great happens at work, you ship something, you achieve a breakthrough, etc. don't let you ego feed on that positive feedback. Just say "yes it was a good day at work" (i.e. don't put yourself personally in the picture "I'm so great because I did this") You have to stay at arms length. Then when negative feedback comes up at work you can say "This was a bad day at work" and won't feel personally affected by this. Basically, you want the "job system" to be able to crash, without your "self system" being affected.
I think if you take my advice and reconsider your "tight coupling" to the job/company, the problems you're experiencing with your colleague will become easer to manage. It's not your job to think about the wellbeing of the company as a whole. Just focus on your tasks, and don't try to fix other people. Sure if feels great to ship lots of things quickly, but it doesn't HAVE to be this way, and when productivity doesn't happen there is no need to beat yourself up about it. Rushing and pushing harder doesn't work long term. Just keep shipping at the pace that the team can support and don't try to go faster than that. Instead try doing less, taking afternoons off, and stop compensating for your colleague in order to achieve some higher ideal standard of productivity.
In another commend, ChuckMcM gave this advice """More importantly, change the criteria for 'success' in your mind from "product" to "what you have produced." """ which is very good and could be a first step to the de-coupling work you have to do from the company.