When you run into tough spots, it’s nice to have another person look at the problem. Rather than immediately visiting a coworker, though, I first turn to another expert:
Laying out the user interface of a mobile app (or any app for that matter) is not a simple process. As visual designs get more complex and the number of devices and screen sizes grow, the work of a mobile developer grows more challenging.
Many developers choose to leverage open source tools to help with layout or image rendering. Because those libraries evolve over time, updating to new versions can cause unexpected changes to the look and behavior of the app. That puts the burden on developers to continuously monitor their work for problems that may emerge in the UI. Read more on Continuous Validation for Mobile User Interfaces in iOS…
Objection is a dependency injection framework for Objective-C that I wrote in one day 2011 while working on an iOS project. It’s funny how a combination of frustration with existing tools and inspiration can create something of value for your company and the wider development community.
Objection turned 4 years old this year and has just recently exceed 1,000 watchers on GitHub. I never thought that Objection would to continue to grow in popularity and be updated regularly through its 4 year tenure, but I am glad it did. Read more on Objection Turns 4, Gets 1,000th Follower…
Documentation is hard. Like writing code, it is a delicate balancing act of packing information into a format that is both very dense and very readable. Going too far in either direction severely limits its usefulness.
We have a great team of six designers at Atomic Object with decades of professional experience. Collectively, We have a broad skill set ranging from branding, illustration, iconography, branding, interaction design, information architecture, product management and front-end development.
Ember Data has strong opinions on how it wants you to structure your data and your API, which are essentially collapsed into one by its default paradigm. If you are using
ActiveModelSerializer, the path of least resistance is to have your
DS.Model classes essentially mirror your ActiveRecord classes, to the point where I feel like an Ember Data app is often doing SQL over AJAX.
The broken windows theory from criminology applies to source code: If a code base has a bunch of inconsistencies and quality problems, we will take that as the norm and continue the pattern. Here are four things you can do to avoid broken windows in your code, and set a norm of quality and craftsmanship.
People who work in IT Operations know that “Everything is a DNS Problem.” Recently, a client experienced an issue where the MX records for their domain were inadvertently changed, which resulted in e-mail not being delivered. Unfortunately there was no DNS history—no record existed of what the MX records had been. The DNS entries had been set up years ago, and no one knew exactly how the system had been configured. This necessitated an investigation and analysis to determine what the records should be.
Do you like creative problem-solving? If you’ve spent more time sketching, working through details, or obsessing over technology than you would like to admit, then Software Design might be the field for you.
Over the years (and much to the delight of my customers) I’ve used story points to accurately predict when a project was going to hit its relevant milestones.
However, I’ve recently been noticing that my estimates deviated very little from user story to user story—and for good reason. The story cards tended to all be roughly the same level of complexity. Sure there were differences, but my boards were often comprised of stories predominantly of the same size.