Today I’m announcing a new project: Pro bono engineering. I will be offering a couple hours per week to those in need in an attempt to make a positive impact.
The concept of pro bono is nothing new. It is a common practice in law and medicine. Sometimes as a method for writing off hours at a tax break (though that is on shaky ground with the IRS) and sometimes as a public service; the American Bar Association recommends donating time to those in need to maintain good standing with the law community. And while engineering doesn’t really have a centralized organization for licensure (yes, the National Society of Professional Engineers acts as this for some fields), it is still an important thing to think about. Really it’s about helping people who are not able to afford services. Other precedents exist for this as well, like Engineers Without Borders (EWB), but I am not aware of this existing for electronics/tech projects.
I would love to tell you that I’m doing this solely out of the goodness of my heart, but that’s not how idea started. It primarily started because some of my skills are less sharp than they had been in the past. I have been working on a lot of things in the last 3 years, but I’ve been learning mostly outside of the field of engineering: marketing, product management, business administration. All of these things are necessary, especially for running a small business. But the core skills that I talk about and am proud of are my engineering skills. Much like my strife over selling my drums, moving away from engineering is as much an identity crisis as anything else. I am the first person to talk about the power of “learning by doing” (see also Contextual Electronics), so this is my form of that.
That’s not to say I’m not excited by the prospect of social good and helping people move their projects forwards. As you’ll see in the criteria I lay out below, the project goals will also help me decide which project to prioritize. Really instead of “social good”, I’ll try and focus on “impact”. If I can help a software engineer move a project forward for a device that helps a lot of people (even if it’s a commercial project), I’ll favor that.
But enough about the motivations, as this is really an experiment. I’ll only know it is working once I have tried it out! Let’s take a look at some of the restrictions and guidelines for projects I’m looking to work on:
- This will be no more than 5 hours per week of my time.
- You will need to pay for parts. Even when a friend mechanic works on a car for “free”, you’re often paying for the parts.
- I will be working in KiCad. This is my eCAD of choice. If there is mechanical or other work, I’ll help out how I can (have been learning Fusion 360).
- I will be talking and writing about all projects I help with. If you have a “secret” project, you probably should be hiring someone to help you out.
- There are restrictions on what I’ll agree to work on, including life-critical and dangerous projects. Really I am the only person who decides what I’ll be working on.
- Projects with existing documentation (even background info counts) will be given priority as that helps to assess the project. There is a place on the form below to add info about where to find the documentation.
So the last thing is that I am taking the “applications” for this via Google Forms. You can access the form directly here and I will attempt to embed the form below.
I am hopeful I will be able to help a lot of people and find great new people to work with. If you have thoughts or questions, please leave them in the comments below.
Thank you Antonella Beccaria for the picture of helping hands
Clayton Workman says
Commendable! I did a couple of projects this past year (pro bono) for very similar reasons.
I bet there are other people who would love to do this kind of thing. I wonder how practical it would be to pool these people together as part of some kind of non-profit for the general good of the community?