eddd-ddde

Personally, any of the flash options is my default most times because it tends to perform tasks faster and with the same level of success.

Do people actually rely on their chat groups as a knowledge base? If tomorrow I come to work and all my chats are wiped I wouldn't even budge .

I see chats purely as an ephemeral way of coordination.

I think the terms are usability Vs usefulness.

Effort is not a good signal for value. Never has been. Just because someone took 10 more hours to finish a task doesn't mean they did a better job or they care more about the result.

Not sure why this is down voted.

You cannot support FOSS and then get mad when people use those freedoms to create a service that matches their ideas and philosophies.

For what reason would grammar influence whether something is true or not...

Zig is always _less_ robust than rust. Even if you have a single allocation you can always forget to free it.

Ideally websites just respect the existing media queries so you don't even have to switch!

Because making segfaults impossible is simply a better solution to playing a game of whack a mole of "crash, root cause, fix and add test for that very specific bug"?

Your macros are not implementing features, fixing bugs, and writing test cases.

This is very similar to my recent experience!

LLMs are surprisingly effective at helping you learn the "vibes" of making music and understanding various concepts.

I can run away from a knife holding psycho or fight back, a drone can fly into my bedroom. Same argument for guns really.

My flow state with AI is having 5 different conversations at the same time making good progress on all of them by giving key insight and feedback at the right times.

You can actually go super fast with the right setup and focusing only on the important details like ensuring the shape of the APIs make sense and that test quality is good.

The main benefits you get are transformations. You can leverage tooling to automate include remapping and things like that.

But it's definitely not geared towards forks, but rather mirrors with deterministic and invertible transforms.

The "supported" workflow is you keep your source of truth in either the monorepo or the external repo. Then you export the current state of the source of truth to keep the mirrors up to date. Then, since we can assume the mirrors are up to date, the inverse transform can be applied to import change requests from the mirrors.

It works well when the assumptions hold, that there isn't large divergence on either side. It can actually be largely automated.