Category: LexBlog

  • Working Remotely in Anchorage, Alaska

    My morning routine is sacrosanct. Every day, I wake up at the same time, drink the exact same amount of coffee (which is usually just a little too much), take the same bus, and settle into work. I find a great deal of comfort in this routine, which is why the lack of shock to […]

  • Overcoming the Trough of Sorrow

    Before I dive in, I should note that this post was written as LexBlog hits its fifteenth birthday. It’s been my pleasure to work in the Seattle offices at LexBlog for over 6 years. So much of that pleasure stems from truly enjoying the people that work here and overcoming the challenges we face on […]

  • Trials and Tribulations with Gutenberg

    I should note that I continue to remain positive about the direction of the Gutenberg project (the new WordPress editor, coming to you as of WordPress 5.0). My feelings on this are numerous and expansive, but the long and short of it is that I believe WordPress core needs a major shakeup to help the […]

  • Investigating New Options for Search on LexBlog.com

    Updating LexBlog.com’s aggregation engine was no small feat. Scott Fennell and I spent months testing all of the various components of our new aggregation engine that powers the vast majority of the site, but something that was hard to prepare for was the shear scale of the site. Now that it’s up an running, we’re […]

  • RSS Doesn’t Stand for “Really Should be Standard”, but Maybe It Should

    Like many technical specifications on the web, RSS (which stands for Rich Site Summary or Really Simple Syndication depending on who you talk to) has a confusing history that seems to only get more confusing as time goes on. The format became popular in the late 1990’s as the need to standardize information held on websites became a pressing concern with the rise of blogging and dynamic websites. The influx of information and content, all organized in different ways, was exciting, but without a standard way to consume the content, you were left with just a few options:

  • Make Technology for Humans

    Engineers make hardware and software for humans. It should go without saying, but remembering and staying true to that axiom is complicated depending on where you’re standing. With each passing year, it seems that things get more complicated, more random, more uncertain. This year was no different, especially in the realm of technology. Facebook and Twitter […]

  • LXBN as the New LexBlog

    Over the past few days, the Product team at LexBlog has been busy launching a few bodies of work that have been a long time coming. While our Success team launches sites and solutions on a hourly basis, the product side of LexBlog has the luxury of spending weeks, sometimes months, working on new features […]

  • LexBlog is Moving to WeWork

    In my time at LexBlog, I’ve seen three different office buildings and worked in two. The first LexBlog offices where my first “real” desk job began was on 95 South Jackson Street in Pioneer Square. The building was near the waterfront, and a stone’s throw away from the Seattle Ferry Terminal. Our CEO, Kevin O’Keefe […]

  • Gutenberg – The Future of WordPress’s Post Editor

    This post was written using Gutenberg, the code name for the WordPress core team’s effort to overhaul the WordPress post editor. One of the things that we strive to do at LexBlog is help data drive decision making processes. The fetishization of data in business is somewhat akin to the fetishization for new specs and […]

  • Building a Visual Regression Testing Application Using React, Selenium, Node.js, and the WordPress REST API

    At LexBlog, my team is responsible for keeping a lot of sites up and running. We help manage the reputation of lawyers and law firms, where each pixel matters. As a result, our product team performs a host of functional tests before launching updates, and we lean on test driven development practices to catch things that […]