You appear to be offline, some content may be unavailable.
Senior Front-end Developer
Scott Vandehey is a front-end architect and CSS specialist in Portland, Oregon with over 20 years experience building scalable user interfaces. His specialty is refactoring large code bases for maintainability and performance, and helping teams define best practices and workflow around CSS development. Between his education in graphic design and his experience working alongside programmers, he bridges the gap between design and development.
A running theme in his career has been helping others level up, and that’s most recently manifested in the Friday Front-End and CSS Basics twitter accounts and newsletter, which he uses to share development tips and links with the front-end community every day. His first book, “How to Find a Better Job in Tech,” was published in 2016.
You can learn more at spaceninja.com, and follow him on twitter at @spaceninja.
On a recent client project, we built a form that submitted to a third-party registration service. Easy-peasy, right? What followed was a comical series of incidents that served as an excellent lesson in defensive API handling.
For a recent project, we needed to take a small web application and embed it inside a client’s existing site. Typically, this means inheriting the site’s styles. However, in this case, the client wanted this…
A friend recently shared his frustration with CSS development. I responded to him with a high-level overview of the current state of CSS. If you’re feeling a bit out of touch with modern CSS development, I hope this helps. You’d be surprised how much you can do with vanilla CSS nowadays!
Timber's resize filters don't play nicely with the Cloudinary WordPress plugin. We added our own custom image optimizer function that check if an image is served from Cloudinary or WordPress and use the appropriate resize method.
You may have heard that you should be “linting” your code. What does that mean? Why would you want to do it?
It’s no secret around the office that I’m a bit of a process wonk. In the past, I’ve been certified as a scrum master, and I have opinions about agile workflows. So it may surprise…
If you’ve ever had to review a PR where the only code change is adding a wrapper element, you’ll be familiar with the pain of reviewing what appears to be a massive change but is actually trivial.
The responsive images spec is fantastic and covers a lot of use cases, but most of the time you’ll only need one: resolution switching using the `srcset` and `sizes` attributes.
What’s typically involved in an npm version release? How can you determine the release process for an existing project? Can project maintainers do anything to make it easier for new contributors?
One frustrating aspect of the modern JavaScript ecosystem is keeping all your dependencies up to date. Thankfully, there are automated tools that can handle this thankless task for you.
Presented at pdxFLIT, Devsigner 2016