It’s easy to get excited about a project that you are working on – in fact, it happens to me all the time.
I start working on something and as I find out more about the technical issues, or the work’s relevance in the overall scheme of things, I get more and more excited about the work that I am doing. And when I get an opportunity to present out the status of the project or brief the experts on a particular issue being worked on, I want to make sure I present as full of a picture of the project as possible. That just makes sense: good data in = good results out.
Let me admit something up front: I didn’t start drinking coffee until I turned 40.
In our current caffeinated society, where 32-ounce morning coffee thermoses are the norm, this must sound pretty backwards or maybe unsophisticated. Truth be told, I thought coffee tasted bitter and had an acidy aftertaste. Unless I put so much sugar and milk into my coffee that it started tasting like coffee ice cream, I wouldn’t drink it.
Every discipline and "domain" has its own unique jargon, vocabulary – including slang, acronyms, and more – and associated concepts. This is as true for cooking (e.g., sautee, carmelize, roue), baseball ("bases loaded," etc.), and the like.
There's no shortage of success stories on the use of project management methods like Lean and Agile to software development (which is what Agile was formulated for) or for manufacturing (Lean's origin from Toyota).
In the old days of “over the wall engineering,” all engineers had to do was throw drawings over the wall to manufacturing. That’s it. Nothing to worry about. Production planners and manufacturing folks would figure out how to make a product close to what designers were dreaming, sketching, and designing.
I’ve been fortunate having been given the chance to talk to many manufacturing companies ranging in size from small hardware startups to large manufacturing companies. In having done so, I’ve learned much from asking people about Bills of Materials, or BOM. Doing so exposes much about how a company designs, manufacturers, and services its products.
In my previous blog post, I provided an overview of what compliance certifications like UL, FCC, CE, and RoHS are, and what ones your new hardware product may need.
In this post, you'll get a sense of how much time and money your product planning should factor in to get them, along with other advice.
When my first engineering internship turned into a full-time job after graduation, my supervisor called me in for a chat. He wanted to talk about possible opportunities in the company, and give me some advice based on his experiences. When he asked me where I saw myself in five to six years, I told him I expected to be in management. I didn’t have the gall to say it to his face, but basically I figured I wanted his job.
A new year is a time for renewal, opportunity, and new beginnings. For engineers, however, it's a chance to argue about part numbers some more. I love the smell of part numbers in the morning. Whether your allegiance lies with the Generic Numbering Coalition (GNC) or the Confederacy of Intelligent Numbers (CIN), valid arguments worth defending exist on both sides. We've covered both factions and spaces in-between. The pursuit of part number perfection, however, may lie in mutually assured destruction. The part number is a lie. For one day, perhaps sooner than you think, part numbers will be no more.