CJSTEELE
  • Home
  • About
  • Contact
  • Blog

The Global Engineer Blog

​Becoming a Domain Expert – Fast and Simple

13/9/2026

0 Comments

 

Or: How to blitz the competition in the long run

An informed engineer outpaces the competition - rowing metaphor
As a global engineer, you are more likely to take on a role where you know less about the specifics of the domain than others. The reason for this is that you would be chosen for that role because if you understanding of engineering and your ability to adapt. That means you need to know how to pick up domain knowledge fast. Also, as any kind of engineer, you want to be continually improving so you can stay ahead of anyone you might be competing with – either to get a new role or maybe even keep your own.
In this article, I am going to talk to you about simple, no-nonsense methods that can help with this.
Domain expert fast and simple
In my book I shared an experience where I was working on a medical device that was controlling the delivery of fluids via drops. The idea was that if the system could produce consistently sized drops, then the precise volume could be delivered by generating a set number of drops.
I had little idea what determined the size of a drop. I knew it would have something to do with gravity and surface tension, but that was about it. I would not have been able to calculate the expected size for any given system.
Not only that, courses on drop formation are less than rare on sites like Coursera and Udemy. So I would not be able to do a crash course on the topic.
Instead, I went straight to Google Scholar. And I found a number of articles on the topic.
In case you are wondering, the drop size depended upon the following:
  • Flow rate
  • Viscosity
  • Orifice size
  • Gravity
  • Density
  • Surface tension
What’s more interesting; the greater the flow rate, the bigger the drop. The viscosity slows the formation of a weaker shape so the faster you get the fluid in the more that will be in the drop before the neck narrows and breaks.
It would have taken me far too long to work that out. And no-one else on the team knew about it. I became the domain expert in about half a day.
And this was before AI was as well established as it is now. If you were to ask any AI system to extract the key information from recent papers on any domain you choose, then you would have a custom white paper on that domain.
Still, don’t underestimate the value of a course if available.
When I started working in the optics industry, I found an excellent course on Coursera about optical engineering. I assume that, like me, you enjoy learning and even more so when it can be applied. So not only was I gaining the expertise I needed, but I was also having a good time.
In summary, it is simple: look for knowledge sources, from courses to research papers, and start studying – and use AI when needed.
Blitzing the competition
When was the last time you re-read any of your textbooks?
I know I would not re-read them often if not for the fact I have them on display in my study. I am thus compelled to look at them, and then randomly pull one out and read a part of it now and then. A friend of mine was more disciplined; he resolved to read two pages a day as he steadily worked through all his textbooks.
You might have heard of the Ten Book Rule. The idea is that if you read 3 books then you know more than 90% of people. Read 10 and you are an expert. The numbers are not important – what’s important is the notion that if you put in the effort to learn (or often re-learn), then you will be more expert than others.
What’s your Google Scholar Alert keyword?
Did you know that you can get Google to send you an email each time a new publication comes out that includes a keyword (or phrase) you choose? Mine is “engineering cognition”. This is because of my field. However, you could choose anything you like. Either for your current role or maybe even one you want to gain.
It might take a bit of tuning – I was getting bombarded with emails with some of my early keywords – but, eventually, you will get regular email updates with the latest in your area of interest. Read them or get an AI summary, and you will be blitzing your competitors with the extra knowledge you have.
Is this a shock to you?
 You would not be the first engineer to have thought that once they finish their degree, they are done with such study.
But that’s good for you.
While the rest take no action, you can move ahead of the pack or even join a new one. If you choose to.
0 Comments

​Are you a trapped engineer, but you don’t know it?

6/9/2026

0 Comments

 

Or: Be honest: Has your past professional experience been good for you?

An engineer in chains trapped by past experience and habit
Many engineers do not realise how much they have been limited, both skill-wise and success-wise, by their professional experience. They have just accepted it for what it is, along with its effects upon themselves, and not thought to correct for any limiting issues – they are thus trapped and don’t even know it.
Let’s talk about how you can tell if you are trapped and how to break free.
First off, I should note that my experience, especially in the early stages, was pretty good. So I should state that this is not a case of me living something out myself and then saying, “and you can too!” However, I still learned that my experience was not perfect, and I did need “escape” in a way.
So what are some signs you are trapped?
  • You feel you do good work, but people still seem to have issues with what you do.
  • You have a fixed notion of how administration should be run – maybe you think there should be none – regardless of the size of the company or the nature of the engineering work being done.
  • You feel you need to always defend your work or remind people of what you have done.
  • You are afraid to share any idea until you have it fully evolved.
  • You work on your own tasks without engaging others working on peripheral or related roles.
  • You follow a few guiding principles doggedly and don’t trust anyone suggesting deviation from them.
  • When you are presented with an idea that is different, and seems odd, your emotional response overrides your engineering mind, and you dismiss or criticise instead of analysing.
  • You expect there to be a prescribed process to solve each problem encountered.
  • You like the idea of the engineering department being separate from all others so you can do as you wish.
It might be hard to see the common theme in the above idiosyncrasies, but the root cause is working in an organisation that did not encourage good engineering practice that is aligned with the company size and business model. In such situations, the following can happen:
  • An influential mentor will instil in other engineers what has worked for them but is not universal. This one is one of the most common.
  • The administration system is not designed or updated for the organisational needs. So it never supports the engineering team by helping to track or guide progress and documenting successes. And it is therefore always a burden for all engineers.
  • There is no established culture of suitable exploration. And engineers are either criticised for thinking of something different or expected to implement set processes and solutions.
  • There is no system, formal or informal, that encourages the engineering team members to engage each other or people from other teams.
An engineer working in this kind of environment will not develop the engineering attributes that allow them to grow into a professional engineer. Instead, they will simply survive the environment – and become reactive engineers just trying to get by from day to day. This becomes habit, and the engineer is then trapped in this mindset.
How to escape this trap.
The good news is that you do exactly the same thing as any other engineer who wants to improve. You need to focus on applying the attributes of the expert engineer regularly. I cover these attributes in detail in my book, but the key points are:
  • You work on framing and reframing problems that are given to you.
  • You think systemically when solving challenges.
  • You apply first principles to assess ideas and inform your decisions.
As you continue to develop these attributes, you will break off the shackles of your prior work experience. You will then be free – and no longer trapped.
Once you are free, you will then be able to consider other aspects of your engineering ability. Things like your cultural, national and economic background. Then you are working toward being a global engineer.
And if the company you work for does not support this, then it’s time to leave. And you know what kind of company you do want to work for – so you won’t leave one trap just for another.
0 Comments

​The True Age of Engineering Documentation is Coming

26/4/2026

0 Comments

 

Or: How you can instantly become the old guy who has seen it all!

A young engineer who has acquired decades of expeirence
As an engineer, you probably don’t like the documentation side of things. You should at least see its value, but, in my experience, engineers are usually not fans.
We know that it protects the organisation, supports future work, and helps others understand what we have done. And yet, under time pressure, documentation is often the first thing to be condensed, deferred, or quietly abandoned.
This is not new.
But there is going to be a new pressure to create even more documentation.
Not because management suddenly cares more. Not because standards have become dramatically stricter.
But because the value of documentation has fundamentally changed. And it’s because of AI.
How AI Will Make Documentation More Valuable
Historically, documentation has been hard to use well.
It was often written because it needed to be and then just left. People might refer to meeting minutes to double-check their deliverables. But usually, it would be left until there was an audit or something official like that.
And that meant it was written in a way that was only useful for such things. Which in turn meant that it was hard to use for other things. Things like:
  • Understanding why an engineering system was set up the way it is. Ideal for new members of an engineering team.
  • Knowing if options had been considered or tried – and if they would work or not.
  • Explaining how the system works – to engineers and non-engineers.
This was, and is, a great loss. People could easily make the same mistakes or not understand the system well enough to think of improvements.
AI changes that completely.
With comprehensive documentation of an engineering project (design decisions, options considered, trade studies, constraints, assumptions, experiments tried, and outcomes), it is possible to interrogate all of it quickly.
Not by reading everything line by line, but by asking the question you want answered.
Interrogating Engineering History
Imagine you are looking at an existing engineering system and considering a change.
If you have good documentation, you can now ask an AI system questions like:
  • Was this kind of change considered previously?
  • What alternatives were explored at the time?
  • Was something similar attempted and found to fail?
  • What constraints drove the original decision?
  • What assumptions were critical—and are they still valid?
The AI does not invent the answers. It mines your own engineering record.
This documentation becomes your operational knowledge.
You won’t repeat the same mistakes and you can better assess new ideas with the knowledge you now have. It’s like you have become the old guy in the company who has seen it all!
Documentation Will Be Demanded More – Because It’s Easier
There is definitely a certain irony here.
The same technology that makes documentation more valuable also makes it easier to produce. Engineers can now:
  • Dictate notes instead of typing them
  • Generate concise summaries from long discussions and disjointed meetings
  • Convert rough thoughts into structured explanations
  • Maintain logs with minimal friction
As I mentioned in the previous article on one-pagers, AI can help you turn raw notes into something readable and useful. That capability will remove many of the traditional excuses for under-documentation.
And once that happens, the expectation will shift.
If documentation is easy and highly valuable, it becomes harder to justify not doing it.
For the Global Engineer (and Company)
This matters even more in a global engineering context.
When documentation exists, AI allows it to be repurposed for different audiences.
Language barriers are reduced. Differences in writing style, cultural expectations, and technical depth can be adapted on demand.
That means documentation no longer has to be perfect for everyone. It just has to exist. Making it easier again for an engineer to work anywhere in the world.
It also means an engineering company can be more robust.
Engineering teams change – sometimes when you least expect it.
People get reassigned. Projects ramp down. An entire engineering team gets taken out by food poisoning at a corporate barbecue.
When a new team comes in, good documentation plus AI dramatically reduces the recovery time. New engineers can interrogate the history of the project instead of starting with fragments and assumptions.
Think about all the lunar exploration knowledge that needs to be relearned with the recent efforts to return to the Moon.
Knowledge that can be reused, transferred, explained, and interrogated is far more valuable than knowledge locked inside a few people’s heads. When all past experience within a company is documented and easy to use, it increases the value of the company’s intellectual property by orders of magnitude.
And an engineering firm would be foolish not to demand all knowledge now be documented.
The Shift That’s Coming
Engineers are probably going to be asked to document more than they ever have before.
You might not like it. You might resist. But, as the above shows, the payoff will be real.
The best you can do now is start using AI to make this documentation easier to generate and then be mindful to use AI to access that documentation (and others) in the future.

0 Comments

    Author

    Clint Steele is an expert in how engineering skills are influenced by your background and how you can enhance them once you understand yourself. He has written a book on the - The Global Engineer - and this blog delves further into the topic.

    Archives

    October 2026
    September 2026
    August 2026
    July 2026
    June 2026
    May 2026
    April 2026
    March 2026
    February 2026
    January 2026
    December 2025
    November 2025
    October 2025
    September 2025
    August 2025
    July 2025
    June 2025
    May 2025
    April 2025
    March 2025
    February 2025
    January 2025
    July 2024
    June 2024
    May 2024

    Categories

    All
    3-body Problem
    AI
    AND Vs OR
    Attachment
    Attention
    Attitude
    Autarky
    Automotive
    Best Engineer
    Budgets
    Business
    Calculations
    Capitalism
    Career
    Casestudy
    Change
    Chief Engineer
    Communism
    Concurrent Engineering
    Creativity
    Culture
    Data
    Decision Making
    Design
    Design For Design
    Development
    Dimensional Analysis
    Documentation
    Economics
    Education
    Employment
    Engineering Cognition
    Engineering Philosophy
    Engineering Teams
    Entrepreneurship
    Experiments
    Expertise
    First Principles
    Fixation
    Focus
    Food
    Framing
    Gender
    Globalisation
    Globalization
    Government
    Heart Pump
    History
    Indian
    Ingenuity
    Innovation
    Intuition
    Invention
    Knowledge
    Language
    Leadership
    Library
    Luck
    Manager
    Mathematics
    Maturity
    Medical
    Meditation
    Meeting
    Mentorship
    Military
    Modal Shifting
    Negligence
    Optimisation
    Optimization
    Paradox
    Political Correctness
    Politics
    Problem Solving
    Product Review
    Professionalism
    Project Management
    Protégé Effect
    Protégé Effect
    Race
    Real Engineering
    Religion
    Retro Enigneering
    Rockstar Engineer
    Safety
    Science
    Self Sufficiency
    Self-sufficiency
    Sensing
    Sex
    Shared Situational Awareness
    Simulation
    Software Engineers
    Spacex
    Stupid Things Engineers Have Said
    Systemic Thinking
    Tariffs
    Technology
    Thinking
    Tier Analysis
    Tools
    Trade
    Transferable Skills
    Trump
    Visualisation
    Western
    What Would An Engineer Do
    Willpower
    Wokeness

    RSS Feed

Proudly powered by Weebly
  • Home
  • About
  • Contact
  • Blog