Adjusting slightly how you use types, you can get code that's easier to maintain, test and reason about.
You can run Flatpak apps on a separate data folder to allow separate instances of the same app, better isolation of personal/work data, and more. Here's how...
If you're trying to run a binary/app on your Mac and you don't seem to be able to because of a missing verification, this tip may help you.
You can use slightly different types than you would normally use to get stricter assurances on your data.
Checking that your program works is essential, in this post I'll show you how you can make sure that your app behaves as expected writing tests that will run in a blink instead of having to manually test the app trying every use case.
Using async functions we can make our code easier to read and maintain, on this article I'll show you how I refactored real world code.
I need/want to query our GraphQL data using hooks but official Apollo support is not ready yet, so I wrote a custom hook to unblock our work until the official hooks are ready.
Sometimes we deal with deeply nested objects and we need to add extra checks to prevent our app from breaking while trying to access undefined parts of that object. Here's a not so usual way of doing so.