Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
    • Asset Reliability @ Work
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
    • Reliability Engineering Management DRAFT
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • An Introduction to Reliability Engineering
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Christopher Jackson Leave a Comment

Do Degrees Hurt or Help?

Do Degrees Hurt or Help?

Remember how we were told as kids in school that we had to study hard to get into college or university? There was that ongoing, implied threat that not getting into university or college would ruin our career. Or at least, be very bad.

It turns out it may not be that bad after all. For example, over half of Apple’s employees don’t have 4-year degrees. Why?

Coding. University graduates can’t do it. Sure, there are software engineering degrees where you learn what coding is and different coding approaches that can be objectively assessed in exams. But coding is an art. It requires on-the-job experience, learning from others, being allowed to make mistakes, getting used to working for deadlines and all the other things that matter in the real world.  Things you can’t test in an exam.

It’s not just Apple challenging the importance of 4-year degrees. Google, IBM, Bank of America and Hilton are just a few of the increasing number of companies that don’t require 4-year degrees for new employees.

In many ways, coding is like real-world reliability engineering.

Reliability engineering is a unique beast. We all know (or at least feel) that probability and statistics are important parts of designing reliability into something. But reliability happens at points of decision. Design decisions. Manufacturing decisions. Maintenance decisions.

If you’re all about probability and statistics, but not better decision-making, then you aren’t a real-world reliability engineer. Which is why universities and colleges continue to let our industry down.

I often talk about ‘ponderous professors’ – stereotypical reliability engineers who love probability, statistics, analysis and testing. There are thousands out there. The person who does ‘statistical stuff’ down the hall. He gets invited to lots of meetings, but when we are ready to design something reliable, our ‘ponderous professor’ demands more data, more time, or both before they give you any helpful, practical guidance. Which they never end up providing until after something bad happens.

Maybe you know one. Maybe you know a ‘highly accelerated life testing’ or ‘HALT guy’ whose answer to everything is HALT. Maybe you know a ‘failure mode and effects analysis’ or ‘FMEA guy.’ These are people who focus on solutions before understanding the problem. People who are so one-dimensional that they try and keep reliability engineering in their very small comfort zone. People who solve the problems they want to solve and not the problems they need to solve.

I have post graduate degrees in reliability engineering. I have worked at two universities. I have seen these ‘ponderous professors’ multiply in artificial, academic safe havens. Free from real-world predators (like commercial insolvency). And most of them weren’t interested in real-world reliability engineering.

Real-world reliability engineering focuses on what your organization is trying to achieve, what it values, what it defines success to be, and then working out how reliability engineering helps you get there. My degrees really help me find solutions for some problems. But not all. It’s not even close.

So if you are a young professional reliability engineer plotting your way forward in life, make sure you remain a real-world reliability engineer. A degree might be part of your professional development plan, but it can’t be your only professional development plan.

 

Filed Under: Articles, on Product Reliability, Reliability in Emerging Technology

« Failure Reporting, Analysis and Corrective Action System (FRACAS)
The Importance of Post-delivery Feedback »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Article by Chris Jackson
in the Reliability in Emerging Technology series

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Posts

  • Terrorism Risk Insurance Act Exclusions: Gray Coverage Areas
  • Why Total Productive Maintenance Is The Answer To Reliability-Centered Culture
  • 17 Powerful Insights on Effective Communication Using FINESSE
  • Surprising Insights from Simple Run Charts
  • Risk is Round

© 2023 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy

This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.