Which also fits with how it performs at software engineering (in my experience). Great at boilerplate code, tests, simple tutorials, common puzzles but bad at novel and complex things.
TDD is opposed to suffering orientated programming IMO.
What pain does writing the tests first resolve? Tests should only be added when you are scared of making changes or want to support assumptions about how things work.
I have seen this first hand with Bazel. You have lots of Bazel rules that are partial reimplementations of the language specific tooling. It usually works better - until you hit a feature that isn’t supported.
Not a search engineer, but wouldn’t a cache lookup to a previous LLM result be faster than a conventional free text search over the indexed websites? Seems like this could save money whilst delivering better results?
This is too simple. Prices float somewhere between cost to produce and value to consumers.
You can’t raise prices beyond value or no one will buy it.
You can’t lower prices below costs (for too long) or you go out of business.
Competition pushes prices down towards costs.
Therefore businesses are always looking for markets with barriers so they can rise prices to value.
Tariffs typically raise costs for all producers, but this only inevitably leads to price increases when competition has driven prices down to near costs.
Unfortunately many staple grocery products fall into this category.
What if people are manipulated by bot farms and think tanks and talking points supported by those corporations?
I think this view of humans - that they look at all the available information and then make calm decisions in their own interests - is simply wrong. We are manipulated all the damn time. I struggle to go to the supermarket without buying excess sugar. The biggest corporations in the world grew fat off showing us products to impulse buy before our more rational brain functions could stop us. We are not a little pilot in a meat vessel.
Well I don’t know what issue you have with whitespace, but the usual complaint is that programs with small typos are syntactically valid but logically incorrect. This is why CoffeeScript became so disliked. A static type checker makes this scenario much less likely since it won’t compile.
I would also add that F# has some indentation rules (“offside rules”) and tabs are disallowed, further shrinking the input space.