lebuin

It does sounds somewhat reasonable on paper. But some of the crosswalk buttons in Belgium have this as well, and it's really jarring. You press the button, see the light go on and look away to look at the traffic light and wait for it to turn green. Except 20 seconds later you look back and the indicator light is off again. I feel very strongly that the indicator light should only turn on when your press has been registered.

Let's say you tell someone to do something, and they say "ok". But when you ask them later whether they did, they say "oh no, I just said ok to indicate that I heard you, not that I was going to do something about it." That doesn't make any sense. The indicator light has the same function. Going on and then off again is a violation of basic communication protocol.

Does it list itself?

Apple has been required by the DMA to accept non-webkit browsers in the EU for 2 years now. But in practice no one has built one. There are some claims about malicious compliance on Apple's part (what else is new), but it seems equally likely to me that no one wants to maintain 2 rendering engines for the same app (1 for EU and 1 for the rest of the world).

I try to leave my laptop untouched for as much as I possibly can. Definitely makes me feel better too.

The argument is based on one of these companies hitting the singularity, making it impossible for any other company to catch up ever. I still think it's way more likely we'll see a typical S-curve where innovation starts to plateau. But even a small chance of it happening in the future is worth a lot of money today.

You should distinguish between residents and visitors. In Belgium, and I believe in many other European cities, street parking for residents is extremely cheap or free.

You can also click the address bar and then press you shortcut. Should be faster and works for all shortcuts AFAIK.

I'd argue that LLMs are not yet capable of the last step, and because most sufficiently large AI-generated codebase are an unmaintainable mess, it's also very hard for a human developer to take over and go the last mile.

God yes. For some reason, I automatically scroll in such a way that I always keep what I'm reading at the very top of the screen. Which means that every time I want to reread a sentence I first have to scroll past the header.

I'm building web-based CAD software for woodworkers. Not a plugin, I'm starting from scratch. I'm aiming for it to be intuitive for non-technical users (think SketchUp), while also offering some of the more powerful tools of "proper" CAD tailored for woodworking: simple parametric workflows, cutting layout optimization, built-in tools like chamfers and joints,...

https://maqet.app

If you are using webpack, see if you can make the switch to turbopack. It cut my build times from ~1 minute to 15 seconds, incremental builds are down from 10 seconds to 2. Memory usage is down a ton as well. But if you rely on webpack plugins this may not be an option for you.

For me, the answer to this question is: parts that involve no architectural decisions, and that won't need to be extended or built upon significantly in the future.

When I'm working on a greenfield project that I intend to build out further (which is what I am currently doing), I find that there's not a lot of work that fits those criteria. I expect that can change drastically when you're working on something that is either more mature, or more narrowly scoped (and thus won't need to be extended too much, meaning poor architectural decisions are not a big issue).

I had to do a fresh install on a 2015 iMac. Same problems with the SSL certificates. I found it rather shocking that a 10 year old computer cannot be booted anymore, and as far as I understand it it's mostly because apple chooses to serve certificates with poor backwards compatibility on a domain that is used for updates, which is just lazy.

I think OP may be referring to the idea that the total number of calories burned in a day doesn't meaningfully change under a workout regime. Working out does burn calories, but after a few session your body starts to compensate by burning less calories in other areas (e.g. immune and reproductive system). The net result is close to zero, except in very demanding workout regimes.

I don't have the background to fully evaluate how true that is. I read "Burn" by Herman Pontzer, which at least makes a very good case for it.

It seems like LLMs in general still have a very hard time with the concepts of "doubt" and "uncertainty". In the early days this was very visible in the form of hallucinations, but it feels like they fixed that mostly by having better internal fact-checking. The underlying problem of treating assumptions as truth is still there, just hidden better.

Exactly. The fact that an LLM isn't very good at helping you fix basic organizational issues like this is emblematic. Quoting the article: "We have automated coding, but not software engineering."

There's also no canonical way to write software, so in that sense generating code is more similar to coming up with a potato soup recipe than compiling code.