Monday, September 9, 2013

What I Worked on This Summer

I wasn’t sure I’d be able to do a post on this; one of the biggest issues with an internship in the tech field is that interns are given a lot of access so they can work on incredibly interesting projects, with brand new and usually top-secret technologies.  As cool as my projects have been, there is very little I can actually say about them unless Google decides to use them publicly (‘launching’ a feature is the golden goose for interns).

However, my host gave me a really great idea for a blogpost.  Instead of talking about what I’ve been doing (as it hasn’t been released), I can talk about the amazing technologies that I’ve been able to work with, some of which are also available to people outside of Google.

Knowledge Graph: linking entities

When my host was telling me what he could about what I’d be doing over the course of the summer, he told me to research the “Knowledge Graph” (  KG is an amazing technology, and what makes it so awesome is that instead of focusing on searches by using strings (for the non-CS readers, a string is a series of letters that are combined), it focuses on entities.  The idea behind entities is that every word holds an entire context, that when a user searches for ‘The Hunger Games,’ they aren’t merely looking for every website containing those words; instead the Knowledge Graph knows that ‘The Hunger Games’ is a book written by Suzanne Collins, has been made into a movie starring Jennifer Lawrence as Katniss Everdeen, and has a second movie premiering in November called ‘Catching Fire’.  It takes that information, and then decides what results to show.  By treating search as a type of interconnected network of associations, KG mimics a human brain’s ability to make leaps of logic--but without the spatial limitation of memory, which has amazing results in providing the most contextually relevant information to the user.

I’m not sure about you, but after I looked into it, I was completely hooked by the concept (I also fell in love with Facebook Graph Search for the same reason).  I started seeing that my Google searches were smarter than I had originally realized.  A friend wanted to know if Ewan McGregor was married, and so I searched ‘ewan mcgregor’; the Knowledge Panel on the side gave me his birthdate, height, full name, spouse, wedding date, children, movies, and images.  This, all without leaving the search page.  I realized during this research, before even beginning my internship, that a lot of the time I make a search on Google for a fact, I never even have to click a link to get the response. (The best example I’ve seen of this lately is the Google search for ‘timer’.  Seriously, that exists.)

Knowledge Panels : yes, they're beautiful

Most of my time here at Google, I’ve worked with Knowledge Panels in some manner, and none of their magic has disappeared with learning more about how they work.  In fact, the first time I managed to make a button appear on one I proudly showed every member of my team; to them it was probably akin to a fifth grader showing their mother macaroni art, but the fact that I got to work with--and affect--something that I used in my daily life was such an awe-inspiring experience.

During a three week period where my boss was on vacation, I had the opportunity to work with the Calendar team, and play with their API.  Although I was working internally, I was surprised to see how much can be done with Calendar externally (  As an intern, I spent a lot of time understanding this API and playing with it before I started working with this product.  Besides the fact that you can customize the features with your own code, there’s already amazing built-in features for Google Calendar (not taking any credit, the most I ever did was make an event show up on my own calendar), my favorite of which is the ability to type what you want, i.e. ‘Dinner with Mom at 7:30pm on Friday’, and have an event appear on your calendar.  It’s a magical moment.

I ended up doing a lot of user interface design and implementation during my internship for a few reasons.  One is that there was a need on my team to see what a feature would look like quickly, and who better than the intern who’s itching to try something new?  The second is that I spend a lot of my free time, outside of work and school, coding up personal projects in JavaScript, CSS, and HTML.  I make my art projects into interactive web pages, use Google Developer Tools to (temporarily) change how my friends Facebook pages looked when they leave me alone, and I write snippets of code in the console to see if functions I am tinkering will would work.  All of this learning was outside of a classroom environment, and I use it every single day on the job. People think that getting an internship is all about studying and knowing algorithms inside and out, and they’re right; however, doing well as a software engineer is about having a passion for what you’re doing and finding projects that inspire you.

I think one of the things that makes the technologies and features that Google makes so great, is that almost every engineer is working on a project that they are personally (not just professionally) interested in seeing succeed.  You’re given the time, and support, needed to become an expert at whatever makes you passionate about engineering, and you’re encouraged as an intern to explore different technologies to see where you fit best.

Monday, August 12, 2013

A Weekend in San Francisco : Intern Style

My hotel!
While I was in Mountain View, I had the chance to stay a few more days and spend some time in San Francisco with a few friends.  I was surprised at how easy it was; my team helped me get a flight planned to leave that Sunday and found me a place to stay.  Baris and I finished our work before noon on Friday, and he dropped me at my hotel before going to the airport.  I wasn’t able to check in since I had arrived earlier than my reservation, so I asked the bellhop where I should go, which is how I ended up in Chinatown.

It was odd seeing San Francisco as an adult; I grew up in the area, but I remember only the most touristy sections.  I was struck by how spread out the city was.  In NYC, everything is either walkable, bikable, or subway-able.  Here, I had to think about the bus system and wear my best walking shoes.  My friend Elissa, an intern for a start-up called Toy Talk, showed me a few apps that she’d used to help get around, including Lyft ( and Uber( that use ride-sharing to lower the cost of getting around at odd hours (I was skeptical for security reasons, but it has some interesting ways of ensuring safety).  I wandered through Chinatown, and into a few stores on Mission Street.  People were very friendly, and it felt like a slightly slower pace of life.  I didn’t get yelled at once for walking too slowly, and pretty adjusted to the West Coast pace of life.

Later that night I met up with my friend Tara, and a group of Google interns she was friends with to go to a club and watch a DJ set.  We were easily the first people at the venue, and it was fun to get to know an entirely different set of interns.  I was struck at how tight the group was; in NYC interns tend to have friends outside of the office, and even when groups forms outside people are often invited along.  In MTV, the group seemed much more close-knit from living, working, and hanging out in the same places all summer with very few interactions with non-Googlers.  I was entertained to see one of them was an intern featured in the Google ‘Real Interns’ video --it was somewhat like meeting a celebrity!

A view of San Francisco from my hotel room.

Tara and her friend stayed the night, and in the morning we went in search of a breakfast place.  In NYC, it’s easy to find food and if you end up in a bad area of town, it’s quick to find a way to a safer area.  I was much more nervous wandering around San Francisco from a combination of the spread out nature of the city, the low-hanging fog, and how quiet the city was.  In a lot of ways I missed the bustle of a New York City sidewalk.  We found a breakfast place called “The Little Griddle”--by the time we found it, we had given up finding a good brunch place, and were shocked at how good the selection, food and prices were (  It was crowded, and Tara and I ended up sharing a table with a few other people, and took a photo of a funny sign that was hanging on the wall.  The last one definitely gave us a giggle (although seriously, G+ is awesome if you use it enough).

The sign from 'The Griddle,'
photo cred: Tara Siegel

Later that afternoon, we met up with some friends at the Japanese-Pop( festival in Japantown.  I don’t think a single one of us actually listened to Japanese pop, but the experience was really fun and the people were super nice.  We spent a lot of time wandering, eating food, and listening to people performing.  After the festival, my friend Elissa took me to a Thai restaurant she had been wanting to try, and it definitely lived up to expectations in both price and quality (Chabaa Thai Cuisine).

Tara and I at the J-Pop festival
The next day I took the BART (Bay Area Rapid Transit) to SFO and got on my plane.  My trip wasn’t that long, and I barely got a chance to scrape the surface of what makes San Francisco such a great city (not the least of which is it’s awesome Google office that I heard a lot of Googlers talking about).  I did have two interesting insights from my weekend in the city, however.  One is how small the tech community really is; I was able to see most of my friends that week, and it reminded me that even though we’ll most likely end up at a variety of different companies, working in the tech industry makes keeping connections a lot simpler, simply because it’s a relatively small circle.  Second, is my personal opinion that there is an inherently different corporate culture on the east and west coasts was reinforced.  People in California tend to leave earlier in the day, mostly because the weather is a larger part of the appeal, and you want to take advantage of the daytime hours. In NYC, people start later, and leave later in order to take advantage of ‘the city that never sleeps.’  There are pros and cons to both, and I think it’s pretty great that Google keeps offices in so many cities; they never lose someone because they can’t work where they would like to.  A lot of fields can’t afford to be as accommodating, but the fact that Google takes advantage of the remote nature of technology and is willing to send people (including interns) to where they can work most efficiently, reminds me how lucky I am to be in a company that cares so much about each employee’s individual contribution and quality of life.

Friday, August 2, 2013

Interview with Google Student Blog

In a very exciting twist, I was interviewed for the Google Students Blog! Such an amazing experience--intern Shelbey Roberts is very fun to talk to--and except for the one little part that implies I have less of a CS background than other interns (sorry non-CS people, I wish I could be an example of someone without a CS-background making it at Google, but I'm a full computer-graphics major; the fine-arts portion is my minor and a few electives the design portion of my major requires), I think she did a wonderful job representing my intern experience.  You'll also get a taste of my project in it, since it's through a more official channel!

Spotlight on Mountain View

When I first got my internship, I expected the offer to be from Mountain View; after all, ‘The Internship’ had just been announced when I was interviewing, and I knew that Google was based in Silicon Valley.  Even though I had heard wonderful things about the MTV campus, as someone who had spent their childhood in the Bay Area and was ready for a new adventure, I couldn't have been more thrilled when my offer was in New York City.

During the second month of my internship, an opportunity to see MTV arose: the female interns had a chance to fly to MTV for the Google Women Engineering conference--the same weekend that my parents would be in NYC to visit me.  I was a little bummed, mostly as I had become utterly convinced that I would like to stay with Google after graduation and knew there was a good chance that I would end up working in Mountain View without ever having seen it.  And then, one day a big surprise occurred. As I was cranking code and focusing on my last weeks to complete my work, we got a new project. During our first meeting with the engineering team we are supposed to work with, their tech lead suggested that my host and I fly out to meet with his team and next thing I knew I was packing my bags.

The flight was a blur, mostly because we left at 6am EST and were at the office around 1pm PST.  I drank a lot of coffee (every moment of which my host, Baris, caught on camera), but thanks to all that caffeine, I managed to be relatively alert as we dropped our stuff off at the hotel and made our way to the campus.

Some fun Google sights outside
the aptly named 'Android Building'
My first realization on the campus was that I could hear birds, something that you almost never hear in NYC unless you've encountered a crazy pigeon.  My second was that everything was so big; there were buildings in every direction, and the colors blue, yellow, and red were everywhere.  It was like I had walked into a Google Candyland style world.  On our walk in, I saw people playing beach volleyball, rows of Google bikes parked in front of the doors and, for no discernible reason, a T-Rex skeleton stuffed with pink flamingos.  The whole experience was odd, and even though the surroundings were so ridiculous, I felt strangely intimidated because no one else seemed to even notice that things were odd; I felt like a tourist, not a Google employee.

It only took a day for me to feel at home.  My host and I met with the team, and quickly went to work; by day two, I had my own desk, chair and monitor, and was knee-deep in code.  We only surfaced for meals, and I would wander and explore at lunch.  I spent a lot of time having my friend Tara (a web development intern for Google on the YouTube team) from Penn show me the campus and the various cafes.  We visited at least four different cafes, including my favorite one that served a large assortment of sushi.  I even got used to biking around the campus, a skill I wasn't even sure I still had.  The weather was stunning, and there were always pickup games of soccer, football, or volleyball going on as I rode by.

Googlers eating lunch in the main campus!

One of the days, Baris and I had lunch with one of his previous interns who was now living in Santa Cruz and working on Google Maps.  It was interesting to hear about her career and the different things she had worked on at Google; it was a bit odd as well, because I could see myself in her shoes in a few years.  Most nights I quickly ate dinner before heading back to work, but one night we went to someone’s house and had pizza and talked about different projects people were working on.  It was interesting to realize that there’s a stronger emphasis in MTV about spending time together after a work day; people don’t leave to go to bars, hop on the next subway home, or meet friends in another section of the city.  They actually spend time together even after work.  I walked down the main street in MTV one night, and it took me about fifteen minutes.  In some respects, the experience was lonely because I was only there for a week; however, I could see how easy it would be to get addicted to how beautiful the area is, how nice the people are, and the more relaxed way of life.

It was a crazy week, and as a reward for the long hours and hard work we’d put in, Baris and I went to his favorite coffee shop in Palo Alto on Thursday morning.  Although the MTV office had espresso machines, I couldn’t figure out the trick to making them taste like the lattes I made in NYC (hard life, right?) and welcomed a decent cup of coffee.  What I got, at the coffee shop called ‘Philz Coffee,’ was the best cup of coffee I’ve ever had, and the first one I’ve chosen to drink without any milk or cream.  They brewed each cup of coffee individually, so it was fresh and the blend was tailored to the flavors I really liked.

I look like I really want
a photo taken, don't I?
At the end of the day, I went to TGIF with Baris.  For those of you who don’t know, TGIF is a weekly all-hands meeting where Googlers can ask questions directly to Larry, Sergey and other executives about any number of company issues.  I sat right next to the stage, and in an incredibly awkward and amazing moment, exchanged hellos with Larry Page himself.  It was such a rush to watch people I've read about and admired for years talk candidly about Google and it’s mission.  I was reminded that Google is a company built on a singular idea: to organize the world’s information and make it universally accessible and useful.  And that includes making sure their employees are as well informed about the company’s ventures as possible.

On Friday, we raced to finish our work and left the office around one.  I had delayed my flight until Sunday so that I could spend the weekend in San Francisco with some friends, and Baris dropped me off at my hotel in SF on his way to the airport.  Although I didn't get the full Google MTV Intern experience, I had a chance to see what interns in MTV experience and I have no doubt that I would be happy to work there one day.

The first time I was asked
to pose for a MTV photo
The fifth time I was asked to pose; I wanted to get to work!

(Countdown to completion: 18 days)

Monday, July 29, 2013

The Path to a Google Internship

I think one of the biggest misconceptions is that the path to an internship at Google is a linear progression.  That it happens just the way the recent Vince Vaughn/Owen Wilson movie made it seem: you apply, you interview, you're reviewed by a hiring committee and then you're either made an offer or rejected.  In reality, it's a lot more complicated than that, and Google is no exception.  There is a traditional progression, yes, but if Google only recruited traditionally, I wouldn't be an intern here.

The traditional path for a software engineering internship starts with submitting your application.  A recruiter reviews your resume, and then chooses whether or not you seem like a good candidate.  If you're a strong candidate, they offer you phone (or on-campus) interviews, and then based on the outcome of these, you enter a Google-specific process called 'host-matching.'  The idea at Google is that you aren't just offered a generic internship; they set you up with a Googler who matches your skills and interests and then you're offered that particular internship.  This is a tough process because even after passing your interviews, there is no guarantee of being chosen by a host.

I had a different path.  I submitted my application (more than once, I'm not embarrassed to a
dmit) and never heard anything.  At the time I was interviewing for another internship, and figured that Google wasn't interested;my resume is pretty design heavy, and struggles to gain traction with software companies.  However, when I heard they were holding an interview prep talk at my school, I knew I wanted to go and see what I would have to do to get a Google internship.  At the talk, they asked for volunteers for a mock interview and a couple of my friends went up; at some point, I decided that I wanted to volunteer if only because it might be the one time I could practice a real Google interview
A Google talk at Penn

At that point in the workshop, they were doing ‘Project Manager’ mock interviews, and considering I only had a vague idea of the job description, I struggled a little.  I worked through an application design problem, and as I left the stage, the engineer who was running the workshop shook my hand.  The next morning I woke up, and had an email that I had been given one of the coveted on-campus interview slots the following week.

I had been studying for almost two months at that point: I knew the space-time complexities of all the sorting algorithms by heart, I had been spending most free evenings doing algorithms homework since it was homework and also studying, and I had already finished four interviews with two other companies (one of which made me an offer, and one of which didn't).  By the time I walked into the on-campus interviews, I knew that preparation wouldn't be the reason I didn't get the internship.

I was nervous.  I typically wear dresses and skirts, but I knew Google respected casual dress so I wore a t-shirt.  I sat in a waiting room for far too long, my nerves completely on end, making far too many jokes that only a few of the other nervous potentials laughed at.  My first interview went really well; my interviewer gave me a question I had never seen, but was something I really understood.  I solved it quickly, and then blurted out the complexity before she asked.  She quickly made it harder and I almost begged to stay in the interview because I had just figured out the trick when it ended and I wanted to prove that I could code it.

A 2am study session for
my Google interview
My second interview was completely different.  When I walked in, the engineer immediately presented me with a question that relied entirely on a fact (not a concept, luckily) I hadn't memorized.  I knew how to solve the problem, but wouldn't have been able to write the details of a necessary helper function.  I explained how I would solve the problem, wrote out the code with the helper function and then when the time came to code the helper function, confessed that I would normally have to Google the information because I didn't know it offhand.  He then quickly gave me the information I needed and I wrote the helper function.  At the end of the interview, he asked me a few questions concerning my interest in Google, and then we discussed an algorithm I had learned in class.  I hadn't met anyone else (besides my algorithm’s professor and my homework buddy) who thought it was cool enough to talk about for ten minutes.

What I didn't know at the time of these interviews was that the engineer on stage, at that original talk, had been impressed that I had gone up, liked the way I approached problems, and had checked to make sure I got an interview. The week after I heard back that I had passed my interview, my recruiter told me that I had had six host matchings.  That meant six phone interviews, with six managers, all of whom were interested in the fact that someone who had such a significant art background had passed the technical interviews.  The skills that had originally caused me to struggle to get an interview were suddenly my greatest asset.  When the fifth interviewer called, he introduced himself; it was the engineer from the workshop.  We talked for a few minutes, he asked me a quick coding question which I first solved and then we discussed, we talked about my interests, and hung up.  The next morning, I had an offer in my inbox.  He chose me because I had taken a chance and put myself out there at a talk; he gave me an opportunity to prove that I could be a software engineer because of my willingness to try new things.  And because I had done all the work leading up to it, in studying for interviews, I was able to show him I could be a computer scientist.

There’s a lot of different stories of how people have gotten a Google interview and offer, and a lot of the time people tell me how unbelievably lucky I am when I tell them my story.  I think, what’s wonderful about Google and how you get an internship at this company, is to simply stop caring about trying to be what they are looking for.  I love art and I love computer science.  Most companies think that means I won’t be as dedicated an engineer.  I asked Google to give me a chance, and Google let me prove to them that my love of design makes me a better one.

That’s the end of my story.  It’s not a traditional pathway to an internship at Google, but I think it gives a good side to the interview process; it’s not always about how beautiful your resume is, or what your GPA says.  Sometimes it’s about making eye contact and taking a chance that you might look stupid, just to prove that there’s more to you than can be seen in a first impression.  And I think that’s something I would describe as very ‘Google-y.’

On a side note, but in the vein of talking about internships, I want to mention one of the things I find most interesting about Google, is that they have two programs geared towards younger college students.  This is not something I have seen at other major companies, and feel is something pretty amazing that Google offers.

Freshman Engineering Practicum:
I really wish I had known about this program: it's geared towards CS (or CS intending) freshmen.  It's a fantastic opportunity to get a major internship on your resume early on in your education.  It also helps to prepare you for further opportunities at Google, which as a current intern, I wish I had been able to take advantage of at that age.

Engineering Practicum:
This is similar to FEP, only geared towards sophomores.  It's practically identical to the SWE internship I am doing, and many of my friends here at the office are EP interns.  The main differences involve more social activities among the group of EP interns, classes to help teach coding skills, and a strong support system.

If you know anyone who is eligible for these, or are eligible yourself, check them out!
(Countdown to completion: 19 days)

Wednesday, July 24, 2013

Google Outreach : Diversity and Service in Coding

Google Scholars hacking at
"24 Hours of Good : NYC 213"
I decided to do a post about the opportunities I've been given here at Google to give back to the tech community--I’ll also be posting in the next few days about my stay here in MTV, but I wanted to wait until I’ve gotten a few fun pictures of the Googleplex to show you!

I have had some awesome chances to participate in outreach while here at Google: I taught Scratch to high school girls, have given tours to college students, and volunteered at the 24HoursOfGood hackathon. Not only were the programs easy to find and volunteer for, but I was intrigued to find that Googlers are encouraged to sign up for them, even when it means that they'll have to set work aside for most of the day.

A Scratch screenshot!
The TechGirls program is incredibly cool; twenty-seven high-school girls from nine different countries in Africa and the Middle East come to the United States for a three week period to meet people in the tech industry.  It’s designed to encourage diversity and allow girls to explore fields that aren’t as easily accessible to them in their home countries.  For my section of the day, I taught them how to make a quick game using Scratch--Scratch is an MIT developed program for teaching younger students how to code, by removing complicated syntax and allowing students to focus directly on the logic. I have used the program in my introductory course, taught it to my mother's elementary school students, and Google uses it for programs like this. Scratch uses a lego based structure such that students can 'drag and drop' chunks of code, quickly constructing working programs that have three components: scripts (the code), sprites (characters), and backgrounds. The program we made was simple, merely a counting game that tracked how often you clicked a character.

After the talk, I had the chance to have lunch with the girls.  It was such a cool experience to hear their stories about life in their countries, and I felt lucky to be able to share in their experience of coming to the states (most of them, for the first time).  They were so excited by all the things they had seen in NYC and DC, and even gave me a coffee tumbler to thank me for presenting!
Tech Girls 2013: I grabbed this photo from their FB page, wish I could
have found one from their day at Google!
24HoursOfGood was awesome in an entirely different way.  The idea is to match a group of  students with non-profits to create apps that help the non-profits succeed in their mission.  The students were mostly my age or older, and I was volunteering to assist teams technically: a slightly terrifying concept when you are an undergraduate intern being asked to help people who have already completed their degree.  However, it was a great time, and I was surprised that I had a lot to offer and was able to make a difference by being there.  After I helped one team work through some tricky JavaScript and HTML5, we celebrated with some delicious ‘bison burgers.’  Everyone had a great time, and even though the teams were competitive, the real prize was the awesome apps that were created for the different non-profits. 
24 Hours of Good Explanation

Google Scholars and technical volunteers
enjoying some delicious bison burgers!
(Countdown to completion: 23 days)

Thursday, July 18, 2013

The Google Coffee Break

My first espresso shot!
Coffee breaks are pretty common at any company; employees get up to stretch their legs, rejuvenate with a cup of something involving caffeine, and talk about their lives for a few minutes before getting back to work.

My first week or two at Google, I did coffee breaks all wrong.  Google NYC has coffee brewing machines placed at convenient locations throughout the office.  The machines don't make anything gourmet (although if you're willing to walk a few flights of stairs to the 5 Borough Bistro, there's always plenty of nicer options) but I'm from Seattle and the need for a quick jolt of caffeine at frequent intervals has caused my standards to be considerably lower than the average individual.  I always arrived a few minutes before my team, since I wanted to study what I had done the day before for a few minutes before anyone else showed up; I'd go straight to the machine, stand quietly next to it while it brewed me a cup of coffee, and then go to my desk to start my work for the day. I would then repeat this procedure for the next eight to ten hours.

One day I was running a little 'late' (or rather, on time), and got to my desk at the same time as my teammates.  Seeing my lack of caffeinated beverage, they invited me to go to a different floor to grab espresso with them.  All of a sudden a whole new world opened up; not only was this a daily routine, but it was a perfect moment to ask a question that would take more than a few minutes to answer, ask them about their lives and careers at Google, and tell them funny stories about my intern ('Noogler') experiences.  All of my co-workers have wonderfully fun and quirky sides to them, and it's during these coffee breaks and latte-making teaching-sessions, that those had time to come out.

After that, coffee breaks became my favorite part of the day.  I rarely get coffee without another member of my team, and when I do I ping (I have no idea if this is a common term, the first time I heard it was at Google--it just means 'to GChat' someone) another intern to go with me.  I've made a lot of friends--and a lot of lattes--through coffee breaks.  Google understands that you're not going to be at your most productive if you stare at a screen for eight hours straight and the company makes it easy to get away from the office environment.  It's amazing how much more I get done after taking a break in the rain-forest  or Lego micro-kitchen (yes, one does have stuffed sloths and the other has crazy contraptions built by Googlers on coffee breaks).

People might think that it's a weird work environment, and I've read more than a few articles that describe my friends in MTV (Mountain View) as working in an 'amusement park,' but that's just part of what makes Google so much fun to work for, their inability to take themselves too seriously.  It might be silly, but it's easier to connect with your team and other Googlers when you're making espresso in a room designed to look like a Times Square crosswalk, and I feel more comfortable asking a question when we're all sitting around the ball pit (although I'm usually the only one actually sitting in it).  The whimsical setting always ensures that I'm not worried that anyone will tell me my questions are stupid; if they were going to say anything was stupid, it would probably be the fact that I prefer sitting in the ball pit to sitting in a chair!  I love looking around and realizing that I would never lose the sense of joy I get while coding, when working here; the workplace is literally designed to make sure that you are always aware there is a world outside of your cubicle and that it's important to be a part of it.  It makes you a better engineer and a happier person, and so I always make sure I make time for a coffee break.

My first attempt, which I affectionately named
'The Smurf'
My first semi-successful attempt which I refer to as
'Grandmother Willow' since I was going for a leaf

My only successful attempt which is just 'The Latte'

(Countdown to completion: 29 days)