Thoughts on STEM education, sustainable business, women engineers, etc. 

Feeling Like an Imposter and 3 Ways to Move Past It

I am not a good programmer. My brain doesn't think in loops. Despite taking courses in college, completing homework assignments, and trying supplemental learning through code academy - I've never reached a point where I can easily write code. As a result - I dread it. Obviously, it's more fun to do what you're good at all the time. But as an engineer you can't avoid programming forever and for the past 6 months it has been the elephant in the [my] room. Some days I have victories and feel awesome; other days, like yesterday - I spend the entire day trying to make something work and it doesn't. Then (truthfully) I usually lose my shit at someone in my life - my parents, my boyfriend, or any of my lovely friends. 

Because the engineering world so highly values strong technical skillsets, having programming not be your thing can be defeating. It makes you feel like you don't have a place in the discipline sometimes. I'm great at asking the right questions; but I wish I was better at finding the answers. While the PhD has given me a lot of opportunity to engage with things I am good at and enjoy [design, systems mapping, tech for dev, impact assessment, etc...] it's also made me jump through a bunch of technical hoops that haven't been fun for me. I get the argument that I'm better as a result however that still doesn't replace the fact that the process is discouraging. Anyways, when I'm feeling like an imposter and that I have no idea what I'm doing here are 3 ways I work around it: 

1. Take a walk: This is the most immediate. When I am sitting at my computer and cannot figure out either what I'm doing wrong or what I should do next I go outside and take a walk. I remember when I was deciding between MIT and Berkeley I had the thought, "At MIT I see myself being stressed out and cold." Turns out -- I was totally right. The PhD process is incredibly stressful. I never take for granted the ability to walk outside at Berkeley, enjoy the sunshine and see a view of the bay. It lets me clear my mind, refreshes my motivation, and ultimately reminds me there's a lot more to life than programming. 

2. Remind myself I don't have to be good at everything: No one is good at everything. No one. When I'm feeling frazzled I take a second to remind myself what my strengths are and why they're valuable for engineering. I'm great at (and love) framing questions, building a storyline around scientific research, and helping others do those things as well. That's where I see my career heading. I'm never going to be a data scientist. And that is okay. 

3. Ask for help: The best part at being at a top university? There are a ton of smart people around. The other day I was feeling stupid but finally got frustrated enough to ask for help. The first person I asked -- who is a rockstar programmer -- didn't know how to help me because it was more of a math question than a coding one. While I wished that he would've had all the answers it served as a nice reminder that this stuff is HARD. harder than I give myself credit for. That gave me the courage to ask a second person for help which was incredibly beneficial for my work. 


Development Engineering: What it is and Why it Matters

Over the past month, Julia Kramer (fellow PhD student, Clevelander, friend) and I put together a piece outlining what constitutes the emerging field of development engineering, how it's different from engineering, why it matters, where it started, and where it's going. Julia and I both were lucky enough to get involved with development engineering programs during our undergrads (at Penn State and Michigan) and so have been thinking about the nature of development engineering programs for some time now. Writing the piece provided a great opportunity to reflect on our academic space and think about how the ecosystem could change to lead to greater levels of social change. The full article from Impact Design Hub can be found here and the introduction is below! 


Development Engineering: A Critical Overview

Development engineering is an emerging field that brings together communities, businesses, students, faculty, NGOs, and governments, as well as for- and non-profit organizations, with the intention of working collaboratively to solve global challenges. It is, by design, a multidisciplinary field that bridges engineering with social sciences such as economics, public health, and gender studies alongside business and entrepreneurship for societal benefit. In order to understand where this new field is headed, both independently and within the broader context of impact design, it’s important to understand where it came from as well as its current state of development, which is what this overview sets out to do.

The history that paved the way for the emergence of development engineering, as well as the drivers behind it and the core tensions that currently characterize it, will all be explored here from our perspective: two current PhD students in the Development Engineering program at U.C. Berkeley. The authors have seen the academic side of development engineering within the university setting as well as the entrepreneurial side, a perspective gained through each having run technology-based ventures in the healthcare space.

Because it’s a nascent and rapidly growing field, development engineering has its challenges, as all sectors of impact design do. However, this growth is coupled with an increase in opportunities to both accomplish the social work that the field sets out to do, as well as to begin addressing the internal challenges development engineering faces. Thus, the field has significant potential to make impactful changes to the contemporary social issues faced by society at local and global levels.

Read more!