Hi all. I'm currently at university studying computer science and I've been learning c/c++ for about two years now. Only I'm going to start looking to look for some programming jobs in the next year or so. But the problem I'm having is thinking that the programming industry expects you to know everything about the language and also the system in which ure programming on etc linux/windows.
For instance lets say your trying to write a multi threaded ftp/ssh server/client and you forgot how to implement threads in linux, would it be acceptable to go and re-study the basics and come back to the program, or would the industry expect you to spit out a solution within a matter of minutes?
It's just summat i'm trying to get around, as i'm trying to write some apps for my mobile device only there's alot to learn and sometimes i'm having to go back a learn some of the basic API's for my mobile platform. Only i'm thinking would i have to know everything from the back of my hand or what.
Thanks people and fellow programmers.
Would this be acceptable in the programming industry?
Started by phil128, May 20 2010 04:37 AM
4 replies to this topic
#1
Posted 20 May 2010 - 04:37 AM
|
|
|
#2
Posted 20 May 2010 - 05:17 AM
Industry expects that you can create code. So, you have to understand paradigms and algorithms and know language syntax, basic APIs, to be productive and efficient. You should also learn fast and know how to find things on Integernet / documentation.
#3
Posted 20 May 2010 - 06:31 AM
When developing, I always have some sort of relevant reference open, even for interfaces I am very familiar with.
However, in the example you gave, with the multi-threaded file transfer application, reviewing the process of threading applications would be done during the design of the application as you would first need to know if threading is applicable to your application, what type of thread should be used in this particular implementation, and calculating the benefits to applying threads.
As an anecdote, any software project that doesn't do the above before having a single line of code developed is "doing it wrong".
However, in the example you gave, with the multi-threaded file transfer application, reviewing the process of threading applications would be done during the design of the application as you would first need to know if threading is applicable to your application, what type of thread should be used in this particular implementation, and calculating the benefits to applying threads.
As an anecdote, any software project that doesn't do the above before having a single line of code developed is "doing it wrong".
#4
Posted 20 May 2010 - 10:53 AM
No program who does anything non-trivial knows everything. I'm looking things up almost daily.
#5
Posted 22 May 2010 - 03:47 PM
If you don't know everything about the language of which your programming or the system that your coding for then I would recommended something like joining a team of people coding a program. That way those that your working with could help fill the gaps in your knowledge and vise versa. I'm not a professional programmer by any means, but I do know two is better than one.
I hope I was able to point you in the right direction ^^
I hope I was able to point you in the right direction ^^
My Personal Blog l Learning C++ l I'll be famous soon enough.


Sign In
Create Account

Back to top









