elyseholladay
commented
9 years ago Hi Kevin & Lam!
Thank you so much for submitting to SassConf this year!
Unfortunately, we weren’t able to select your talk.
We had an incredible number of submissions this year: 81, in fact, enough to fill up over two weeks of Sassy goodness! But we only have two days, and we couldn’t pick everything.
If you have any questions at all about our selection process, your submission, or anything else at all, please reach out: elyse@sassconf.com and I’ll gladly give you more details.
Again, thank you for submitting. It’s people like you, who are willing to put themselves out there and work hard and submit and give talks that make it possible to even have SassConf. I hope you will submit again next year and continue to be part of the Sass community!
See you in November!
Title of Presentation
Styleguide Driven Development
Type of Presentation
Standard Length Talk
Description
Governance. Standards. Styleguides. In other words, restrictions. However, at Capital One our Build Book and styleguide is the first step towards solving problems. The styleguide was the first step in the proof of concept for our site-wide responsive retrofit. The styleguide and its component-based structure has helped drive time-to-market from months to weeks or even days.
Quality engineers start with our styleguide for writing test cases and ensuring components and content display work correctly. UI developers across the country have a single location to double check they're using the right class or javascript hooks and see new functionality added or in-flight. Designers focus on design and user experience rather than pixel-pushing because a line-break isn't quite right.
In short, a styleguie adds value to our entire team by allowing us to identify and solve new problems rather than repeating ourselves. We're working on re-building it this summer and we'll share what we learn. We'll talk about how we build and maintain it. Through empathy research, we'll show what problems our users have and how we solved those, and show examples to help you do the same.
Speaker Info (required)
Social Media:
Bio:
Kevin: I've worked with companies large and small, profitable and not (intentionally and not) to manage content, write code, and solve problems. As a senior software engineer at Capital One, my current focus is on the health and hygiene of the Capital One Marketing Platform. That's simply a fancy way of saying I wear many hats. I work on our styleguide and coding standards, backend process improvement, front-end feature enhancement, mentoring new team members, and learning new ways to solve old problems.
Lam: I've been with Capital One for over 8 years in various roles. I started as a PHP developer and moved into User Interface and Experience Design, focusing on front-end development. I'm currently the lead UI engineer for our design library team. My primary focus is on bridging the gap between our design and tech teams, creating, maintaining and governing coding and design standards, and creating new UI features for our platforms.
Photo:
Kevin:
Lam:
