Draft to Drift:
How Writing for Engineering Took Me Further Than I Thought
When I first began my class of Writing for Engineering, I thought it would be another writing class where we focused on grammar and maybe wrote a couple of essays. But this course didn’t just prove me wrong; it also taught me how to write better. It taught me how to think like an engineer, plan like a project manager, and present like a professional. From group work to solo reports, from elevator speeches to full-on project proposals, I had to apply real-world soft skills. And along the way, I started to take writing a little more seriously, even if I still prefer math and code.
The intro paragraph is my first assignment from this class, so it contains more vulnerability. My intro paragraph gave me a chance to show a little of who I am: a student from Bangladesh, a gym-goer, a tech fan, and yeah, a chocolate lover. It was one of the first things I posted on the discussion board, and even though it was short, it made me realize that the audience matters. Whether you’re talking to a friend, a class, or a future employer, how you introduce yourself shapes everything that follows.
The resume and cover letter assignment felt super useful to me. It was the first time I built a resume that I would actually use for internships. I learned that keywords and formatting really matter, and also that you’re not supposed to include your age, religion, or how much you can bench press (unless you’re applying for a powerlifting job). Writing the professional summary and tailoring the cover letter to the job posting taught me how I should match the audience and purpose. I also got used to drafting and revising, which I usually avoid, but it made a big difference.
Lab Report One was kind of fun. We all did a dice-rolling experiment. I used JavaScript and charted the results in Excel. I had to write an abstract, format results with figure captions, and follow a clear layout. I also practiced APA citations for the first time. Even small things like using “two” instead of “2” in the wrong place made me pay attention to detail. The lab taught me how to combine technology, data, and writing into something meaningful.
Group Proposal (Beaver’s Den) was one of the most exciting parts of the class. I worked with Arham and Safwan; we called ourselves the “Triangle of Vision.” Our project was a student center proposal called Beaver’s Den, and we went all out to get the student prospective via surveying what they expect from their new student center. From this survey, we discovered that CCNY is not only a commuter college but also has a big dorm. Unfortunately, the dorm people don’t know we already have a student center, and very few even visit that one. We designed floor plans, included a Gantt chart, broke down costs, and even planned to add Tesla Superchargers in the underground parking. To support our argument, we included studies like Miller and Croft (2022), which showed that students who used campus recreation centers were more likely to stay enrolled. We also cited Mixson-Brookshire et al. (2023) to show that student centers boost social connection and retention rates. These sources helped us strengthen our proposal and made our writing more research-driven. I worked on sections like the tech tools, budget planning, and also helped present. It was a crash course in collaboration, visual design, and staying organized. We applied pathos, ethos, and logos to make a case that CCNY needs a real student hub. Honestly, this project made me feel like I was actually doing something real, not just a class project.
For this Technical Description, I broke down a complex topic, which was MRI, and explained it in simple terms. I used headings, figures, and citations, and I made sure it would make sense even to someone outside of STEM. I learned that writing for an audience doesn’t always mean “dumbing it down”; it means making it clear and easy to understand.
Besides the big projects, my friends and I took part in an extra credit trip to the American Museum of Natural History. I wrote about the visit, from getting lost near the deer exhibit to standing under the giant glowing sun in the Rose Center. That writing reminded me how important it is to capture a moment with honesty and detail. I didn’t expect to enjoy writing it as much as I did, but that assignment showed me how storytelling, voice, and reflection can make a simple field trip feel like an entire journey.
In conclusion, this class helped me realize that writing is part of engineering, not separate from it. Whether it’s a proposal, a lab report, or even a quick email to a supervisor, the way you present information matters. I also learned that writing doesn’t have to be boring; it can be clear, structured, and still sound like your own voice. I may not have made three new friends like Mr. Bubrow hoped, but with two solid teammates and a strong project under my belt, I would say I came close. This course didn’t just teach me to write. It taught me to communicate, collaborate, and build something that I’m proud of.

