meijer

My rule of thumb is: if it is the type of error that I want a stacktrace for: use an exception. For example: programming errors, unhandled cases etc.

If it is an error that I want to handle explicitly, for example by showing a nice user message: use a result type. It is okay to use combinators in this case, but use them wisely.

The link is NSFW.

But this doesn't handle the state. It is not working imperativ code.

So I guess this is just an opportunity for you to get rid of Stallman.

But the lynch mob is still there and defends its cancel culture. You can see them all over Twitter. They are ruthless.

Something is going wrong with the streaming market. In Germany, nobody is streaming Seinfeld!

Amazon stopped a few months ago. You just cannot watch Seinfeld online.

He did not defend Epstein.

You might have a point here.

I wish I hadn't read "Why we sleep"...

"Stoicism" got a bad rep 1700 years ago when I was defamed by Roman christians. I think it still suffers from this.

As a German, I don't like the name "Camelia" very much because it is associated with hygiene products here (brand name).

"Raku" sounds nicer for me.

> Property-based testing is very good at shifting the cost-benefit ratio of testing, because it somewhat reduces the effort to write what is effectively a larger number of tests and increases the number of defects those tests will find.

Yes, property-based testing is great. Of course, you need code that actually has some nice properties. Typically that is the case for well-designed code, so it's a win-win.

For me the point is: you should treat people well even if you don't like them. And that includes not spreading slander.

Yeah, I also noticed this.

And I'm pretty sure that some years ago gmail was much better at this.

> Do you see what's not there? Programming language competency. Database knowledge. Things like that.

I hear this a lot, but I'm not sure I agree 100%.

I want to work with people who can write idiomatic code and are able to use a database efficiently (or who are at least willing to learn these things).

Wrt to "How the Mind works": The beginning is really pretty dry, but it gets a lot more interesting in the later chapters.

There are now more completely obvious bugs in widely used software. It's like developers care less.

One could argue that such an API exists. It even understands natural language!

We probably don't remember those who were eliminated.

Well, kids need more, obviously.

But old people do not really less than young adults, according to "Why we sleep".

I hope Windows 7 will somehow live forever.

> Do python or ruby devs really feel they are less productive than java devs because they have no types?

Yes, I do.