Electronics > Beginners
what is the most relevant programming language for ee?
<< < (11/21) > >>
spec:

--- Quote from: Nusa on November 04, 2018, 05:27:25 pm ---In a technical field, unless you've found and gotten stuck in a particular niche, you continue learning for your entire career. One of the most important lessons you get from your formal education is learning how to teach yourself, if you didn't know already.

--- End quote ---

So true: learning how to learn. That is the key to success.  :-+

The pro programmers I have known seemed to be able to use most languages.

On one big project the core language was Ada, but there were chunks of assembler, Fortran, Basic and C.
Karel:

--- Quote from: Crazy_Pete on November 05, 2018, 05:06:46 am ---I would like to really underline that C is obsolete and if you have no experience in programming you should forget C (it will only teach you bad thoughts) and go right ahead to learning C++.

--- End quote ---

Now I understand  your nickname. C is far from obsolete and is here to stay for a long time, whether you like it or not.
And C++ is a terrible language...
HB9EVI:
just to mention: even though the arduino language uses a c++ like syntax, it is in fact no c++, although it uses the gcc toolchain, there is no libstdc++ for the avr platform but only the avr-libc.

So far i guess c and asm are the most used languages in the EE environment - so far that, what I used; for bigger embedded platforms python is coming into business.
bd139:
@Karel: I couldn’t agree more.

If anything more people need to learn C.

For me, on the desktop, you write in python and fix the slow bits using C extensions.

On embedded stuff, C first every time.

No C++, no java. There is no place for abstraction that deep in that space. Even the bastardised C++ on Arduino stuff is vile.

There is some room for some imperative stuff like FORTH however.
Rerouter:
C / C++ for the micros, and probably python for UI to those devices

It mainly comes down to your use case, but my approach is bash out the functionality in "Bodge code" the ugly inefficient stuff that you know will work, e.g. going as far as bit banging a protocol, then setup the test cases and begin cleaning it up as time allows, you already know it works, you can demo it or release a version early if push comes to shove. but it keeps dev time short.

Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod