Name: Happy Cog
Price range: $

Defining our industry's methodologies, standards, and culture have long been a part of Happy Cog's values.

We started Cognition as a product to offer advice, create a dialogue, and serve our industry and clients to help them with their goals and aspirations.

Learn more about Happy Cog at happycog.com.

Taking the Local

6/12/14

by Joe Rinaldi

A prospective client recently raised the (periodic) concern that our team wasn’t in close proximity to their headquarters. My reply was thorough: “We have two locations ourselves; successfully working remotely is in our DNA.” “We have a track record of working with clients all over North America and abroad, and a laundry list of client testimonials and references.” “Even when we work with a client in Philadelphia or Austin (where we’re based), those projects behave the same way as when we work with a client in South Dakota. Our process is location-agnostic.” Etc. etc. etc.

The client seemed to appreciate my response, but in the end, they chose a local firm instead. I missed my opportunity to win that particular project, but the next time our proximity to clients comes into question, I’ll have a different response. My answer should have been simple, concise.
Cognition Roundtable

6/5/14

by Michael Johnson

On this edition of Cognition Roundtable, we ask: “Does every site need to be responsive?” This question has been an undercurrent topic for conversation in the web industry ever since RWD was introduced, but our own work as well as others’ continue to spark it again and again. Design Director Michael Johnson leads a discussion on the differences between adaptive, responsive, and dedicated sites with Senior Designer Yesenia Perez-Cruz and Developers Anthony Colangelo and Sam Hernandez. Tune in for this half-hour discussion that also covers:
Designing with a (Performance) Budget

5/29/14

by Katie Kovalcin

Lately, the web industry has been focusing on ways to improve performance—specifically, by applying the idea of a “performance budget.” A performance budget involves establishing a target page weight (usually in kilobytes), and then making sure no single page exceeds that value. While sticking to this number may seem like a developer’s burden to bear, as Mark Perkins puts it, “performance is everyone’s problem.” As a designer, it’s important to keep your budget in mind throughout your entire process—all the way from discovery through implementation. When both designers and developers work closely to set and stick to a budget, a sweet spot will emerge where neither performance or design will be compromised.
Meaning over Complexity

5/22/14

by Anthony Colangelo

Over the past few months, I set out to write regularly. I also had a few potential talk topics bouncing around my head, and I had been waiting to find the right place to share them. This past April, I spoke at two events: Jersey Shore Tech on design patterns in JavaScript and Peers Conf about how we built the system at the heart of the O Music Awards.
Hover-crafting

5/15/14

by Sophie Shepherd

As a designer, my involvement in projects’ front-end development varies. Sometimes, I spend most of my time in code; other times, I work solely in Photoshop. But, there is one part of every front-end engagement that I always love to jump into the browser for: to create hover animations.

Hover animations are a site design element just like typography and color, so it’s important that designers take ownership of this step. Not only do hovers add to the look and feel of a site, but they also add an extra layer of usability for users with a mouse. A finished site may “work” without them, but these nuanced touches add polish and really reinforce a site’s personality. I like to think of their addition as “bonus design”—it’s an opportunity to better what’s being built.
’Tis but thy name that is my (fr)enemy

5/8/14

by Katie High

“What’s in a name? that which we call a rose / By any other name would smell as sweet; / So Romeo would, were he not Romeo call’d” (Shakespeare, Romeo & Juliet, 2.2).

In the world of project management, naming conventions are often the source of miscommunication. You have to call your work something, but if you assume everyone interprets a name the way you intended, you’re likely to stub your toe during the course of the project. As managers, minimizing risk and setting expectations is an everyday task, yet something as simple as a name or label can fly under our radar. We live and breathe our work, and we are passionate about it. It’s a good practice to never assume labels are understood out of the gate. Here’s a few tactics to help you make naming conventions work for you.
Why Developers Need to Learn Design

5/1/14

by Stephen Caver

A couple of years ago at Happy Cog, I transitioned from my position as a designer to a developer full-time. Up to that point, I had been a hybrid designer and developer, splitting my time between the two responsibilities. The truth is that it was a long-overdue transition. My passion lies in the development side of the spectrum, so I am glad to be in a role where I get to express that passion full-time.

I no longer design all day every day, but my experience as a designer taught me that developers should learn and practice design. The trope is often that designers need to learn to write code, but in working as a developer on the web, I’ve learned that the value of a design education pays dividends beyond being able to mock up a page in Photoshop.
And They All Look Just the Same

4/24/14

by Greg Storey

The article’s title is borrowed from Malvina Reynolds’ song, “Little Boxes.” No doubt, many of you have heard the lyrics, though sung by a different artist than the original songwriter. Malvina wrote the song to protest the mass conformity of home development taking place in a suburb of San Francisco in the early 1960s. If you have ever driven through the area, you can still see all the ticky-tacky, little boxes dotting the hillsides and throughout the area. Though Daly City provided the inspiration for the song, Suburbs of Sameness are prevalent throughout the country.
Everything I Know About the Web I Learned on the Job

4/17/14

by Brett Harned

When I graduated college with an English and Fine Arts Degree, my school’s career services office didn’t know what to do with me. They handed me a giant book of jobs for English majors. Nothing interested me, but I wasn’t going to let some lady in a university office dash my dreams. I went to Monster.com and found what seemed to be my dream gig at a startup. I applied, selling myself as a creative type eager to learn anything and everything.

I got that job over 15 years ago, and I’m happy to report that that description of me still hasn’t changed. I’ve always wanted to learn on the job, and I still do. Somehow, I’ve made a career in an industry perfect for learning while working.
Avoiding #RWD Limbo

4/10/14

by Chris Cashdollar

Almost four years ago, I wrote a Cognition post about my Rule of Threes. In it, I explained that pushing a design effort far enough often resulted in stronger, better-conceived, and more thoroughly vetted solutions. If you didn’t read the article, let me give you a quick recap:

At the conclusion of the information architecture phase, multiple designers worked in unison to evolve three unique design concepts. Each effort was aimed at different, but agreed upon goals. By varying art direction, user-interface interpretation, and content prioritization, the Rule stressed designing a “range” of static mock-up solutions to present to a client. Whichever concept garnered the most attention became the “base model” that was iterated on and drove the overall look and feel moving forward.

Want to hire us?