We say social, because CodePen is a community. Most creations on CodePen are public and open source. They are living things that other people and the community can interact with, from a simple hearting, to leaving a comment, to forking and changing for their own needs.
People use CodePen for all sorts of things: prototyping new ideas, reduced test cases for bugs, sending clients things to look at, evaluating potential hires, to finding inspiration. People also use CodePen as a sort of resume and portfolio, showing off their best design and development work.
We're trying to make CodePen a happy and healthy place for front-end designers and developers and the people looking for them, while also being a damn fine place to code. ❤️
Tim is a full stack developer but with more focus on back end. He does a lot of the Rails work for CodePen. He is also our server master and keeps CodePen fast.
@timsabat on Twitter and @tsabat on CodePen.
@alexquez on Twitter and @quezo on CodePen.
@chriscoyier on Twitter and @chriscoyier on CodePen.
Marie wears a lot of hats. She is our podcast producer, documentation lead, customer support maestro, editor, and community manager.
Marie is @MMosley on Twitter and @mariemosley on CodePen.
Rachel is a full stack'er in Australia. Not only a creative and talented designer and developer, but a great technical writer and wonderful and encouraging CodePen community member.
Rachel is @rachsmithtweets on Twitter and @rachsmith on CodePen.
Cassidy is @cassidoo on Twitter and @cassidoo on CodePen.
Klare is a designer who codes in Seattle. She focuses on everything from design research to crafting interfaces and illustrations to playing around in SASS.
Klare is @klare on Twitter and @klare on CodePen.
Stephen is @shshaw on Twitter and @shshaw on CodePen.