I love building things. My primary focus is systems software; my career's spanned work on operating systems, virtual machines, distributed systems, compilers, and machine learning.In engineering, my usual approach is to focus on the problem -- what's driving the product? Who's the customer, and how're they going to use it? That then breaks down into engineering projects (where you know what to build) and research questions (where you don't); you design engineering projects to answer your research questions, you figure out what's achievable, and you build the best product you can within that space.As a team lead & manager, my focus is on how to unblock my team -- what's holding us back from doing our best work? This usually breaks down into some combination of good task assignment, project tracking, skills development, architecture definition, test engineering, requirements engineering, &c, but I find that I don't have much dogma in those areas -- these are all just tools in service of enabling the team to deliver great products, according to the customer's definition of great.As a coworker and a human, my focus is on being as kind as possible, creating a psychologically safe environment, both because it's better for the team and because I've found it to be essential to delivering great products. I spend a significant amount of time practicing conflict resolution techniques, training myself to see things from other people's perspectives, rethinking what I think I know, and building an instinctive habit of finding the win/win angle that leaves everyone feeling great.(Or, to put it all another way -- in my experience, writing software is Easy; the tricky bit is figuring out what to build and getting everyone onto the same plan and pulling together, maximally utilizing everyone's various strengths.)So if you have something cool / useful to build, and I sound like someone who might be able to help, please feel free to reach out; I'd love to hear from you. :-)