Terms like "professional" and "engineer" are bandied about in the software world. A lot of us are engineers by title, and most of us would like to think of ourselves as professional.
But what do these two words really mean?
I think the answer to that question can help you understand how to proceed in lots of tricky work situations:
- Should I be cutting corners on the quality of my work?
- Is it OK to express strong emotions in the workplace?
- When can I get my way?
- When do I compromise?
This blog will lay out what it means to be both "professional" and an "engineer" for those of us building software for the web.
We'll go into detail on each of these, but at a high level here's what I think makes for a professional web engineer...
An engineer:
Knows the materials — You understand the properties of different materials, tools, and patterns, and can choose options which are fit to purpose.
Documents the decisions — Numbers are crunched and shared, reasons for decisions are made clear. Available tradeoffs are presented.
Works within a code of ethics — You don't design a bridge you think is dangerous.
A professional:
Is efficient — You don't waste your time, and you don't waste other peoples' time.
Is accountable — When you screw up, you make it right.
Works well with different kinds of people — You don't just have one specific kind of person you can work with. You do the work to allow folks from many backgrounds to be comfortable working with you.
The web:
- Is whatever software you can deliver in a web browser.
Follow @erikpuk on Twitter to follow as we learn how each of these goals plays out in practice.
Image credit: Dave Lauretti
Top comments (0)