Shared bookmarks

I'm learning Podman and Systemd integration! Very helpful guide

TIL you can tell Postgres that it's running on NVMe drive where parallel random reads are very cheap

I started noticing the corporate "we" everywhere at some point and to my delight it's actually called that!

I definitely needed to read this! The article helped me to reconcile my overall positive sentiment towards Go with my dissatisfaction with the lackluster type system and some implementation choices.

This is the kind of article that makes you think. UI paradigms and tools come and go, there's a new paradigm every so often, claiming to solve the problems of the previous ones, and it's so painful to hear how "innovation" brings a lot of regressions for users who benefit from accessible solutions the most. Doubly painful when coming from someone really passionate about Linux.

This piece very accurately reflects my current sentiment towards smart home appliances which effectively cools down any automation ideas...

Short, non-controversial and easily applicable set of advice!

I can relate to parts of this article. Mastodon isn’t what I expected but I have different expectations from it, perhaps something I should write as a separate post.

Intuitive explanation of BFF and view-models.

Came up in a discussion about ReDoS vulnerabilities.

The post has aged like good cheese: since 2015 we've moved on from callback syntax to async/await, but the debate about advantages and disadvantages of futures and microthreads remains open and this is a fantastic, clear way to picture it (even if opinionated in one direction).

I haven't implemented bidirectional BFS but now I kind of want to, I didn't realize how much improvement it can be. Also the trick with starting the next step from the "narrower side" makes a lot of intuitive sense.

The reference I didn't know I needed! Even though I'd typically use converters, the compatibility chart is extremely helpful to have.

I had no idea that the famous quote "free flow of information is the only safeguard against tyranny" is attributed to a fictional character from a classic computer game! Many more gems are to be found here.

Just bumped into this problem, very positively surprised how helpful an answer I was able to find!

I was surprised to see such a throwback to the classic PHP article. I can see a value in this article because it brings attention to a lot of gotchas and inconsistencies in the language that we should be aware of; I especially appreciate a good summary of inconsistencies around zero values. However there's a different point to be made here: Golang feels like a successful language to me. It has a purpose and fits this purpose really well. There's a lot of amazing pieces of software that I use regularly that Golang made possible. Maybe this means we should appreciate Go not as a "overall well designed language" but as a language that successfully solved a problem back when a compiled language with great tooling, concurrency and modules wasn't so readily accessible? This reminds me of how PHP successfully solved another important problem, despite its language design problems.

Surprised to see Go use more memory than Java in some benchmarks!

The thing that surprised me most about this article is how much ongoing effort there is to "upgrade" C++ to match the modern set of expectations, and how much friction it seems to face. I wasn't familiar with the historical events like the big ABI vote, so lots of learning here.

This article is like a box of chocolates! There's some quality-of-life tips, some best practices tips and some performance tips. I wish I knew earlier about \pset null '[NULL]'...

Great piece about leaving "breadcrumbs" that will help you revisit your past creations. A fantastic zero-effort alternative to writing a blog post about everything :-)