| Electronics > Beginners |
| what is the most relevant programming language for ee? |
| << < (5/21) > >> |
| emece67:
. |
| tggzzz:
--- Quote from: emece67 on November 04, 2018, 11:37:08 am ---Although, after a long career all we have used many different tools, the OP defines himself as a 2nd year EE student that has taught a little bit of C and is asking about "what to do now?". I think that overwhelming him with a huge list of, otherwise, valuable tools is not really useful. My advice, learn C. After C, learn any OO language (C++ or Java seem the wisest elections to me). Then... well, it depends on the way your career gets developed over the years. Maybe you turn on needing HDLs, or number-crunching, or easy scripting, or real-time, or regular expressions or... time will know. --- End quote --- Yes, but... * the OP needs to understand that EE is a large field and that no one language is sufficient. He will have to choose which to ignore, based on his (unstated) interests * he is at an age at which he can learn easily * many people stick with the first tool they learn, thus limiting the quality of what they produce and limiting career options * it is necessary to realise that you will need more than one tool, so get an appreciation of their advantages and disadvantages * knowing when to use/avoid a tool is a very good discussion point in job interviews |
| Karel:
C language is the most important language for EE's. Apart from that, it's the second most used language in the world. Only Java is more popular. Once you have mastered C, you will have a very good understanding of programming in general and you will have no problems to learn other langauges in case that's needed. Personally, I would never hire an embedded engineer who doesn't understand the concept of pointers to pointers. |
| IanMacdonald:
--- Quote from: Karel on November 04, 2018, 12:12:27 pm ---Personally, I would never hire an embedded engineer who doesn't understand the concept of pointers to pointers. --- End quote --- Personally, I would never hire a bench engineer who thought that wrapping tinfoil round fuses or splicing cables with tape were good ways to repair things. Something over half of all IT security issues are due to programming with pointers. (and forgetting the small issue of bounds checks) The cost of this practice in terms of downtime and stolen data outweighs by orders of magnitude any advantage. |
| Karel:
--- Quote from: IanMacdonald on November 04, 2018, 03:35:00 pm ---Something over half of all IT security issues are due to programming with pointers. (and forgetting the small issue of bounds checks) The cost of this practice in terms of downtime and stolen data outweighs by orders of magnitude any advantage. --- End quote --- You have to blame the programmers or their bosses who put tight deadlines and/or don't want to pay for an experienced C programmer. I have learned to always: - check all input - use Valgrind - use unittests I have seen many that skip those because of lack of time. |
| Navigation |
| Message Index |
| Next page |
| Previous page |