Sasha 🐏💨 Koss

How deno_doc is that good? --json outputs data structure I always needed to render date-fns docs.

I wish I had discovered it earlier. I dread migrating the documentation website once again, but I feel it would be worth it!

I used ChessBase just a bit so it's hard for me to compare, but even Lichess Study UI is a bit nicer when it comes to annotating lines. It's good to have an open-source alternative though. I hope the author/community finds the energy to evolve it and eventually add missing features and improve UX 🙏

Anthropic's answer to GPT-5 is brutal!

If you're into chess, you'll love En Croissant: github.com/franciscoBSa...

It's a well-made cross-platform app (à la ChessBase) w/ support for multiple engines, a nice UI, and many more features useful when studying.

Consider supporting the creator at: buymeacoffee.com/franciscosal

ADRs (Architecture Decision Records) are immensely beneficial but also tedious to write when following the recommended templates. So I found myself avoiding writing them.

Now start with just bullet points to capture the essence.

Perfect is the enemy of good.

So glad to see these options enabled in the new TypeScript default config 👌

It is improving, and I think I can completely get rid of ts-expect-errors and make my tests clean ✨

Look like naive `satisifes` expressions fail most of the times.

Isn't this rad?

If you don't write complex TypeScript types, it's a test framework that checks generic results.

Here's the link to the WIP doc: github.com/kossnocorp/g...

And the tysts file I use to build it: github.com/kossnocorp/g...

I'm working on dissecting TypeScript type system to breakdown all the magic that powers the most complex generics.

Here's the assign compatibility matrix of all basic types.

And no, you can not reproduce it by adding all primitives, object and void. {} is the key 👆

www.typescriptlang.org/play/#code/C...

The reason it works this way is very fascinating!

{} is a non-nullable type and includes everything but null | undefined, so with null | undefined it mirrors unknown behavior.

So that unknown could have been expressed as:

type unknown = {} | null | undefined

Playground link: www.typescriptlang.org/play/#code/C...

Did you know about the everything type in TypeScript?

type Everything = {} | null | undefined;

It behaves not like you would expect, and you can assign anything to it, even unknown, that can only be assigned to any and itself.

And you're lucky if you have an extensive tyst suite and can catch broken types early. It's pure hell without it.

Writing advanced TypeScript generics turns into a whack-a-mole game at some point.

While I appreciate the power the type system gives me and it's wonderful what one can do with it, but I really don't enjoy how brittle it can be.

Strict function types by ahejlsberg · Pull Request #18654 · microsoft/TypeScript With this PR we introduce a --strictFunctionTypes mode in which function type parameter positions are checked contravariantly instead of bivariantly. The stricter checking applies to all function t...

I love how @typescriptlang.org issues are often are the documentation when it comes to behavior nuances.

For example, I found out that method params are checked bivariantly while function params are checked contravariantly and the explanation why is so is there: github.com/microsoft/Ty...

I just spent 5 hours straight debugging a Rust-based @Cloudflare worker panicking, and it all lead me to workers-rs using unwrap and causing a trivial deserialization error show as "Worker exceeded CPU limit."

True clusterfuck 🫠

The culprit: github.com/cloudflare/w...

It is mind-blowing that this tiny board runs Linux

🤯 You can merge namespace declarations in TS!

I didn't realize how off my world physics intuition until I tried to internalize how electrical resistance works.

I have my own typed versions of `useMemo` and `useCallback`, so that I can check if I didn't accidentally pass an unstable reference as an argument (where it matters).

It would be great to have typed `useEffect` dependencies too.

I think it must be in React types btw!

For the first time, used the TS interface merging feature and I think I'm so clever 😎

Nix and NixOS are great and sound great, but not for everyone. Not for me, certainly.

I like learning but, not when I have to do it, to make any progress.

After six months using NixOS for reproducible development environments, I'm giving up. The last drop was trying to make it work with embedded development (ESP32, Rust, WSL2).

Switched to Dev Containers and couldn't be happier.

Update: It doesn't work for runtime due to `ReferenceError: Self is not defined`.

Still good for types, though.

Is `import Self = BlueprintPromptController;` a cursed hack or a genius idea? 🤔

I love it, personally, and proud that I discovered it.

I'm considering moving from the pattern of defining `ComponentNameProps` to using namespaces `ComponentName.Props`.

1) Name pool is smaller.
2) I can add more component types when needed.
3) Single import vs. multiple.

Y'all hate namespaces, tell me why it's a bad idea.

TIL there's very handy "TypeScript: Find File References" VS Code command

It is still funny that removing fishing/scum tweets is the main Twitter Premium feature.