3 answers
Updated
1920 views
Should I learn multiple programming languages for biomedical engineering?
I'm intrested in creating technology that can help progress the medical field. #programming #technology #biomedical-engineering
Login to comment
3 answers
Steve Lewis
Assistant Vice President, Cybersecurity Team Lead & Technical Product Owner | Technical Lead | Public Speaker
83
Answers
Haddonfield, New Jersey
Updated
Steve’s Answer
If you want to enter technology, then you can't go wrong knowing now to program. You can start with Java, JavaScript, C#, Swift, etc. Pluralsight and codeschool are great places to start.
Updated
Stephanie’s Answer
I believe you should learn multiple programming languages as a biomed engineering major. I would suggest you examine some job boards to see specifically which languages are relevant today and will be relevant tomorrow so that you don't take courses that are outdated in the workplace.
Updated
William’s Answer
I think that a firm understanding of the concepts goes very far, rather than trying to zero in on a specific "hot-for-now" language. Understanding basic constructs like "if/else", "loops", "arrays", or "structures" typically translates in some fashion between languages.
As mentioned in the other posts, it's really hard to say which languages would be the most relevant, depending on when this response is being read. I could make well reasoned arguments for Perl, Python, and a whole host of scripting languages if your direction shifts towards dev-ops. My basic premise remains though, that knowing the concepts translates.
I would suggest writing some code by hand however before getting too deep into a development tool or IDE. You will get a better feel of what the code does, and you'll only be trying to learn the language, as opposed to trying to learn both the language and the IDE tool. The IDE only makes things easier once you get the gist of the language basics.
As mentioned in the other posts, it's really hard to say which languages would be the most relevant, depending on when this response is being read. I could make well reasoned arguments for Perl, Python, and a whole host of scripting languages if your direction shifts towards dev-ops. My basic premise remains though, that knowing the concepts translates.
I would suggest writing some code by hand however before getting too deep into a development tool or IDE. You will get a better feel of what the code does, and you'll only be trying to learn the language, as opposed to trying to learn both the language and the IDE tool. The IDE only makes things easier once you get the gist of the language basics.