JoeNr76

I never said that you should prefer 3 star restaurant. I was responding to the specific claim that home cooked meals are always better than eating out.

What you find regrettable is your problem, not mine.

If I invite people, I do it for the people, if I go out to eat I do it for the food. I don't see why this regrettable just because you think it is.

> I think nobody in my country would say going out to eat is better than eating at home.

You haven't eaten at a 2 or 3 star restaurant then. They use ingredients you don't have access too, using techniques you can't use at home and pair them with wines or juices you haven't heard about.

However good you think your home cooking is (I think I'm a fairly good cook), you don't come to the knees of a chef with such a restaurant.

Yes, they are not cheap. But neither is buying a bigger house.

And if it's about getting together, who cooked the food doesn't matter. Or even get together without food, that works too.

Completely anecdotally:

I am 46yo. And I was in a reading slump for most of my fourties. I used to be an avid reader until I became a father and my 3 children began taking up more of my time. And I got a shorter attention span too.

I signed up for TT because my eldest child wanted an account and I wanted to see what he was sharing and seeing. He abandoned his account quite quickly, but I found fantasy booktok. And the Tiktokers' youthful enthusiasm was a big part of what got me out of my years-long reading slump.

I doubt if this happens often enough to be industry changing, but it does happen, even for someone very much outside the Tiktok demographic.

As an aside: where it does seem to have an influence is more people in the Dutch language zone reading books in English. I have been reading in English since I was 12 and at the time many people thought that was crazy. But nowadays every bookshop has a wall full of English Fantasy en YA books.

You can use verbs passively to do something on something else. Or you can have your program or process do it. Logically, I see no difference between:

"The HandlerCreationFactory created a Handler based on the Request." (oop)

"A Handler is created based on the Request." (passive) or "The program (or process) creates a Handler based on the Request. "

Only that the first one needs a lot more nouns, even when they look silly.

It only targets big "platform providers" not startups. It even levels the playing field for those startups. People get so ideologically tangled that they just knee jerk.

In the case of iMessage, Apple has a competitive advantage that stifles competition, not enhances it.

Setting a baseline for interoperability is not the same as requiring them all to be the same.

Not just that, it's removing barriers for competition. Which is what good regulations is all about. (and, technically it more than just bubble color, it's also including everyone in group chats)

Even after all these years, people still have this misconception about TTD. No idea where it came from.

No, it was earlier. I was subscribed to this Dogbert newsletter and it was increasingly obvious that he was not as logical as he thought he was. Like really believing in positive affirmations because he did a good exam after doing them.

translated: Never complain, proles, just be glad you get some scraps from that ever-growing economy. Even if it's less than your parents.

The only questionable part is end-to-end encryption. I don't see how you can make your messaging apps interoperable and have E2E encryption.

Most of the other things: mostly good. Apple and Google need to be taken down a peg or 10.

The article is wrong. I don't get how this could make it to the top.

It has nothing to do with greenhouse emissions, but with nitrogen compound emission. See https://www.dutchnews.nl/features/2022/06/whats-all-the-fuss... (the first english source I could find)

The source is mostly cattle. Which doesn't make up for Ukrainian grain.

yes. When I get called in as a senior consultant for some business app, it's always for the same reason: development speed has crawled to an almost stop. And it is always caused by unnecessary complexity.

I blame the fact that design patterns and specific architectures are being taught to people who don't understand the problem those things are trying to solve and just apply them everywhere.

Any senior dev or architect should always live by this maxim: make it as simple as possible.

Limits on free speech by government is dangerous. Private companies enforcing rules you have agreed to when you became a member, is something completely different.

Wild speculation with a sprinkle of logic (garbage assumptions lead to garbage conclusions)

HOWEVER, I have skimmed through it by now and the last paragraph is actually quite good. It takes a while to get there and the chosen examples aren't great, though.

As others have said: you need to think about your functionality as a public API. How the API works under the hood shouldn't affect your tests.

So how do you test private methods? You don't, with the exception of testing during development, but those aren supposed to be kept around.

I stopped reading right here:

"Considering the factors mentioned above, we can reason that unit tests are only useful to verify pure business logic inside of a given function."

That just isn't true and it makes the rest of the blogpost also not true.

A unit test should test "a unit of functionality" not just a method or a class. Your unit tests also shouldn't be coupled to the implementation of your unit of functionality. If you are making classes or methods public because you want to unit test them, you're doing it wrong.

The exception is maybe those tests you are writing while you're doing the coding. But you don't have to keep them around as they are.

Nah. EBM does explain the obesity crisis. We're just eating more.

The average American consumes more than 3,600 calories daily – a 24% increase from 1961, when the average was just 2,880 calories.

And that's just the average.

That's why the scientific literature uses the better term "ultra-processed" to mark the difference between, say a loaf of bread and a chicken nugget.

This is already 6 years old:https://cei.org/blog/study-wounds-the-carbohydrate-insulin-t...

Basically, as long as proteine is controlled for, there is no long term fat-loss difference between dietary compositions.

See here for a longer and more recent explanation: https://www.performancelab.com/blogs/nutrition/carbohydrate-...

Why are we still talking about the CIM? It failed practically every test we threw at it. Sure low carb diets can make you lose weight, but that's because you eat less, not because of insuline.

Of course. Becoming a milionaire because your dad gave you a million is not what people understand as being meritocratic.

They already get a lot of advantages during their life because of the position and wealth of their parents.

Is it bad to leave things for your kids? Nope, it's completelhy natural. But you can't claim that the society where that happens is a meritocracy.

Real strict type checking (as in, eg, Haskell ) does indeed make your code resistant to a certain type of bug. But the kind of type checking Typescript gives you is mostly useful as autocomplete.

(and, if I'm not mistaken, at run time, you can still add or remove properties from an object and re-introduce bugs. Which can happen with 3rd party libraries, for example.)

This was my main reason to switch to mainly front-end: to get away from clunky, badly written C# and Java back-end programming. 2/3 of a code file are just the coder wrangling the OOP typesystem instead of just coding the functionality that is needed.

I do like Typescript if you just use it minimally: you can type (I prefer interfaces usually) argument types and rely on the compiler to infer types.

But then the OOP fundamentalists got their hands on it and now they want strict type checking and believe that it makes their code bulletproof https://indepth.dev/posts/1402/bulletproof-angular

Well, I don't see why developing an application for transforming csv files to xls files would go faster than developing an application that uploaded csv files to a database.

I could see that i could be a rush job problem, but in this case they're not gaining any time.

It might start out as a function, then become a factory, then an object and if you bind your test to the implementation details of this code, you will have to rewrite your test every time you refactor your code. Not ideal.

"The smallest amount of testable code. Often a single method/function,"

I hate (HAAAAATE) that definition of unit test. That's how some IDEs implemented unit tests, but it's not what was originally meant with the term 'unit'

The unit tests the author means has no value outside testing while you are programming the code. For real value, unit tests shouldn't be bound to the implementation of your code.

Unit tests should test a "unit of functionality", not a technical part of the code.

I've been doing Angular for 5+ years now. I think you might be using it wrong because I never experienced anything like that.

I do. Are you asking?