This is a (heavily) abridged version of an internal talk I gave at Unity in Copenhagen in December 2018 about User-Oriented Development. I’m sharing it here because I believe the learnings are useful outside of internal tools and outside of Unity. Hello. Long time no . . . . write? ¯\_(ツ)_/¯ I’ve spent the last year working on a new internal project at Unity called Flight Control. For the purpose
Hello, everyone! I’ve been missing in action, I know. There are a lot of great things I have been meaning to write about and I’ve been struggling to find the time. I’ve especially been doing some really cool work at Unity this past year in the area of data-driven development and I’m itching to write about – so this is me attempting to get my act together and start writing
Yesterday I was attempting to relax by browsing random things on the internet (usually a mistake, I know), and I stumbled upon an awesome white paper by Arnon Rotem-Gal-Oz about the 8 Fallacies of Distributed Computing. These are so obvious yet so profound I couldn’t help but write up a quick blog post about them. They’re especially relevant for modern day build engineers and tools developers — certainly relevant to the Build Automation
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
In a previous post, I wrote about what build engineers actually do. A related question is, “What makes a good build engineer?” Obviously this is subjective, but I can share my opinions based on my particular skillsets that are useful in my job as a build engineer, and the qualities I look for in prospective candidates when looking to expand my team. When trying to answer this question, an important thing
“Press forward. Do not stop, do not linger in your journey, but strive for the mark set before you.” Goodbye Nich. You’ll be missed. https://blogs.unity3d.com/2013/02/21/time-to-move-on-to-something-else/
I recently upgraded from my old Nexus One to a brand new Nexus 4. I won’t got into a lot of detail here (there are a lot of in-depth reviews of the Nexus 4 on the internet), but I will say that overall I am extremely happy.