So, you want to hire a new engineer.
I have dabbled in programming at all layers of computer science: from Hardware Description Languages to AI.
In this page I'll make my case to you that I can fulfill your requirements. My greatest asset, it must be warned, is my motivation to learn.
Table of contents
Behaviors that will save you labor time and improve outcomes
No BS.
It is easy to tell busywork from real work. The distinction should be clear, but too often isn't.
Interruptions are the devil
Interruptions are ruinous for people who depend on deep focus. I seek to keep collaboration time as concentrated as possible each day to leave room for the "action" in action items.
Think like an economist/statistician
Thinking about projects, tools, and everyday design decisions in terms of tradeoffs, expected values, and opportunity costs improves decision-making.
Decisions are not only made by managers, but every individual contributor asking for advice or help or embarking on a new project will make many technical decisions they fully own. Being aware of these concepts is useful far beyond business school.
Feedback should be as open as possible
Constructive feedback and the free flow of concerns and praise within the company are required components for quality to improve, for problems to be addressed, and for merit to be recognized.
Constant comments are not necessarily productive or effective, but openness and a high enough frequency are.
Hard skills that will help get your requirements built in time and on budget
Stuff I have worked with for over a year
Things I've worked with for the past year
Things I'm dying to learn
Other things that don't have a good icon for them:
- Operating systems: very early days, but scheduling is a wonderful problem to lose hair over
- Assembly languages: only played with a toy assembly language so far as part of ECS, but it's great fun