595 karma · joined March 17, 2009
A comparison would really be a VC saying - I will invest in your company if you give me 80% equity. Or Yes, I will invest if you hit 30% growth in profit for the next one month. That, to me, may be unfair in some cases, but doesn't sound unscrupulous.
After 4 years, the car is yours.
I think another lesson learned is that the log analyzer needs to be analyzed.
Moral: Correlation does not imply causality.
Humor on the web and why to stop it (if you run a community site)
Sometimes the best way to break a bad habit is to enforce it
Base Price (US) < Base Price (India)
Base Price+warranty(US) > Base Price (India)
Base Price+warranty(US) < Base Price + warranty (India)
-- i.e. the difference wasn't that large as evidenced by eq. 2
I guess I see the following scenarios could make this work:
1. Build a 'feature' that is complex enough that the other company will see value in just acquiring you rather than eliminating you.
2. Work for early mega-adoption so that you can pivot to larger scope/better product based on feedback
1. There is an objective way to measure your performance
2. That way does not depend on any team level/company level objectives like finalizing a business model, completing a prototype, making a sale, getting funded - as a fresh grad, you will have little to no impact on any of these, and so you should neither be rewarded nor penalized for these
3. The current finances and burn rate of the startup makes you feel comfortable that the company will have the money to make the upgrade without hitch.
4a. You have absolute trust in the founders that they will stick to their word
4b. get the criteria in a contract
on second thoughts, if 4a is not true, you shouldn't join the startup anyway - startups have a lot more dependent on the founders being moral rather than a large company where everything is process driven.
Also, if you have to go the 4b route, you will potentially leave them with ill feeling towards you ('this guy doesn't even trust us'). Meaning you wouldn't/shouldn't get hired.
If others have ever noted that you're borderline perfectionistic, this is the job for you!
(on the customer service job posting)
Could we also talk a bit more about the problem I was trying to get around to - how do you solve the second problem? How do I 'by all means don't let that happen'?
The basic point you are making is that if there are unplanned/under-planned developments, we need to account for them in a way that's humane, rather than forcing the developer to hold on to an arbitrarily identified date. I am all for it, but in my case, I am not getting any good reason for the delay, just a note that things are delayed.
I think my question is being taken the wrong way. Let me try asking again: I have work X to get done. I have a team member who I would like to work on this. I ask them to estimate the work, validate the estimates and then track against the same. In the weekly status calls, if they are behind schedule, can not give a justifiable reason for being behind (like personal reasons, unexpected technical complexity, hardware issues); how does the group manage?
Its frustrating to be in my place, because I feel sad for the nightouter when he picks up for the third guy