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.
Last weekend my best friend’s gregarious seven-year-old (we’ll call her Ellie) took over our lunch date to ask if she could teach me to play the board game Sorry!. Ellie has known, since she was four, that she wants to be a teacher. She wakes up early to play school, goes to school, then comes home and promptly starts playing school with her 2-year-old twin sisters. SHE LOVES SCHOOL. But really, she loves teaching.
The night began innocently enough. Now it’s two in the morning, and the best I have to go on is a sense of irony that’s settled in my lower back. Distractions on top of distractions.
Recently I’ve been “evangelizing” Docker quite a bit among the Happy Cog developers. Sometimes that sounds like “zomg, Mark really loves Docker” and other times it’s closer to “omg, why is he over engineering this again.” What I’ve been working on, lately, is a way to use Docker containers to re-implement a more flexible version of Heroku. The end goal is a workflow that starts with a developer pushing code. That code, regardless of branch, is published to a unique URL that anyone can see, regardless of their setup or environment.
Our work with SuperFriendly and Philly.com is well underway. We’ve shared some insights, and launched our work on a beta site starting with our templates for article pages. We’re receiving valuable feedback and some really positive initial reviews and reactions. I’m so proud of this work and its response, but I keep telling people “Just wait, there’s so much more on the way!”
The beauty of web was pure once
Design and dev in an unexplored medium
A true alternative to corporate tedium
A rise to type, deservedly so
Was anyone sad to see Comic sans go?
As a new Happy Cogger (today is my four-month workiversary), I am slowly but surely adjusting to my new role and schedule. Before joining Happy Cog, I spent two years as a Graphic Design MFA student at Maryland Institute College of Art in Baltimore. Two years of trying new things, advancing my skills, and writing and researching. Despite now working outside of an academic context, that doesn’t mean my education has ended. It’s just shifted focus. The following are ways my education has evolved during this transition from graduate school to professional practice.
You’ve kicked off a website redesign project for a new client. Between negotiating contracts, facilitating a dialogue with stakeholders, and establishing a deep understanding of your client’s content and design priorities, you’ve arrived at a list of pages to represent a journey from old to new. These pages likely represent templates from which a site-wide design system comes to life. So you return to your desk, work for weeks and months, and snap all of those pages have been designed and coded, and you’re finally ready to share your work with the client. Right? Not so fast.
Terminal is one of the more powerful apps that comes pre-installed on the Mac. In a nut-shell (see what I did?), it’s an emulator for bash, which is a command processor that lets us interact directly with the UNIX-based operating system that makes the Mac go. As developers, designers and curious tinkerers alike, it’s safe to assume we all rely on it one way or another.
I decided to experiment with keeping a journal of my projects: an iterative, running log that captures all the small day-to-day decisions made internally or with the client, in one place. It began as a way to keep myself more organized, but I’ve noticed a few benefits to this practice, and overall, it’s been a way for me to get to know my work much better. Unexpectedly, presenting my design work has become much easier, as this journaling has been a way for me to rehearse and commit to memory exactly what happens when anything is clicked, why I made each design decision, and how this will all come together in the CMS.
Our modern workforce seemingly champions what I call the two-year tech itch. That is to say, it’s in an employee’s best interest to move on from an employer after several well-fought, win-laden years. You’ve put your time in so you’re not a job-hopper, you stand to level up a few K; and maybe you want a loftier title, to start fresh at a new gig. It’s a very common sentiment—as though there is an hourglass cemented to the edge of your standing desk, just ticking away the time left before you wonder, “What am I still doing here?”
Copyright 1995-2024 Happy Cog™
