The post from a mechanical engineering student captures a feeling that is far too common: the gap between learning syntax and building something real. You study Python, you watch tutorials on machine learning, and then you sit down to apply it, only to realize you have no idea where to start. That is not a personal failure. That is a structural problem with how coding is often taught. The student says they are lost, but what they are really describing is a missing bridge between knowledge and application. That bridge is not built by memorizing more functions or watching another video. It is built by choosing a problem small enough to solve, then solving it badly, then solving it again.
For engineers, the path forward is not to abandon the technical foundation. It is to stop treating Python and machine learning as abstract subjects and start treating them as tools for a specific job. If you are a mechanical engineering student, your advantage is that you already have access to problems. Heat transfer, stress analysis, fluid dynamics, optimization of a simple mechanism. These are not hypotheticals. They are your homework, your labs, your projects. The practical move is to take one of those problems and force yourself to model it with code, even if the code is ugly, even if it only works for a single case, even if a more experienced programmer would laugh at it. The goal is not to write good code. The goal is to connect what you are learning to something you can touch.
What holds most beginners back is not a lack of ability but a lack of context. When you learn Python by itself, every exercise feels like a puzzle with no purpose. When you learn it to calculate the deflection of a beam or to predict when a pump will fail, the purpose is already there. The motivation follows the meaning. So if you feel lost, stop looking for a better course or a smarter tutorial. Look for a smaller problem. Break it down. Write a script that does one thing, even if it is just reading a CSV of temperature data and plotting it. Then add one more thing. Then another. The learning will not feel like a climb anymore. It will feel like building a tool you actually need.
The student is not behind. They are just early in a process that does not have a clear map. But the map is not a curriculum. It is a habit of connecting new skills to old problems. Start with something that matters to you, even if it is small. That is not a motivational slogan. It is the only practical way to move from lost to learning.