You can't force your way through a mental wall if you're using the wrong learning style.
Switching from dense text to visual tools cured his task aversion and rebuilt his confidence.
I explain complex systems hacks in a simple way!
Systems Addict - productivity, automation & a comfortable life!
Join my list : https://use.toth.al/join?utm_source=mastodon&utm_medium=social
You can't force your way through a mental wall if you're using the wrong learning style.
Switching from dense text to visual tools cured his task aversion and rebuilt his confidence.
And life is flowing ...
.. like a river to the inevitable vastness of the ocean.
Am I making the most of it, enjoying the journey? Experiencing every single meter of it with the full knowledge I will never travel this way again!
Will never see this part of existence again. In some sense, this me won’t exist anymore. Just a memory frozen in time. If that …
.. memories are changing and fading so fast!
You are likely wasting time on software tools instead of doing actual engineering work.
I once spent a week building a digital voting system for a meeting but failed to ensure my plan traced up to the actual value of the discussion!
J. F. Evans writes in Key Concepts in Systems Thinking that we must constantly focus on the core purpose of our system.
When you spend all day fixing a SysML block or formatting a document you stop directing the project and become just another worker.
I hope my mood won't hop wih the weather today ...
Procrastination (whether it's studying for a certification or the dread of updating a CV) is rarely laziness.
As a mentor your job is to help them find the right tools to overcome the resistance and build momentum.
𝗛𝗼𝘄 𝗺𝗮𝗻𝘆 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗱𝗼𝗲𝘀 𝗶𝘁 𝘁𝗮𝗸𝗲 𝘁𝗼 𝗰𝗵𝗮𝗻𝗴𝗲 𝗮 𝗹𝗶𝗴𝗵𝘁𝗯𝘂𝗹𝗯?
None. They just document the darkness as the new baseline requirement.
We stop being the organising force and become just another spinning rock. A Systems Engineer is dark matter, the one thing that holds a project together and can bring order into chaos!
An optimist sees the glass as half full. A pessimist sees the glass as half empty.
A systems engineer sees a requirement for a larger container that the current design fails to justify.
I’m a problem solver, a communicator, a planner, an analyst, and a prover.
I’m the glue that binds projects and programs together. I’m the guy you ask how something works or how it’s supposed to work, and how to fix what’s broken.
I’m a #systemsengineer
My next newsletter "Why Coffee Machines are ruining your confidence." is coming Thursday.
Subscribe to get it and stay in the loop on everything I'm creating.
https://use.toth.al/join
A mechanical engineer designs the vehicle suspension.
A software engineer writes the braking logic and adaptive suspension SW.
A principal systems engineer spends three weeks in Cameo just to prove the road is an external actor.
𝗡𝗼 𝗠𝗮𝗴𝗶𝗰! Wizardry ...
We should never do a process, or a model for its own sake!
It is there to help the business to keep in control of what you try to achieve. If it doesn't you shouldn't do it.
People so often lose sight of why they are modelling. What's the purpose.
And jump head first to build complicated pretty diagrams (that are even smart) but ultimately useless.
I'm here to stop people do it and keep reminding them to consider the purpose of their work: now they can work much more effectively.
The Rye ..
In 60 minutes I cut through the noise and identify the one thing standing between you and your next career move.
Then build a concrete, actionable plan to tackle it.
Whether you need to position yourself for a promotion, sharpen your CV, or prepare for a critical interview, we’ll leave the call with a clear next step you can act on today.
Start at https://EveryExpert.com/alex
People often ask me how to prove work experience for an interview when they are at the beginning of their career.
Others ask how to pick a path for the future while still a student.
You may already know I'm a strong believer that practical learning is the best possible learning! What's my view?
I won't faff about this more:
𝗕𝘂𝗶𝗹𝗱 𝗮 𝗿𝗲𝗮𝗹 𝗽𝗿𝗼𝗷𝗲𝗰𝘁! 𝗕𝗨𝗧 𝗸𝗲𝗲𝗽 𝗶𝘁 𝘀𝗶𝗺𝗽𝗹𝗲 𝗮𝗻𝗱 𝘀𝗺𝗮𝗹𝗹 𝗲𝗻𝗼𝘂𝗴𝗵 𝘁𝗼 𝗳𝗶𝗻𝗶𝘀𝗵. ⬇
Most ambitious engineers try to level up the same broken way: stack another certification, master another tool, wait for someone to notice. No one notices!
They end up overqualified on paper and completely invisible in the room: anxious, overlooked, and wondering if they’re the problem.
Most Systems Engineering degrees fail to prepare you for real-world industry challenges.
Why?
They prioritise ideal scenarios and textbook processes.
But 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗿𝗲𝗮𝗹𝗶𝘁𝘆 𝗶𝘀 𝗺𝗲𝘀𝘀𝘆. You will face:
• Incomplete data
• Shifting requirements
• Tight resource constraints
• Corporate office politics
👇
I asked my newest automated buddy to synthesise and distil our latest support videocall. This is the best it came up with …
Any useful?