Self Assesment
Professor Pamela Stemberg
Syed Rahman
05/22/26
Coming into this course, I assumed writing would be the least technical challenge of my engineering curriculum. I was wrong. Scientific and technical writing has its own rigor, and learning to meet that standard reshaped how I communicate as an engineer. Below, I reflect on the course learning outcomes I fulfilled and how each one contributed to my development.
The first outcome, acknowledging linguistic differences as resources, became most apparent through collaborative work. Peer review worksheets after every draft gave me perspectives I wouldn’t have considered working alone, which mirrors how engineering itself actually functions. This dynamic was equally valuable during the group lab report: some teammates were stronger at interpreting data trends and variable relationships, while I focused on structuring and communicating those findings clearly. That division of strengths produced a more complete document than any one of us could have written independently, much like how engineering teams divide technical responsibility on a real project. Practicing library and database research was a skill I underestimated coming in. For the literature review, I had to move beyond Google and learn to navigate academic databases strategically, using precise technical keywords to locate credible, peer-reviewed sources. Finding three original research articles that were parallel in methodology and findings, and then synthesizing them into a coherent narrative, taught me that sourcing in engineering writing is as deliberate and systematic as any design process.
Genre analysis reshaped how I read and write technical documents. Comparing journalistic coverage of engineering topics with actual research papers made the differences in audience and purpose impossible to ignore. Journalists simplify and sometimes editorialize; researchers hedge claims carefully, maintain objectivity, and let data drive conclusions. As an engineer, the scholarly model is closer to the professional writing I will produce, as technical reports, feasibility studies, and research proposals all demand that same precision and neutrality. Strengthening source use, particularly synthesizing without quoting, was one of the hardest skills to develop. The literature review required me to paraphrase and connect multiple sources into one coherent argument, with no leaning on direct quotes as a crutch. The general audience essay pushed the opposite challenge: distilling dense technical content into something accessible without losing accuracy. Both exercises reflect real engineering communication demands, where the audience shifts constantly between specialists and stakeholders.
Finally, negotiating genre expectations across assignments tied everything together. Technical reports, lab write-ups, and public-facing documents all follow different conventions, and learning to shift between them deliberately is a skill I will use throughout my career. An engineering memo written for a client reads nothing like a methods section written for a journal, and now I understand why and how to navigate that difference. Engineering is often thought of as numbers and systems. This course reminded me that communicating those systems clearly is just as critical as designing them. That perspective is something I carry forward.
