Senior Software Engineer
What’s your average day like?
First thing I do is spend 15 minutes to an hour skimming my RSS feeds for the latest technology news. Sometimes I'll come across something that's very relevant to what I'm working on at Blurb, like a new CSS technique or development tool, so I prioritize these articles. Other times it's just an inspirational blog post (like the ones I read from The Pastry Box Project).
I then focus on my tasks and stories for the current sprint. I do a lot of code review at Blurb using GitHub—this gives us an opportunity to review someone else's work and provide constructive feedback. It not only helps us maintain a high-quality codebase, but it's also a great learning tool. It gives me a chance to see how someone else might achieve a task—we each have unique approaches as coders.
When I worked out of the San Francisco office, lunch was always something I looked forward to. There are so many amazing restaurants near our office, so a few of us would get together every week to try them out. And of course on Wednesdays we have catered lunch. This is always fun as I usually get to chat with someone in a different department.
If you could describe working at Blurb in three words, what would they be?
Challenging. Flexible. Diverse.
How do you describe your job at Blurb to other people?
I'm a UI-focused Software Engineer at Blurb, an on-demand publishing platform where we help people make both print and digital books.
What technologies, processes, and techniques do you get to use?
Tell us about your own Blurb books.
Every year my husband and I celebrate our anniversary with a book that nicely summarizes the year for us. It's a photo book of all our adventures.