How Technical Writing Changed My Engineering Degree

[Frederic]

When I started my mechanical engineering course, I thought "technical writing" just meant adding a few bullet points to an email. Boy, was I wrong!

Last semester, we had this massive group project where we had to design a prototype and then submit a full technical report. I was so focused on the calculations and the CAD models that I totally neglected the documentation side. My project partner, bless her soul, sat me down and said, "If we can't explain how this works, all our hard work is useless." And she was right! I ended up taking a short online course in technical writing specifically for engineers, and it was a total game-changer. I learned how to write clear instructions, create effective diagrams, and structure a report so it's actually readable. The best part? Our final report got praised by the professor for its clarity, and we got top marks!

Now I actually enjoy the process of breaking down complex ideas into simple steps. It's like solving a puzzle, but with words. For any STEM students out there who think writing "isn't for them" — please give technical writing a chance. It will make your projects stand out and your future boss will thank you! Has anyone else had a moment where good documentation saved their project? Share your stories!

 

[SalmaBrown]

I'm a CS major, and I've been guilty of the exact same mindset. For the longest time, I thought my code should "speak for itself" and comments were just a waste of time. Then came a group project where I had to pick up someone else's code from last semester, and there were ZERO comments. Zero! It was like reading ancient hieroglyphics.

That experience completely flipped my perspective. Now I'm that person who writes detailed README files and comments on everything. It takes extra time, but future me (and my teammates) are always grateful. Your story about the technical report is so inspiring — it's awesome that your professor recognized the effort!

Do you have any favorite resources or templates you'd recommend for someone just starting to take documentation seriously?