Aside from that, I'll be doing one thing I don't normally do much of over the weekend, and that's some $DAYJOB work. I'm working on some experiments with the OBO (On Behalf Of)[2] login flow with Azure Entra, and since I'll be on PTO most of next week, I'm trying to finish things up, at least to a point where I can cleanly hand it over to a co-worker to finish this coming week.
[1]: https://direct.mit.edu/books/edited-volume/2224/The-Analogic...
[2]: https://learn.microsoft.com/en-us/entra/identity-platform/v2...
https://www.inclusivecolors.com/
I'm working on an article about how to develop an intuition behind the WCAG color contrast rules so you can spot good and bad contrast by eye instead of getting surprised by contrast checker tools. And how to solve color contrast problems like what to do when two colors don't contrast and what to do when your primary/brand color won't contrast for links and buttons.
After speaking to a few designers, I find most people want to follow the WCAG rules but get stuck going in circles not knowing how to navigate color contrast issues e.g. when changing one color throws another one off, or they have to use certain brand colors that don't have good contrast. Since working on my palette designer, I developed a lot of intuition in this area so wanted to share what I learned.
Spending time in the gym and spending time with my wife.
2) TurboStitchGIF: A fast, header-only C GIF decoder without dynamic allocations, ideal for embedded systems and cross-platform projects. https://github.com/Ferki-git-creator/TurboStitchGIF-HeaderOn...
My family - they're coming to visit for a few days
My health - evaluating what's been working for weight loss, charting my progress.
The idea is to give it a task, let it do whatever it decides and expect to produce a result *inside container*. I'm still exploring this idea whether it makes sense, and is cost effective.
Probably overthink buying a mini PC to run Ubuntu on to do homelab like things, like running n8n or other docker images on like plex. Then probably abandon the idea and watch something off a streaming service, lol.
Given a database[1] and a set of DDL statements/migrations you want to check, pglockanalyze will open a transaction, execute the statements, read the pg_locks view to analyze the locks they acquire and rollback (or commit, depending on the flags you passed) the transaction. Then, it will output the results for each statement.
I think there's merit in this idea, that said it's very much an experiment so there could be flaws and/or corner cases that this strategy won't work well for.
It's meant to act as a complement, not a replacement, to things like static analysis and the official Postgres docs.
https://github.com/agis/pglockanalyze
[1] typically an ephemeral database spawned by your CI pipeline