Azman Choudhury

Professor Sara Jacobson

ENGL 21007: Writing for Engineering

Throughout this roller coaster of a semester, taking this Writing For Engineering Class, I learned that writing is much more complex than simply explaining information. At the beginning of the semester, I believed technical writing mainly meant explaining how something works in as much detail as possible. I was proven otherwise very quickly. As the semester progressed, I learned that strong technical writing needs more than just explanations, it requires organization, audience awareness, credible research, collaboration, and reflection. Through projects such as my technical description essay, engineering proposal, and group work, I developed skills that improved both my writing and the way I approach larger assignments. One thing I improved on was explaining complicated ideas in a simpler way. In my writing reflection, I wrote about how good writing should be clear but still detailed. This semester helped me see that clear writing does not mean adding every possible detail. It means choosing the details that actually help the reader. I saw this in the MotoEcho proposal. Our product was a motorcycle helmet with ultrasonic sensors, a rear-view camera, a heads-up display, a microcontroller, software, and a power source. At first, it would have been easy to just describe all of those parts like a list. But the proposal had to be more than that. We had to explain how those parts worked together to help riders with blind spots and rear visibility. That made me understand technical writing better. The reader not only needs to know what the product includes. They need to know why those parts matter. This led me to learn the value of credible research and evidence in writing. Before this course, I often relied on general information or whatever source seemed easiest to access. However, through our engineering proposal project, I learned how important it is to use reliable and credible sources to support claims. While working on the MotoEcho proposal, my group and I researched topics such as motorcycle accident statistics, ultrasonic sensors, rear-view cameras, battery systems, and heads-up display technology. Instead of simply making assumptions, we had to support our claims with information from organizations, technical websites, and research sources. This process helped me understand that strong writing becomes more convincing when it is supported by evidence rather than opinion. It also made me more careful about checking whether information was trustworthy before including it in my work. This project also helped with my organizational skills. The technical description required just as many components as our product, including the introduction, problem statement, objective, product description, key components, safety benefits, challenges, investment, and conclusion. At first, a project that big felt like a lot to handle. Breaking it into sections made it easier to organize and keep track. It also made the paper easier to read because each section had a purpose and depth. I learned that organization is not only about making the paper look neat. It helps the reader follow the idea from the problem to the solution. The presentation helped me understand organization in another way. A presentation is different from a written proposal because you cannot include every detail. You have to pick what matters most and explain it quickly. That was not always easy because the project had a lot of information. But it helped me see how writing changes depending on the format and the audience. A proposal can be more detailed, but a presentation has to be more direct. The hardest lesson for me was about collaboration. In my group work self-assessment, I wrote about how stressful the MotoEcho project became. This collaboration attempt showed me how important it is to actually put in effort. It made me realize how important even small contributions can be. This taught me to be more aware of how I approach collaboration moving forward. I learned that communication and accountability are just as important as completing the work itself. Even if someone cannot contribute a large amount, consistently putting in effort and staying involved can make a major difference in the overall success of a project. This experience also taught me to better manage expectations in group settings and to step up when necessary, while still encouraging others to contribute their share. Nonetheless, this semester not only changed the way I view analytical writing but also my own writing habits. I learned that strong writing isn’t only about regurgitating information, but also about organizing ideas, understanding the audience, supporting claims with credible evidence, and working effectively with others. Through assignments like the MotoEcho proposal, technical description, presentation, and reflection work, I gained a better understanding of how to communicate complicated ideas in a way that is both detailed and understandable. While some parts of the semester were challenging, especially group collaboration, those experiences still helped me grow as both a writer and a student.