Students will be able to produce writing that demonstrates their ability to navigate choices and constraints in a variety of public and/or academic research genres that matter to specific communities.
This outcome helped me understand how different types of research writing work. I learned how to adjust my writing depending on the audience, whether it's for a school paper or something more public, and how to follow the rules for each type.
For the C.R.A.A.P. Test assignment, I had to identify the constraints of writing in a critical evaluation genre intended for an academic audience, specifically within the context of ENC 1102. The purpose was not to argue a point, but rather to assess sources objectively using set criteria: Currency, Relevance, Authority, Accuracy, and Purpose. I learned how genres come with their own expectations, such as structure, tone, and formatting, and how understanding these constraints helps tailor my work to a specific academic community. To meet the assignment's requirements, I made deliberate choices like using third-person analysis, focusing on measurable criteria, and avoiding personal opinion unless explicitly allowed. These decisions were shaped by the intended audience (my professor and peers) and the purpose (evaluating source credibility). From this, I learned how to adapt my writing to different genres and rhetorical situations by observing conventions and using them effectively. The assignment definitely exceeded my expectations of ENC 1102 by pushing me to think about how genre influences research and presentation. In the future, I'll apply this genre awareness when writing in different disciplines or professional settings, knowing how to shape my content and tone for maximum relevance and clarity.
The "Cache Simulator Report" aligns well with the Research Genre Production learning outcome, as it required navigating multiple writing constraints tied to genre, audience, and purpose. Because this was a technical report written for a computer architecture course, the genre called for formal academic language, structured sections, detailed analysis, and the integration of code-based and simulation results. Our team had to make decisions about how to present complex performance data in a digestible way for readers familiar with computer systems, such as using graphs, system architecture diagrams, and metric explanations to support our claims.
From this experience, I learned how to communicate findings in a way that was both technical and accessible, which is essential in STEM fields. I also learned that writing for a technical audience means making choices about precision, clarity, and what background information is assumed. To meet genre expectations, we included sections like Implementation, Evaluation, and Summary, mirroring what's common in industry white papers or academic reports. This assignment exceeded my expectations for ENC 1102 in terms of how much crossover it had with my major. It helped me realize that research-based writing isn't just for English classes, it's a key skill in engineering too. I'll definitely use this in the future when writing technical documentation or research-based project reports in both academic and professional settings.