You can always ask it to nudge you in the right direction instead of giving the solution right away. I suspect this way of using it is not very popular though.

This is not a new problem I think. How do you use Google, translator, (even dictionaries!), etc without "degenerating" your own abilities?

If you're not careful and always rely on them as a crutch, they'll remain just that; without actually "incrementing" you.

I think this is a very good question. How should we actually be using our tools such that we're not degenerating, but growing instead?

> How do you use Google, translator, (even dictionaries!), etc without "degenerating" your own abilities?

By writing down every foreign word/phrase that I don't know, and adding a card for it to my cramming card box.

And oftentimes some endpoints simply hit the max URL length limit and need a proper body. I thought we ought to already be using this method. Seems quite fitting for fulfilling GETs with bodies.

I was going to say that. Gratitude to the creators of fish shell. The history-based rank is immediate as you type. Lately I've simply done:

abbr --add c cd

And then the "most used paths" are just present in the history filtered by the prefix I already typed.

For awareness, if you want to build a SSG/SSR frontend, there's also [Astro](https://astro.build/)

It lets you ship client islands to the client, which AFAIK is essentially partial hydration.

You can make islands with pretty much any JS framework or even none e.g. Web Components

Katie Sylor-Miller named them when she was at Etsy and from memory they were React components in a PHP page to start

> When using npm, all dependencies for a project are installed in a single node_modules directory. This means that if two packages depend on different versions of the same package, the one that is installed last will be used, which can lead to compatibility issues. This is known as "dependency hell" and can make it difficult to manage the dependencies of a project.

> pnpm's symlink feature addresses this problem by allowing different versions of the same package to be installed side-by-side, and linking them to their dependents through symlinks. This helps to ensure that the correct version of a package is used for each dependent, reducing the chances of compatibility issues and making it easier to manage dependencies.

From the last issue linked in the PR (https://github.com/oven-sh/bun/issues/1760)

Empty is not the same as succinct & straight to the points. I'd say strong title, succint content. Each of the points invites as much thought as you can give it.

Content is left as an exercise to the readers.

I think he's proposing a fix for the regex in the title.

/(ab?)using/ matches:

- ausing

- abusing

while /(ab)?using/ matches:

- using

- abusing

That was a nice read. Do you recommend any books for one who wants to get into queue theory?

Greatly appreciate these tips! I'll apply most of them, especially the diff ones.

This is awesome! It's a great aid in understanding the protocol.