undreren

I did. It is clear that you have no idea how bad this have gotten in other countries.

These are iniatives to spare the old and the weak. How little regard do you have for these people? Their mortality rate is way higher than 0.5%

Everyone is possibly a transmitter. We are protecting the old and weak, not the young and healthy.

This is what lethal ignorance looks like.

Kids are much worse vectors for the spread of the disease, so this is absolutely NOT a good argument.

Mass surveillance is a nightmare for political activists, key figures in grass root movements, journalists and political opponents.

And that's what makes it a nightmare for the rest of us.

I'm not much of a conspiracy theorist, but it seems awfully convenient that a guy that knows how to nuke his hard disk to protect himself from the CIA, only nukes the the hard disk he downloaded the WikiLeaks transfer program on, and then forgets to nuke the hard disk riddled with child porn.

They give up. Literally. A lot of content creators even joke about it during their videos.

“Gotta hurry past this café so the music won’t get my video copyright striked, lol!”

Two, but sometimes closer to three.

Oh really? I often mention my salary when relevant, and I have never experienced any negativity.

They are not supposed to be located at homeowners, and in Denmark we already (mostly) have the infrastructure to support it.

I actually completely forgot about why they were cylindrical and all the benefits.

I worked for a major Danish power company for 2.5 years, but I mostly did mathematical modelling and implementation of the production planning system.

We do this in Denmark for storage of district heating water. They are called "varmeakkumulatortanke" in Danish, roughly translated to "heat accumulator tanks".

They are insulated like a thermos (but more efficiently), and since they are really big, they have small surface area compared to their volume.

It is a VERY efficient way to store heat over shorter periods, like a week or so, and it helps making power plants more cost efficient.

The best way to make it efficient for long term storage (like seasonal storage) is to

1. Make them huge

2. Make them ball shaped

3. Put them underground

There has been talk of tryibg this out in Denmark. Almost all our powerplants (i.e. the not-really-old ones) are combined heat and power plants, and because we use district heating water to create a vacuum behind the power producing turbines turbines (instead of sea water) we go from a theoretical limit on the energy efficiency of around 60% to 98%, as we do not pump out the excess heat into the sea.

Newer combined heat and power plants have an energy efficiency of around 95% to 96%. The trade of is a slightly lower vacuum, meaning less production of power. However, we can scale up heat production to reduce costs of running power plants when energy prices are low (or even negative).

It’s a CRM, not a CMS.

Neither do the buyers. No one cares about the ergonomics of enterprise applications, because the users are forced to use it.

> While I don't think he's 100% correct, I do think he raises a lot of interesting points

One of the things I got from this was that maybe we should do more to design structured interfaces instead of counting the number of clicks needed to transition to the page you're looking for.

Many enterprise applications (especially web based ones) are horrible to navigate, and some people spend most of their working days in them. It's terrible.

This sounds like the Nirvana fallacy. Just because parsing over validation is not perfect, it can still lead to significantly more maintainable code and safer and stabler system.

Pure validation has a lot of problems, namely that you have to validate the data on all levels for the invariants required at that level.

Yeah, the author mentions that too.

For me, the funny thing about this article is that I kind of had the core insight just yesterday while hacking together a cli framework, but like the author, I couldn't quite explain what I learned.

Just because it is a hard to name a concrete situation, where panic is a good survival strategy for the individual, it can not be concluded that nature is not ripe with situations, where panic saves the flock.

Also, it would seem that the panic response is evolved for the benefit of the flock, not the individual, as it spreads rapidly; if one person panics, more will follow suit.

When it comes to Haskell, this function that generates all the fibonacci numbers did it for me:

  fibs = 0 : scanl (+) 1 fibs

Cool.

Checklists work so well. A kanban board has all the same qualities if used correctly :)

You can add two new columns to your Kanban board called "Documentation" and "Documentation Review".

Then tasks cannot move to your "Done" column unless documentation is written and passes review. If you enforce column limits documentation it will also block other tasks if not completed.

As far as I understand, yes. The red shift of the light can be measured, which tells us for how long the light has traveled.

The ant and balloon analogy is really good from an intuition stand point. Great explanation! Well done :)

The light we see is from when the galaxy was closer. As the light left the galaxy and travelled towards us, the universe expanded "between" the photons and the galaxy.

Why is this comment so downvoted? I'm not american, and I was also curious about why they don't have an adress.

As far as I know, only homeless people don't have an adress in Denmark.

EDIT: Great, now I'm downvoted as well! Huzzah!

What a load of over-generalising bullshit.

I thought this was a very thought provoking talk, even if we talk nothing the speaker says for granted.

A year or so ago I had a semi-breakdown over the fact that all the best practices I stood by was more or less just a regurgitation of what some software "guru" had to say on the subject. I didn't know if it was true, but I damn sure believed it.

I believed so hard that my opinions and feelings was almost (if not entirely) religious in nature. Sure, I had some experiences with things that absolutely did not work, some techniques that worked under the specific circumstances I applied them in.

But in general? After 10 years of software development, I can't tell you why I solve a specific kind of coding problem the way I do. I can give you a lot of reasons, but only based on vague hand-wavey stuff such as feelings and experience.

Don't get me wrong; experience is really great. But it's not the same as truth. What works for me might not work for you, and vice versa. And what I believe works for me might in fact slow me down.

And there's no real way for me to know for sure.

If you are going to use my own trick and use the same dictionary against me, at least have the common decency to also use my own words against me!

Definition 1C in the link you provided lists "a means to an end" as a definition of a tool, which I explicitly mentioned code was.

So I must concur, code is a tool. But I'm adamant that it is also a liability.