As a mechanical engineer, Statics (a course all about calculating internal forces of non-moving structures) was the course that made the difference. It had almo

As a mechanical engineer, Statics (a course all about calculating internal forces of non-moving structures) was the course that made the difference. It had almost nothing to do with the content---I think about internal forces of a thing about once a year---but that was the course where a structured and reliable engineering process was first introduced: • Draw the full system • Split into parts • Build a free-body diagram of all parts • Build an equation for every point of interest. For statics, the sum of all forces is zero and the sum of all "torques" is zero. Start here every time. • Identify all "knowns" and put them in one place. • Identify all "unknowns" and group them in a second place. • DO NOT PROCEED UNTIL # of equations = # of unknowns! If this isn't true, you need to think harder about what equations are missing, start making assumptions, or change the points of interest (e.g. from method of joints to method of sections). • Be prepared to defend your assumptions (gravity, friction, mounts, reference frame, material properties) • Make sure all signs "match" and make sense. • Solve, step-by-step, equation-by-equation. • Make sure all units match and make sense. • Sometimes ignore intuition. Parts that look like tension can be compression and vice versa. (If you need an example, those "impossible floating tables" can confuse a lot of people's intuition about force equilibrium.) • All work should be clearly organized and clearly marked---especially the answer, with proper units. ... and as a bonus ... • You can't push a rope.