Engineering learnings from my first semester at MIT
November 5, 2025
- Good engineering is very rigorous, and requires a LOT of analysis. Every decision should be justified with calculations and analysis - why is this architecture better for this system, why this type of pulley or gear, why placement of this part here? Question everything, especially the assumptions which underlie the models
- Always make conservative assumptions - err on the side of caution! Apply a factor of safety for loads and forces (usually 1.5 or 2). Safety and a working part/system are the most important. Engineer for worst-case scenarios and edge cases
- To be truly passionate about something you should believe in *both* the product and the process
- In learning as well, to truly understand something you should understand both the high-level concepts and intuition, and the technical workings
- Iteration and feedback are immensely important, and very related. Be humble and aware of your unknowns, seek feedback and input from people who know more, improve and iterate
- Everything is inputs and outputs. This is quite obvious in CS, but it applies to mech e as well: if you input a load here, what deformation or stress does the system output? This is why almost everything physical can be modeled by differential equations/"everything is a spring"
- Do things well the first time around. The more well-justified your initial decisions are, the less resources you have to spend iterating. The more robust your initial design or initial code, the less you have to adjust and fix later
- Engineering in three words: readability, stability, and robustness
- Readability: can other people understand your logic and scrutinize your work. Is it followable? Good engineers communicate well
- Stability: if you change something small in the system, does it explode and diverge or does it remain mostly the same? 1 Also parameterization
- Robustness: do you account for edge cases, does the system still work under the extremes
-
differential equations definition of stability :) but it applies here as well
↩