157 karma · joined February 4, 2012
I designed the hardware and software for the MV-1200 and MV-1400 aircraft cameras at Astronics Max-Viz, then helped provide purple printed circuit boards at OSHPark. Now I build boards, code, and websites at Wickerbox Electronics.
Remote: OK
Willing to relocate: Yes
Technologies: Embedded systems from circuit schematics, component selection, board layout, assembly, soldering, testing to writing code for microcontrollers (embedded OS or bare metal), and FPGAs. C/C++, Assembly, MATLAB/Simulink, Python. Also VHDL and Verilog for FPGAs.
Resume: upon request
Email: jeh.wicker@gmail.com
Website: http://jennerhanni.net
Github: http://github.com/wicker
I have a Master's in Electrical and Computer Engineering. I much prefer systems integration or full-stack stuff where there are lots of pieces to go together. My recent work has been putting IR and visible camera cores together in an aircraft camera housing with custom microcontroller and FPGA-carrying boards; the code is writing C and VHDL to output blended video so the pilot can see at night and through light fog.
All my work experience has been in aviation: avionics technician, aircraft homebuilding, writing quadcopter stability code, modeling UAV payload systems at a drone manufacturer, and building hardware for 12-foot rockets that stream video and data to the ground during flight over wifi. http://psas.pdx.edu/
I would prefer work in aviation or on mobile robot platforms. I've messed around with building and control of an underwater robot.
I'm looking for either contract work that's remote and part-time or for a full-time on-site position. I just want a job where I can geek out while making a tangible product.
Are you saying you don't carry a cellphone? How has that decision impacted your daily life?
My first job was as a Marine avionics technician and I had the misfortune to work for bosses who reassured themselves by blaming you at full volume and making you feel like shit. Usually with the 'you could have killed somebody you useless idiot' which is actually not that often true. Not a great environment.
Last week I'm just starting my second year at this company as a real proper electrical engineer and I neglected to run all the steps of the pre-tests I said I ran and I therefore missed a (in retrospect, really cool) bug that showed up in front of the certifying examiner on a Friday afternoon. Said examiner costs a lot of money per hour, it's a government agency, etc. etc. I spent a weekend and Monday finding the bug and squashing it. It took til Friday before the new code was released and all the paperwork up to the certifying agency was fixed.
The whole time my boss was there and clearly frustrated but also very clearly keeping quiet. I definitely went and thanked him on Friday afternoon when it was all over for being so chill about it. He said it was no problem as he could see I had sufficiently embarrassed myself and was working hard to fix it. It's so true. I was keeping my head down, being calm but intent on the problem, and I don't know how I could've solved anything if he'd lost his shit.
Fear and care are definitely with me now. As is proper testing and better logging of my own day-to-day dev process. (Note to self: power cycle in the test when it tells you to power cycle. You're also testing the non-obvious functionality.)
Thanks for writing this, swanson. I've written on and off over the last few years but lately I've wanted to write, started to write, and then lost the nerve and never posted. Hearing "you don't have to be the next Joel On Software" helps.
Next, I usually suggest grabbing an introductory reference and a bunch of small projects (usually my go-to is Project Euler) in the language of their choice. What she's doing is exactly what I'd recommend if you were brand new and wanted to get a feel for the landscape.
EDIT: Oh right, just saw that the link's through Google Translate. My bad.
At the least, if someone contributes a ton of code for an assignment in one shot that's identical to somebody else, the professor could compare commit logs there too. Tons of code is out there on the internet and plagiarism is something that'll be tempting on the job under a deadline, too, with potentially more serious legal consequences.
I keep my code private until the class is over, then open-source it. I consider this stuff to be my resume.
I haven't seen a study which addresses how many women do this, nor a clear breakdown on how many of them do it because they've experienced harassment or are just worried about it because of second-hand stories.
What would be great would be a FOSS-only list of internships and push for a change where a remote internship was more common, which I think is more what you're getting at with how GSOC differs from existing options.
I'm at Portland State and we've got a solid six-month capstone program in computer science where local companies, including several in open source, are working with student teams. I know electrical/computer has a similar program with a more hardware focus. It's not that GSOC is the only program where companies work with students, only the most visible.