Iterating over design that needs to be reflected in code can be tedious and time-consuming.
Typically the designer works in graphics editing software and then submits flat art to the developer who implements the design in code. Refining the design requires going through the same laborious process.
Even harder if we want to support multiple themes in our apps. How would we even approach that if we were using Interface Builder?
Let’s look at how we can approach implementing a simple library that could solve all of the above concerns.
As I open source another framework this week, I wanted to share few thoughts about building developer tools.
Developers are lazy creatures, we like to automate stuff, we write scripts, use File Automation to get rid of repetitive work.
One would think that we’d use the same principles in our jobs, yet I’m constantly surprised how few developers actually invest their time into building tools and setting up processes inside their app to ease their day to day work.
Many of us already write unit tests and run continuous integration servers, we can also leverage great tools like Danger to easily add some checks to the pull requests.
If we’d like to prevent some common mistakes from appearing in the repo in the first place, we can use pre-commit hook.
