As I look back on my work this semester for this class, I notice how much my approach and thought process to writing has changed. At the beginning, I mostly thought technical writing was about sounding formal and following a certain format, the cookie cutter standard of intro,method and conclusion. As the weeks passed and I worked through each assignment, I started to understand that technical writing is in essence about communication. It is about thinking through who will read the document, what they need to understand, and how I can make the information clear and useful. Each project I wrote helped me see different parts of this process, and together they show my development as both a thinker and a writer.
The first major moment that made me aware of audience and purpose happened during the technical description assignment on the magic lantern. Before this class, I had never written a technical description of a historical device, and I was anxious to start. I quickly realized that readers can be like me or a peer, and writing for someone I know to get my message across seemd to work and easy my worries. Technical documents didn’t sound like writing out a shopping list. The writing needed care and explanations of how the pieces worked together and why the design mattered. I remember revising sentences to make sure I was defining key terms in a simple way without losing accuracy. I also reorganized the description so the reader could move step by step through how the lantern produced an image. This was when I first started to understand that technical writing depends on anticipating the reader’s needs. I can see that shift clearly when I compare my early draft to the final version especially when I wrote the revised version, thinking about what I would like to see in a technical document.
My memo on campus accessibility helped me grow in a different way. This time, the writing situation felt more realistic and professional, it brings me back to when I worked in an office. I was no longer just explaining a device. I was trying to communicate a real issue on campus and persuade an administrative audience to consider improvements. Writing the memo encouraged me to think about tone, politeness, and clarity in a way that sounded professional yet not demanding. The tone of the memo was something I struggled with greatly, and I feel I would still struggle with well into the future.differently
The lab report on risk and hazard assessment strengthened my ability to use research in a disciplined and organized way. Lab reports require precise writing, and I learned that every claim needs support from data or a credible source. I had to search for stronger background information after realizing my sources were too broad. Through that process, I learned how to evaluate whether a source is reliable and how to integrate research without overwhelming the reader. One moment that stands out to me is when I rewrote the entire discussion section multiple times trying to find a way to express the importance of communication in all fields of engineering not just civil.
The group project on flood mitigation was probably the assignment that pushed me the most. Working with others made me think about writing as a shared responsibility instead of something individual. Our group collected a large amount of research at first, but we struggled to bring it all together into a focused proposal. After reviewing peer feedback, we realized that we needed to synthesize the information rather than simply place it side by side. Synthesis is something I’m used to since I love to research, but in a group setting it requires making decisions about what truly supports the argument. It also requires clear communication within the group so everyone understands the direction of the project. Revising our literature section taught me how to blend multiple voices into one unified tone.
Revision itself became an important part of my growth. In the past, I used to think of revision as fixing grammar or adjusting small details. This semester helped me see revision as rethinking the document at a higher level. At different times, I had to reconsider my structure, my opening paragraphs, my evidence, and even my explanations. For example, in my technical description, I moved the historical context to a later section because readers needed to understand how the lantern functioned before learning its history. In the memo, I rewrote my opening to make my purpose clearer from the very beginning. These changes taught me that revision is not just editing but reimagining the document so it communicates more effectively.
When I look across my portfolio, I can see evidence of my progress in each piece. I learned how to analyze audiences, write with clarity, synthesize research, collaborate effectively, revise meaningfully, and write responsibly. More importantly, I feel more confident in adjusting my writing style depending on the situation. Technical writing now feels like a skill I can carry into other classes and into my future profession. I still want to continue improving, especially in making long documents more concise and in integrating visuals such as diagrams or tables. But overall, I believe I have met the learning objectives of the course, and I can see my growth clearly through the work I’ve done.
