ty-porter| blog.ty-porter.dev
All of the interesting problems in this blog come from the MLB LED scoreboard at this point I believe. My role on maintaining the project is rapidly becoming the gatekeeper of “how do we make the application more configurable” while keeping in mind that we now have a huge permutation of configuration options across hardware we don’t control. It is hard to complain, though. It really is an interesting problem to work with. For a little background, mlb-led-scoreboard is a Python-based sco...| ty-porter
This year at work there’s been a push to brush up on relational database fundamentals. I’m generally pretty good at that, so I wanted to put my skills to the test. My preferred way to learn (or upskill) a new language in the month of December? Advent of Code! I’ve done AoC for the last 5 iterations starting in 2021, spanning a few languages – starting in Ruby, then Python, then Golang last year (but I got busy and didn’t finish), to finally a mix of Python and SQL. I get really suck...| ty-porter
Other Posts in This Series Part 1: Test Timeouts Part 2: On Video Conferencing Part 3: <select> Tags Crash Chrome (You’re here!) --- I hope you enjoyed (and possibly sympathized) with the bugs in this series. Somehow, I’m the one that manages to find and diagnose a lot of these and they were interesting to debug. This last bug really wasn’t totally out of our control, but a change to the browser implementation of <select> tags uncovered a severe performance problem in our application. T...| ty-porter
Note: This is not a disparagement post. I had a good experience at WGU because I knew what I wanted to get out of my time there and where I’d need to look elsewhere for some deeper understanding. I completed the degree very quickly, and I think it’s important to be realistic about anything that seems too good to be true. My background I have written in the past about my experience attending Vanderbilt University’s coding bootcamp back in 2019. For me, it was a positive experience where ...| ty-porter
On Reddit a few days ago I read through this discussion thread regarding the article by Matt Rickard titled “Developers Should Deploy Their Own Code”. I was just the guinea pig for starting this process at the company I work for, so while the pain experience is fresh in my mind, I figured I’d jot down some thoughts. --- The Argument(s) The discussion of the article really made two points – it’s not as simple as “developers should deploy their own code”. There were two common thr...| ty-porter
Ripping out Rails in favor of a minimalist pure Ruby application.| blog.ty-porter.dev
Writing automated tests for someone else's code is kinda hard.| blog.ty-porter.dev
Part 2 on bugs that are out of our control.| blog.ty-porter.dev
A look into a few incident reports caused by Chromium.| blog.ty-porter.dev
Revisiting our dark launch pattern with lessons learned.| blog.ty-porter.dev