Welcome to Oops2Ops: Coding Stories!

First, thank you for taking the time to look into what the heck this new newsletter I'm starting is. I appreciate that and hope you will be interested in following this newsletter by the time you finish reading what it's going to be about.

Now, let's talk about what I intend on writing in this weekly newsletter. Every Friday at 4:00 PM EST/EDT, I will be publishing an article containing stories about my personal experiences in computer science, especially focusing on the lessons I've learned from my mistakes and general advice I have for people interested in joining the field. I wanted to do something different this year, and I was inspired to do this when a friend of mine came to me asking for advice—they're considering majoring in computer science and are starting to explore the domain—which made me think about the plethora of lessons I've already learned (many the hard way) in this field and the many more I will learn once I start my professional career.

Finally, allow me to give a brief preview of the next few weeks. Next Friday, January 12th, I will be releasing a list going over some of the best lessons I've learned so far. In the weeks following, I will go into further detail on some of them while sharing relevant resources and stories. I hope you will join me on this journey, especially if you're someone looking to join the field of computer science and would like some advice/guidance.

Disclosures

AI Disclosure: I created the title for this newsletter and its description with some help from ChatGPT. Aside from that, I intend for this newsletter to be completely authentic and written by me. I may, from time to time, use AI tools for editing and reviewing purposes, but not for writing purposes.

Expertise Disclosure: I have be programming since 2016, and I will be receiving my Bachelor's of Science in Computer Science in May 2024. As of writing this, I have not had a job in the field, but I am actively searching for one. As such, I speak primarily as a learner and student, not as a professional (yet).

Feedback Disclosure: I always welcome feedback and constructive criticism. If there's ever a specific topic you'd like to see my take on, some changes you think should be made to an article, or something else, then you can send me an email at [email protected] (I'll be sure to shout you out in the relevant article if I include your feedback).