When I joined Unity in 2010, we were well under 100 people. I don’t just mean in the Copenhagen office. I mean total. I can’t remember; I think I was employee number 60-something, or maybe it was 70-something. Unity 2.7 was the current version. There was no Linux version. Almost all of R&D sat in a couple of European timezones. We had a single, company-wide mailing list that we used
Many people have asked me over the years what they need to do in order to make their technology workplaces more appealing to diverse groups of people. I have given a lot of advice about increasing the representation of women in technology over the years, but since I’m returning to work soon after being on maternity leave with my second child, I’ve been thinking about how what I value in
Hello, World! Well, not exactly. I’ve been around, just quiet. The better part of the last year has been spent on this project: In early April of this year, Levi and I welcomed Player 3 into our family. Baby Bard is a silly, happy, loud, messy, clever little boy who quickly turned our lives upside down, despite whatever efforts we made to plan and prepare for his arrival. I’m lucky
OK, let me clarify. Engineering is not 100% about problems. It’s more like the first 70% or so. The last 30% is about the solution. In all of the engineering teams I’ve worked in, I’m convinced that one of the biggest productivity killers is lost time due to engineers not fully understanding the problem they are trying to solve. Conflicting advice, not understanding all of the constraints, unclear expectations leading
On May 16th, I gave a Keynote at ACT-W Seattle, a conference designed to bring technical women together. The entire recording (https://vimeo.com/129499527) includes both keynote sessions and the morning’s lightning talks; a shortcut to my part is here: https://vimeo.com/129499527#t=47m40s