- Forum
- General C++ Programming
- languages?
languages?
I have a question for some of the experienced/expert programmers on this site. If you have 2,000+ posts, I'm asking you a question. "How many languages are you fluent in?" I've been programming for about a year. I've taken 1 class in C and 2 classes in C++. I'm not working in the programming industry yet, but I'm trying to see what people in the indrustry are doing and what they know. thanks for your time.
If you intend to focus on programming in your whole entire working life, you must learn the art of learning programming languages. 13 years ago I graduated, join the working world and started to do programming until now. I have been using quite a few programming languages along the way. Each new job or new task will require me to use different programming languages to solve the problem.
For some ppl, programming is only during the first few years. After which they move on to Systems Analysis,DBA,Project Mgmt etc etc. That is why, graduate programmers positions are always available as few senior programmers want to do programming their whole working life. They feel programming is junior staff work and they should be doing higher level stuff. Also most new graduates are trained in the latest technologies and programming languages which the senior programmers may not have learn them yet.
I, however prefer to do programming in my whole entire working life provided my employer pay me well enough. If my employer feel programming does not worth that monies, then you can bet I am off to search for another employer who values my programming skills.
Sometimes it is very hard to convince the interviewers you intend to do programming your whole life. To them they feel programming are junior stuff. If you are senior you should do more IT non-programming tasks indeed. You can also bet such companies I would not want to join either.
For some ppl, programming is only during the first few years. After which they move on to Systems Analysis,DBA,Project Mgmt etc etc. That is why, graduate programmers positions are always available as few senior programmers want to do programming their whole working life. They feel programming is junior staff work and they should be doing higher level stuff. Also most new graduates are trained in the latest technologies and programming languages which the senior programmers may not have learn them yet.
I, however prefer to do programming in my whole entire working life provided my employer pay me well enough. If my employer feel programming does not worth that monies, then you can bet I am off to search for another employer who values my programming skills.
Sometimes it is very hard to convince the interviewers you intend to do programming your whole life. To them they feel programming are junior stuff. If you are senior you should do more IT non-programming tasks indeed. You can also bet such companies I would not want to join either.
Learning programming languages is rather... easy. It takes a while to actually master them, but once you are familiar with a particular paradigm (like imperative programming) you could work with any language that supports that paradigm within maybe like 1 or 2 weeks at most.
Other skills, like being able to come up with good solutions to particular problems at a conceptual level and especially soft skills like team interaction are more important for a succesful career. And of course it depends on where you actually live - for example over here where I am, if someone is just a programmer he would have problems finding a job, and could pretty much forget about finding a well paid one - whereas someone with applicable competences in theoretical informatics would easily find work here and elsewhere. That of course does not mean that the person in question would never have to program anything - it's just not the key competence that employers look for.
Other skills, like being able to come up with good solutions to particular problems at a conceptual level and especially soft skills like team interaction are more important for a succesful career. And of course it depends on where you actually live - for example over here where I am, if someone is just a programmer he would have problems finding a job, and could pretty much forget about finding a well paid one - whereas someone with applicable competences in theoretical informatics would easily find work here and elsewhere. That of course does not mean that the person in question would never have to program anything - it's just not the key competence that employers look for.
Topic archived. No new replies allowed.