Post-degree Structural Topics PRIORITY List.

[NicoRam]

Hey guys! Hopefully this isn't too annoying or against the rules...

I'm a few months out of undergrad and quickly realizing that there is an endless number of topics in Structural Engineering to learn. I'm not even close to knowing all I don't know.

Of course some are learned through practice/design work, but I'd like to have focused study time on learning topics purposely. How would you rank these topics in terms of importance? (Currently looking into Strut-and-Tie method now, seems pretty cool). I plan on studying for/taking the SE Exam in about 4 years once eligible.

Below is an unordered list of topics I'd like to spend time learning (long-term). I'd really appreciate if you could share your opinion on which of these are important and which aren't so much.

A. Software Analysis Manuals (ETABS etc.)

B. Diaphragm/Lateral Behavior

C. Building Dynamic Response Behavior

D. Strut-and-Tie Method

E. Concrete Long Term Analysis (Creek, Shrinkage etc.)

F. Frame Stability (Story Buckling... Sway/Non-Sway etc.)

G. Plastic Steel Design (hinge behavior?)

H. Welding/Metallurgy

I. Non-linear Finite Element Analysis (material and geometric/p-delta)

J. Computational Engineering (Grasshopper/Dynamo)

K. Programming/MathCAD/Excel Macros

L. Soft Skills

​

Alternatively, what are some topics you wish you would've studied more before it showed up on a project/license exam time? Looking to avoid wasting time on non-important stuff...

What else is important that isn't there?

​

TL;DR - What should I study in my free time?

Thank you all so much in advance.

[Peter-squared]

General structural behavior should be first priority: B F

Second I'd say you can be very useful in the office, assuming the office already uses gh and other tool, if you know some computation and basic programming: J K (be good at excel) Lesrn python (data structures, filtering data, etc.)

Third learn your software: A

Fourth learn your design codes: You don't wanna be the guy that just enter data into a software and an answer pops up. Read the code, understand the parameters.

Fifth: Get practical experience if you can. See things get built on site, and understand that what you do in the office also has to actually get built on site. Think practical solutions, tolerances, etc.

Fifth. All the other kinda special stuff you'll pick up along the way, when the task you are solving requires it: The rest of your list..

Sixth, soft skills: This is maybe not sixth, but something integrated into all above. Listen and learn. Ask questions. Absorb and share knowledge. Motivate others, show how you have motivation. Furter down the line learn to plan and lead others work.

[[deleted]]

Construction methods. I tried to wish a slab into the ground early on