AstroMechLab

   When we start learning engineering, most of us focus on components. Motors. Sensors. Controllers. Code. But as problems become bigger-in robotics, satellites, or real-world systems-components alone stop explaining behaviour. That’s when  systems thinking  becomes important. And at the heart of systems thinking are three simple ideas: inputs, outputs, and boundaries . They sound basic. But misunderstanding them causes more engineering failures than complex mathematics ever will. 1. Why Systems Thinking Matters Engineering problems are rarely isolated. A robot doesn’t just move. It reacts to its environment. A satellite doesn’t just orbit. It responds to disturbances, delays, and limitations. To understand such behaviour, engineers don’t ask: “Which component is this?” They ask: “What are the inputs, what are the outputs, and where is the system boundary?” This shift in thinking changes everything. 2. What Is an Input? An  input  is anything that enters a ...

As engineering students, we use the word system almost every day. Control system. Robotic system. Satellite system. But for a long time, I personally used this word without ever stopping to ask a simple question: What does “system” actually mean in engineering? I could solve problems, follow block diagrams, and even run simulations — yet the idea of a system always felt abstract. This blog is not a textbook definition. It’s my attempt to clearly understand what a system really is , based on how engineers think, design, and analyze real problems. 1. A Simple Meaning (Without Overthinking) In the most basic sense, a system is: A set of interconnected parts that work together to achieve a purpose. That’s it. Multiple components directing their interactions toward a single outcome. But this definition hides three important ideas: parts are connected behavior comes from interaction the system exists for a purpose If any one of these is missing, you don’t really h...

 As engineering students, we often say things like “I understand this topic” or “I’ve studied this concept.” But when it’s time to apply that knowledge — in a project, simulation, exam, or real system — things suddenly feel unclear. So the real question is: What does “understanding a concept” actually mean in engineering? Is it memorizing formulas? Is it solving numericals? Or is it something deeper? From my learning experience so far, true understanding in engineering goes far beyond textbooks . 1. Memorizing Is Not Understanding Let’s be clear first. If you can: recall definitions write formulas solve only familiar problems that does not automatically mean you understand the concept. Memorization is just data storage , not comprehension. Many students can write equations for torque, PID control, or orbital motion — but struggle when: parameters change assumptions break systems behave unexpectedly That’s the gap between knowing and understandin...

In engineering, it is easy to feel that learning faster means learning better. Advanced topics, complex software, and sophisticated systems often look more important than spending time on basic ideas. As a student, I have felt this pressure as well. Over time, however, I have realized that many difficulties in engineering come not from complexity, but from weak understanding of fundamentals. This post explains why strong fundamentals matter more than early exposure to advanced topics. Moving Fast Does Not Always Mean Moving Forward Learning advanced material can give a sense of progress. Solving complex problems or running simulations feels productive. But when the basics are not clear, this progress is often shallow. Some common signs of this are: Using formulas without knowing where they come from Applying methods without understanding their limits Getting results but being unable to explain them clearly These problems usually appear later, when systems become more comp...

 AstroMechLab is a space where I document what I’m learning as a mechatronics engineering student interested in space science, satellite systems, robotics, and bio-inspired engineering. This blog is not about shortcuts, viral content, or surface-level explanations. It is about understanding concepts properly — why things work the way they do, how theory connects to real systems, and where common confusions come from. As a student, I’ve often felt that many resources either oversimplify topics or jump too fast into advanced material without building foundations. AstroMechLab is my attempt to bridge that gap. Here, you’ll find: • Conceptual breakdowns written in clear, simple language   • Step-by-step explanations of core engineering ideas   • Notes from my own learning, experiments, and projects   • Connections between fundamentals and real applications   This platform is intended for engineering students and early researchers who want to thin...