This post originally appeared on the Flatiron School Blog.
Deciding on a first programming language to learn can be overwhelming. Flatiron School hosted an online lecture to help students better understand a few of their options and decide what’s right for them. Here are a couple key takeaways. You can register for the next time the session is hosted or download the recording here!
He highlighted three reasons for this approach:
“I don’t get the value of knowing just one language,” Avi says. “I want the right tool for the job. If you only know one language, you’re pigeonholing yourself into using one approach for everything.”
Working as a developer, you will need to learn new languages (maybe even as early as your first day on the job). Learning more than one language—and starting to recognize patterns, abstractions, and commonalities between languages—at the beginning of your coding education better prepares you to continue learning new languages in the future.
Learning both languages opens up more immediate job options for your first job as a developer, and prepares you to keep on learning new languages and technologies as the job market and tech landscape evolve. “The most consistent thing in technology is that everything is going to change,” Avi states. “Eventually, you will need to know more than one language if you want to have an awesome career and build deep, meaningful things. So, why wait?”
Interested in a deeper exploration of the differences between the languages and how they complement each other? Mark your calendars for Thursday, July 21 at 1pm EST and RSVP for the next live lecture.