In the afternoon we went to the birthday party of my sister-in-law. Her daughter has a nice black-and-white cat called Puck. I took a few photos of Puck and picked the one below for this blog.
She has grown a lot; compare with photos I took the 12th of July 2020.
I’ve come across a lot of websites in my career (and in daily browsing) that are straight-up inaccessible. If you’ve ever worked on a project that is riddled with accessibility issues, you’ll know that fixing these problems is a mammoth task - it needs time, it needs people, it needs prioritisation… it costs money, basically. As I mentioned in my blog post 7 myths designers and developers believe about web accessibility, retrofitting accessibility is hard.
The key is to start out with the right tools for the job - or rather, the right tags for the job. In every website, underneath the layers of CSS, the bloated frameworks, the 45945 API calls, there’s good old HTML, and that’s the key to accessible websites. Specifically, semantic HTML.
Source: The right tag for the job: why you should use semantic HTML, an article by Sophie Koonin.
I’ve been a NetBSD developer for three years and it’s been my primary operating system for a long time too - on everything: routers, laptops, Raspberry Pis, PowerPC mac minis, Vortex86 embedded boards, and servers.
I’ve recently been using FreeBSD a lot at work. We have a lot of servers and embedded boards running it, and I was given the option of installing anything I wanted on my workstation. I chose FreeBSD to maintain a separation of BSDs between my work and home life ;)
I thought I’d write a little bit about some differences that stand out to me. Since everyone that knows me well knows that typical use cases like web hosting aren’t really my jam, and I’m more of an embedded, audio, and graphics person, maybe I can offer a more uncommon perspective.