Comments URL: https://news.ycombinator.com/item?id=49164775

Points: 58

# Comments: 83

I do realize the cloud is just someone else’s computer right? Power goes in, tokens and heat come out - just in another place

If you don’t want/need a new car, the used car market in Germany is pretty active with EQAs and EQBs.

Electricity is sold on the market. If you live next to a data center you can choose not to use any services enabled by that center, but you cannot choose to pay non-datacenter prices for the electricity to charge your car or run your household

Get your new drug approved by the FDA, and ~50+ countries would follow more or less on autopilot.

This wasn’t necessarily a bad thing, because as far as I know, they really _were_ that good.

That might have changed somewhat, recently.

> Torvalds was born in Helsinki, Finland

> In 2004, Torvalds moved with his family from Silicon Valley to Portland, Oregon.

How about we keep it civilized

> > Not to be confused with Binary large object (BLOB).

> In the context of free and open-source software, proprietary software only available as a binary executable is referred to as a blob or binary blob.

[0]:https://en.wikipedia.org/wiki/Binary_blob

Nitpick, but it’s just ‘blob’ as in ‘a big blob of bytes’. It’s not an acronym or abbreviation for anything :)

Unfortunately it is now a question of sovereignty and basic risk management, not nationalism ([0] and multiple other sources).

[0]: https://mspoweruser.com/europe-calls-out-us-tech-after-micro...

Electricity has been comparatively cheap (to DK at least) for a long time due to all the hydro.

I remember as a kid when visiting family in Norway, we were surprised that there were no rules on turning off the lights when closing the door to an empty room :)

Exactly - that’s the point.

Story points assigned to a SINGLE task is not for estimating time spent on that task.

Story points can - given prior data - give you an estimate of time spent on a GROUP of future tasks

I’d like to disagree on that one. A single story point shouldn’t be translated to time, but should reflect the relative complexity between tasks (ie. a 7 is harder than a 3 and so on).

You could assign relative complexity based on a number of things:

- number of integrations to other systems, - is the area well known to the team, - is the code well tested, - is CI/CD set up, - do we need a lot of alignment or can we just get started, - etc.

So you’re not estimating time, but complexity or hardness.

Then, supposing you have a stable team, you can go back six months and find out “we do on average 90 points per month” or similar

The linked articles are not about NATO obligations.