TDEB Top Bar

Trending
Semiconductor Industry News — The Digital Electronics Blog
Follow Us

TDEB Masthead

The Semiconductor Hub

Semiconductors.  Chips and Systems.  Innovation.

Indexed by leading Search Engines, AI and referenced by Engineers worldwide 500+ Articles 10M+ Pageviews 30+ Reports 50+ Citations

What Will Be Your Engineering Legacy?

The Editor's Desk
by
2
Share Facebook X LinkedIn WhatsApp Email

It is no easy task to record the achievements of individual engineers nowadays. Most engineering work is done by large teams, credited to companies, and buried inside products. It is tempting to think a lasting legacy depends on having studied at a famous school such as MIT, Stanford or an IIT and having joined one of a handful of companies known as superb training grounds. This post, first written in January 2009 in response to an EE Times article on the subject, asks a simpler question: what will your engineering legacy be, and how can you make it visible?

What an engineering legacy is

An engineering legacy is the part of your work that keeps being useful after you have moved on. For most engineers it is not a famous invention. It is a block that is reused in chip after chip, a test method the team still runs, a document that new hires read on their first week, or a junior engineer who became a strong lead because you took the time to teach them.

Why it is hard to see

  • Team credit. A chip or product carries the company's name, not the names of the engineers who designed it.
  • Short memory. Products are replaced in a few years and design databases are archived.
  • Invisible quality. The bug that never reached a customer, because your check caught it, leaves no record.

Forms a legacy can take

  • Designs that ship and get reused. A well-built IP block or library can outlive the product it was first written for.
  • Methods and tools. Scripts, flows and checklists that make a whole team faster or safer.
  • Documentation. Clear specifications and design notes that let others understand and extend your work.
  • Published work. Patents, conference papers, standards contributions and articles carry your name.
  • People. The engineers you trained and mentored carry your habits into their own teams.

Deep dive: the numbers and details

This part holds a practical checklist for making your contribution traceable. Skip it if the overview is all you need.

Make your work findable

ContributionHow to leave a record
A reusable design blockA specification, an integration guide, a regression suite and a change log that names the owner
A new method or flowA short internal write-up with measured before and after results, such as run time or bugs caught
An idea that is newAn invention disclosure through your company's patent process
A result worth sharingA conference paper or article, cleared through your employer's publication review
Help to othersTraining sessions, recorded talks, and code reviews that explain the reason behind a change

Measure what you changed

A legacy is easier to recognize when it has numbers attached. Examples of measurements an engineer can keep for their own work:

  • How many projects reused a block you designed.
  • Regression run time before and after a flow you improved.
  • Bugs found by a check you added, and at which stage.
  • Silicon issues avoided, for example first-pass success on blocks you owned.

Keeping a simple yearly log of such items also helps at performance reviews and when changing jobs.

Questions to ask yourself each year

  1. What did I build this year that someone else is now using?
  2. If I left tomorrow, could a colleague maintain my work from what I have written down?
  3. Whom did I help grow, and how?
  4. Is there an idea I should disclose, publish or present?

A note on schools and companies

A well-known school or employer can open doors early in a career, but the work itself is what lasts. Engineers anywhere can build a record of reusable designs, documented methods, published ideas and people they have helped.

The Editor's Desk
About the Author
The Editor's Desk
Share Facebook X LinkedIn WhatsApp Email

Post a Comment

2 Comments

Your comments will be moderated before it appears here.

  1. There is a lot of talk these days about a college degree being less valuable (and more expensive) than years ago. I totally agree for the following reasons:

    BEFORE - You could learn a lot of what you needed to know for your career in university.
    NOW - Half of what you learn will be obsolete before you graduate.

    BEFORE - You needed to get hired by an employer.
    NOW - You can go it yourself much easier and we're all independent contractors.

    BEFORE - It was about what you know.
    NOW - It's about how quickly you can learn new things.

    The only real value of a degree from a good university seems to be as an indicator of future success.

    ReplyDelete
  2. What you said is so true!
    Now a days education has less significance looking at what you are going to do in the industry, the industry which evolves everyday and transforms to adapt itself.

    Yes, i agree that a degree is just an indicator of the capabilities and the future success.

    ReplyDelete
Post a Comment

#buttons=(Ok, Go it!) #days=(20)

Our website uses cookies to enhance your experience. Learn more
Ok, Go it!