#dev

Accessible Buzzfeed

Post

This article was originally published on the BuzzFeed Tech Blog Header image by Devin Argenta Last month, external accessibility experts certified buzzfeed.com as compliant with the best accessibility practices for the web. That simple statement, ripped straight from the headlines of a boilerplate internal email, does not do justice to the two-year process that brought us to that point. Nor does it embody what the achievement means to our team, especially myself, on a personal level.

Names, Legal Names, and Fractally Deferred Responsibility

Highlight

I was prompted to write this article by the experience of a friend of mine who was somewhat embarrassed by having his full, legal name called out in front of a room full of people who only knew him by another name. The was the result of a software system suffering from precisely the ailment I described: someone used the ‘name’ field for the name displayed to kitchen workers who were preparing an order.

Getting off of Netlify

Post

I wanted to quickly follow up to my recent post about personal infrastructure with some updates I made this week. Why the change I got a warning last week that I was almost at the limit for my allocation of “build minutes” on Netlify. Upon investigation, I found that my personal website had been building too often and for too long on Netlify, and that soon they would start charging me for the overages.

Second-guessing the modern web

Highlight

I can, for example, guarantee that this blog is faster than any Gatsby blog (and much love to the Gatsby team) because there is nothing that a React static site can do that will make it faster than a non-React static site. — Second-guessing the modern web, Marc Wright

How this site works

Post

Note: There’s a follow up to this because I’ve since made more changes to the infrastructure of the site. Read more. I’ve been slowly moving over to self-hosting more services and trying to balance that with personal convenience. This post is a quick summary of the current setup I have running to do the following: Develop and run my personal website Cross-post certain types of content from my website to Twitter Periodically scrape a couple of proprietary services I use, to keep track of the media I’m consuming Store and serve that data along with some other personal data in an API Regularly update my personal website with the latest in my media consumption Personal website My website is built on Hugo, a static suite builder written in Go.