Some of the best and most useful things we build have humble beginnings. Small side projects start with a sapling of an idea—something that can be built in a weekend, but will make our work a little easier, our lives a little better.
As an industry, we’re historically terrible at drawing lines between things, except when it comes to our roles. The old thinking of defined roles is certainly loosening up, but we still have a long way to go.
There are some simple JavaScript design patterns that developers of any level can start using to improve their code. These aren’t process-altering changes—just minor tweaks that make code more reusable, extensible, and understandable.
You can’t be at the top of your game while stressed and nervous about the emergency, so unless there’s an obvious, quick-to-deploy resolution, you need to give yourself some cover to work.
“Just” implies that all of the thinking behind a feature or system has been done. Even worse, it implies that all of the decisions that will have to be made in the course of development have already been discovered—and that’s never the case.
Today's Topic: Packing for Travel. The origin story of the podcast is revealed. The hosts also discuss various packing methods, emergency socks and underwear and how to deal with dirty laundry while traveling.
There’s a constant tension between that type of longform, art-directed content and content management systems. New tools like Craft’s Matrix field give developers the control they need to achieve such beautiful layouts.
Craft’s Matrix is a game changer in the age-old battle between art-directed content and WYSIWYG editors. Matrix blocks, together with Twig’s template inheritance and multiple includes, provides us incredible power and flexibility within our templates.
Apple has always had a funny relationship with responsive design. At last week’s WWDC, they finished laying the foundation of responsive design within native applications.
We talk about Apple finally adopting adaptive & responsive design and riff on the paradox of choice, the impact of Swift of programming education and "web vs. native" being the wrong outlook.
As the back-end developer on this project, I focused on the CMS-side of things. We built out a fresh ExpressionEngine instance to handle all of the Foundation’s content publishing needs. Strong search functionality was key to the success of the project, so we customized a Solr install, and integrated it with the ExpressionEngine environment.
Developers have a love/hate relationship with styled form elements. It’s fine when the interactions are simple, but what happenswhen things get a little more complex?