For those of you that make decisions based on hierarchy, composition, and usability (read Designers) Apple gave us a great tool without even knowing it.
tl;dr: Go to Settings > General > Accessibility > Grayscale: On. Continue reading …
Chris Egy Rose and Patty Chang came to Carbon Five in spring of 2012 with an exciting new concept around facilitating human interaction and connected learning. The idea was to allow young people to connect with their friends, classmates and families through face-to-face interactions and a shared canvas. The interactive canvas overlay allows participants to use simple tools to create and draw with one another. The initial ten-week engagement happily turned into a rewarding long term partnership that shepherded the product and team through many iterations over many months, resulting in an outstanding, feature rich set of products.
Scoot & Doodle’s Scoodle Jam is featured in the Education section of the app store.
I am writing this to explore the following line of thought:
I will be exploring this in two major sections. The first will describe why flexibility matters. The second will prescribe a possible solution: Kanban. Get comfortable, this post is a little long.
Continue reading …
It was about a year ago that we first announced Raygun, our Rails applications generator. Since then, many apps have been zapped into existence, both internally at Carbon Five and in the wild. Raygun evolved over the year; it does more of some things and less of others. Let’s see what Raygun does and what has changed…
Raygun is a command-line tool, installed as a gem, that generates new Rails apps with a bunch of tweaks, settings, and other time-saving enhancements. It bakes in the libraries and recipes we find useful when building Rails apps. Rather than including everything we might need, it provides a foundation that, by and large, is applicable to most projects.
Raygun also serves as living documentation of our conventions at Carbon Five. Changes are made via pull requests, where people propose ideas and others chime in with their thoughts. It evolves in small ways all the time, as our preferences and the available tools change.
Last night I had the opportunity to do a dry run of my talk for the Flowcon conference coming up this November 1st at the Lean UX SF Meetup. The event was hosted at WeWork which has a beautiful office conveniently right around the corner from ours. Thanks to great promotion by Mike Long and Niley Barros, we had a sell-out crowd which at one point resulted in a line out the door. The folks from WeWork and the Flowcon conference, which was sponsoring the Meetup, were incredibly helpful and accommodating and we packed everyone in that we could fit.
Getting in front of a room that crowded had me battling quite a few nervous jitters but the friendly, enthusiastic faces in the crowd brought a ton of great energy. By the end of the night I realized how inspiring it can be just sharing stories with people about the work that we are all doing. I know that personally it always serves to refocus my efforts and ensure I’m on top of my discipline going into work the next day.
Last week at lunch I found myself using a plate of beans and rice to explain the basic tenants of MVP. This got me thinking. Could you take a basic burrito and use it as a metaphor for a software product? What if your software product was a burrito? What kind of burrito would it be? The burrito analogy actually started to work; so much so that I took some time to organize my thoughts a little more and wrote the first of 3 posts about my thoughts on process here at C5. Additionally, it seemed fitting that I should at least list my favorite burritos currently in the greater Mission District here in San Francisco. More on that later.
Spend some time this spring in Manhattan learning from 25 designers, innovators, entrepreneurs, and at least a couple developers at the LeanUX NYC conference. TLC Labs and Lean Startup Machine have partnered with NYU Stern’s Berkley Center for Entrepreneurship and Innovation and Cyrus Innovation to bring you 3 days of talks and workshops that delve into the entire product development lifecycle by accomplished practitioners and leaders in the LeanUX Design community.
Lane Halley (@thinknow) and Courtney Hemphill (@chemphill) will give a talk: “Mixing Lean UX and Agile Development: How to minimize risk, maximize flexibility and create the right product.” and run a workshop: “Conversation, Cadence & Culture: Recipes to Inspire Collaborative Teams.” Grab a ticket soon and come on by, say hi, and join in the conversation!
When integrating 3rd-party APIs, it’s important to listen to your tests. The most common design relies on tests that directly mock the 3rd-party API. These tests are brittle, but are often acceptable because, well, they work. A better approach is to take the time to design an app-specific interface to wrap the 3rd-party API. The resulting tests will be more resilient to change and more maintainable. Introducing an explicit interface for an implicit concept will also enrich your domain model. In this post, we’ll take a look at each of these approaches.
As an application matures, classes begin to take on more and more responsibilities. Eventually a class’s main responsibility starts to become obscured. You can prevent overwhelming your classes by introducing collaborators to help them fulfill their responsibilities. In this post, we’ll look at an example of using a collaborator to prevent non-domain responsibilities from creeping into a domain model.