While Javascript is not essential for this website, your interaction with the content will be limited. Please turn Javascript on for the full experience.

A Blog and Activity Feed Rolled Into One: Evolving Conversations

So it begins, @BioMechSports officially launched #Acculock putters today at #PGAshow2015, and with that, their first mention on Twitter!

Putting blues? @biomechsports AccuLock Ace.Forearm anchor,2 deg,blue to sooth nerves,great feel #like #PGAShow2015 http://t.c…

Putting blues? @biomechsports AccuLock Ace.Forearm anchor,2 deg,blue to sooth nerves,great feel #like #PGAShow2015 http://t.c…

@benspaulding It was truly a pleasure having you here with us. We're glad you were able to find a new home @Lionbridge. Godspeed!

It was a pleasure working with the fine folks @pe1999 — they are talented and fun. But I have now moved on to another opportunity.

@RevSys 's "12 Days of Xmas Performance", a few chuckles mixed with great tuning tips from the best in the biz! http://t.co/mfw…

Use SASS/SCSS and BEM to create Markup that Makes Sense

Part of the challenge when crafting new markup is coming up with semantic class names that are descriptive but not restrictive. This article can’t help you come up with a base name, but it can help make applying those names to your markup and SASS quicker, easier to understand and modular.

There have been quite a few nice posts in the blogosphere about SASS and BEM and how to make them work together nicely. I have seen different ways that people prefer hyphens before elements or underscores, but that doesn’t really matter. What matters is that you have a system and you stick to it. Here is a real-world example that I have from a recent project.

Lessons on design from Charles Moore

I like to compare web design to architecture. I think it is an apt metaphor and will expand upon that idea later in a full article. For now, though, I'd like to share a quote from Mark Simon about the architect and teacher Charles Moore (my replacements in brackets):

Charles Moore taught me too many lessons to list all of them now, but here are a few of the most important:

Listen carefully to your client. Don't assume that you know what they want.

You can give a client just what they want and still make an interesting and beautiful building [website] if you use their vision as your inspiration.

There is no such thing as a perfect design. However, there is a substantial difference between good and bad.

There can be multiple good solutions to the same problem.

[…] Even a master has to discard many bad ideas before finding a good one.

Don't be afraid to collaborate. Share credit.

Dress conservatively to sell a radical design.

— Mark Simon, Centerbrook Architects and Planners. Quoted from Metropolis magazine, May 2014

Added by J. Hogue | July 24th, 2014

Catching our breath & looking over our shoulder

We’ve been quiet for a time, I know. Heads down, working hard… not making time for ourselves and for self-promotion. Sometimes, when the projects are large and the problems are difficult to solve, it’s unavoidable.

It’s been a bit bumpy, I can tell you that. We treat everyday as a learning opportunity, so that keeps us ready for change, however tumultuous it may have been. As I look back at the past six months, though, I can’t help but think we’ve accomplished quite a bit. While the road has been long and bumpy, we have survived and gotten stronger and hopefully smarter. If we don’t learn a little bit everyday, we must be doing something wrong.

Hey @newrelic how can we get our nerdy little fingers on some of those #nerdlife stickers? We want to do some sticker bombing!

Most of the new python site wasn't me, but @fcurella @webology @jacobian and @pe1999. I just helped finish up a few things FYI!

I think it's safe to say that @DjangoSuit has some new groupies at PE. First time working with it, but so far so good. Well played!

We determined that it would cost us more to support IE7 than it would to buy new computers for clients stuck with it. htt…

Welcome to the office @benspaulding! We are getting ready for a great week with our remote peeps in the PVD office for a nice change.

Instead of "Which CMS are you using?", ask "What needs do our users have?" We're designing & delivering services, not buy…