Oiza B.’s Post

View profile for Oiza B., graphic

Frontend Engineer @ GitLab

I'd like to share some thoughts on the use of the word "easy" when referring to computer science courses at U Penn or any other college or institution. First, it's important to recognize that computer science and software development are not the exact same thing, despite overlap. Many experienced software engineers would agree that success in a computer science program does not guarantee success as a software engineer, and vice versa. Indeed, it's even possible to initially struggle in both school and work before finding a niche within software engineering that truly resonates. The software industry offers a diverse range of pathways and specializations. By labeling certain CS courses or milestones as "easy," we unintentionally discourage those who face challenges, leading them to believe they're not suited for the field. This mindset can be detrimental for two main reasons: 1) People might be well-suited for another area within software engineering that they've yet to explore, and in fact might not be able to until they start working. 2) Filtering out individuals with self-doubt and humility at the beginning of their careers will deprive the industry of potentially valuable and thoughtful talent. Personally, I'd rather be mentored by someone who struggled than someone who found their early foray into CS an absolute breeze. So, let's be mindful of our language and strive for inclusivity. Rather than insisting that certain courses or aspects of the field are simple or straightforward let's try to foster an environment where people aren't unintentionally influenced to self-select out before they've even begun to really explore tech.

To view or add a comment, sign in

Explore topics