Hacker Newsnew | past | comments | ask | show | jobs | submit | tweetle_beetle's commentslogin

The page proclaims "A Ferrari is forever" underneath showcasing an app for chasing climate control. Durability/preservation and companion apps don't go hand in hand.

It could be like the specialist supercar garages keeping a specific model of 90s Compaq laptop which run DOS with custom cards as they're the only way to interface with McLarens F1s. In 2050: "We keep an iPhone 13 with the app loaded which has never been allowed to connect to the internet so we can move the seats back".


Isn't Venice as problematic/artificial as suburbia in its own way? If you're saying car-free then I assume you mean the centre, where the real population is tiny (compared to San Francisco at <50k), aging, declining amd dwarfed by tourists. My understanding is that it's increasingly meeting needs of tens of millions of ultra short term visitors rather than real communities. It feels like there must be a wide range of happy medium places in between.

The actual Venice in the lagoon is fine. Nothing like suburbia.

35 in total as of last year, with the most recent released in 2004

https://web.archive.org/web/20250215082603/http://www.dogme9...


That said, I'm not sure if new certifications are still being accepted. So there may have been uncertified Dogme95-compliant films made since that was never been in the official list.

To extend your metaphor further, it would be like also giving them performance bonuses and building them a new home office which they then rent out on AirBnB on the strength of those predictions.

> Tesla acquired SolarCity for $2.6 billion partly on the strength of this vision [of producing thousands


I once met someone who refused to engage with leadership using his team's story points as a direct measure of productivity. To make it harder to extract the data and compare against other teams, they moved to using names of animals to represent types of task associated with differing amounts of uncertainty.

I've also seen a supplier who was asked to provide some kind of tracking, where literally nothing existed. Their delivery team produced reports with story points per person, per task, per sprint. Every sprint, every person hit their target month after month after month. They were asked to stop.


If your limit for being slightly out of your comfort zone is a year, why did you have a child? You don't have to be a parent to know that you are going to be challenged when a baby arrives.


Amusing that's he's praised the original for it's lack of precision and predictability, which makes it more "human" and "honest", then spends loads of money refining it. Must be craving precision crafted dishonesty in his photography these days.



Easy repairability is good too. (I was going by their own "Specifications" that said battery is "non-removable" - https://archive.md/Ngoxu ). I would buy this phone if my banking app is able to run on it.


Confluence and Notion are not equivalent products. Docmost looks to be similar to Confluence - a full fat wiki, but the whole point of Notion was its database-like features.


As with most things, isn't the truth somewhere in the middle? True cost/value is very hard to calculate, but we could all benefit by trying a bit harder to get closer to it.

It's all too common to frame the tension as binary: bean counters vs pampered artistes. I've seen it many times and it doesn't lead anywhere useful.


Here I think the truth is pretty far to one side. Most engineering teams work at a level of abstraction where revenue attribution is too vague and approximate to produce meaningful numbers. The company shipped 10 major features last quarter and ARR went up $1m across 4 new contracts using all of them; what is the dollar value of Feature #7? Well, each team is going to internally attribute the entire new revenue to themselves, and I don’t know what any other answer could possibly look like.


Even if you could do attribution correctly (I think you can do this partially if you are really diligent about A/B testing), that is still only one input to the equation. The other fact worth considering is the scale factor - if a team develops a widget which has some ARR value today, that same widget has a future ARR value that scales with more product adoption - no additional capital required to capture more marginal value. How do you quantify this? Because it is hard and recursive (knowing how valuable a feature will be in the future means knowing how many users you have in the future which depends on how valuable your features are as well as 100 other factors), we just factor this out and don't attempt to quantify things in dollars and euros.


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

Search: