610 karma · joined December 29, 2011
Second, what would the pricing be for the option?
If it's $10-20, that'd probably be fine, similar to what Amazon did for Kindle. But if it's more than that, then I bet the negative PR they would get for including the option outweighs the potential benefit to customers. "I would never buy an X, they're extremely greedy and want $50 just not to show ads. Crazy. I'll buy Y brand instead (which has ads but no 'corporate greed' option to not show them)".
It'sutterly insane to me that the step-up basis exists in the US, it's such an obvious loophole that can fairly easily be closed without many adverse effects.
In my country (Sweden) if you don't know the purchase price, you can use an approximate purchasing price (e.g. for equities you are allowed to assume that it was acquired for 20% of the current value, so you'd be taxed on 80%).
Of course it's easier to integrate a magnitude fewer refugees, and there will be less issues overall.
Most people are nowhere close to working fully focused 8 hours a day, and may also benefit from more time to recharge. Others benefit less. The average probably matters more for the company (also shorter work hours will improve retention, or allow you to pay lower wages to compete etc).
If your country's only advantage is to steal tax money from other countries, or provide cheap energy by burning coal, or cheap labor by using slaves, then it's perfectly fine to isolate that country to force it to stop. We obviously shouldn't just accept that everyone is worse off just so that a country with no other advantage can thrive.
If you say you're doing continuous deployment because you deploy every Tuesday evening, it's perfectly fair to point out that that's not continuous deployment.
Of course, you should follow it up by explaining why as well, but many companies don't actually follow the agile principles.
If you're competing within the team to complete as many story points as possible that's pretty weird. Is someone using story points as a metric of anything other than forecasting?
The "constantly coding on side projects" developer is pretty rare, in my experience, but tend to bubble together. (in startups, cooler tech companies or in the "innovation teams").
I absolutely, 100%, agree that a small and focused team is the best way to get shit done, but for a large company the size of Spotify the amount of work is absolutely massive. I wouldn't be surprised at all if many teams at Spotify are small and tight-knit and doing great work at delivering kick-ass anti-fraud systems or moderation software to detect and report child porn etc.
Not to mention the obvious thing where the higher your revenue, the less percentual impact each employee needs to have to more than pay for themselves. While you might think it's ridiculous to have a full team dedicated solely to the main marketing page, that could be extremely worth it if that team increases conversion by 10%, as an example.
I'm surprised people don't realize this, especially on hackernews.