Back when I was working on slide-element, I noticed an issue that would occur when I rapidly toggled an element open & closed. If the previous animation wasn’t allowed to finish, the new one would eventually get outta whack, clipping the content on subsequent animations.The Cause of the WeirdnessThis was
Read ItA while ago, I wrote a premium WordPress plugin for creating typewriter effects with TypeIt via shortcode or Gutenblock. I was ill-prepared for the trickiness of managing plugin updates for such a plugin. Since a premium plugin is monetized, it can’t live inside the WordPress Plugin Repository like free options
Read ItThere’s a certain number of JavaScript features that I’ve never really used and find highly intimidating. Bitwise operators are among them.These operators exist for manipulating binary representations of data, and for the type of work I usually do, I’ve never met a scenario when I’ve needed to dive into nitty-gritty
Read ItA project of mine recently needed a simple FTP server that can give multiple different users access to the contents of specific directories (and only those directories). My technical requirements were stupid simple, the data I’d be dealing with wasn’t sensitive, and I wanted to avoid paying for an expensive
Read ItGuidelines for Pushing the Technological Envelope While Validating New Business Ventures
Read ItIt’s difficult to overstate the value of GitHub Actions in automating tasks we previously had to perform manually – deploying WordPress sites included. Recently, I was tasked with setting up a WordPress repository to automatically deploy to a WP Engine environment whenever a commit is made to a particular branch.
Read ItImagine we have some JavaScript on a page that updates an element’s contents and immediately logs those contents out: After loading the page, you’d correctly expect that “updated text” will be displayed on the screen. And when it’s exposed via
Read ItAnd a Couple of Challenges I've Seen Too
Read ItA while back, I began contributing to a small JavaScript library responsible for sending a POST request with some data to an endpoint. At the time, it used axios to make that request, and I wanted to simplify things by shedding a dependency. The obvious alternative was fetch – modern,
Read ItA post on behalf of my team about why growing in your craft requires writing more than just code.
Read ItA guest post on CSS Tricks in which I explore some of the times you might consider using “old school” approaches in JavaScript in order to avoid particularly heavy Babel transformations.
Read ItModern iterations of JavaScript have introduced some nice methods that make writing code a lot more legible, performant, and fun to write. Take, for example, the find() method on the Array prototype, which allows you to elegantly retrieve the first item in an array that meets some condition.const players =
Read ItA while back, I started working in a Rails application in which I needed to introduce a JavaScript file that’d be compiled with Webpacker. To do so, I created the file in my packs directory and loaded it up via content_for: <% content_for(: body_assets) do %> <%= javascript_pack_tag("some-file") %><% end %>Locally,
Read ItI’m writing a Gutenberg block for TypeIt that’ll allow content creators to easily drop typewriter effects into WordPress. The Gutenberg infrastructure is heavily rooted in the React ecosystem, so building a block feels very much like building a React application.One piece of this ecosystem that’s new to me, however, is
Read ItI’ve been seeing my preference change in how I write simple conditional statements in JavaScript. Consider the following: if (snack) { eat(snack);}Back in the day, that’s how just about every “if I have this, then do this” statement looked. As complexity and context changed, I might have pivoted a bit,
Read It