44 minutes ago · 11 min read2137 words · Tech · hide

I’ve written about becoming a Design Engineer a few times, and the advice gets awkward when I try to give everyone the same starting point. An engineer who’s spent years shipping interfaces needs something quite different from a designer opening a codebase for the first time. Someone who’s just graduated might still be figuring out which part of the work they enjoy. You bring something useful with you in each case. I’d start there, then look for the part of making a product that you currently need someone else to figure out. For me, design engineering means being able to work through a design problem and take responsibility for its implementation. You can lean towards either discipline, and you’ll still need to ask for help along the way. What matters is understanding the decisions well enough to explain them, change them and deal with what happens when somebody uses the thing. This is a little choose-your-own-adventure guide to practising that. Pick the closest starting point, even…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town