im going to have to agree. I'm dyslexic and am working on my Ph.D in Computer Science. Also, everyone in my house is using Linux now too since I refused to support Windows any longer. There hasn't been a single problem since.
Dyslexics Untie!
go to http://www.craigslist.org/ (select your city) I live in NY and find loads of part time gigs when I search the jobs for "part-time" or I search "gigs"
Good Luck
I think TIOBE is flawed. For real statistics I use indeed.com. It's the mother of all job sites, and it also does trending.
http://www.indeed.com/jobtrends?q=%22C%2B%2B%22%2C+%22C%23%22%2Cjava%2C+Perl%2CPython&l=
thats the view of the current job market.
Perhaps C/C++ is slipping in some areas, but it will not go away. I work on Wall Street, and fast trading systems are written in either Java or C/C++. There will always be a need for speedy software.
As for Perl/Python. Sure there are people using Python out there. I'm sure its a great language, but I haven't really found a reason to move off or Perl yet. Every systems engineer I know uses Perl. A while back some twit said that anything more then 100 lines of Perl becomes difficult to manage. This quote has gotten lots of publicity, but I don't agree with it. I've actually seen entire Quantitative Trading Systems written in Perl (thousands and thousands of lines of code) that were quite easy to maintain. The real issue with maintaining code is writing good code and commenting the code where it needs to be commented to begin with. Its really quite simple.
As for not having a new release of Perl.. I fail to see why so many people make an issue of it. It works.. really well as a matter of fact. I could see getting my underwear in a bunch if it didn't work well; but it does.
I look at the popularity of a development platform.
indeed.com is the greatest job search engine on earth. It polls data from loads of other job sites and compiles the information in one place.. that being said, it also offers tools that show trends in industry based on what jobs are posted and the key words associated with them.
I can determine which platforms are popular and which ones aren't. That information will also tell me which ones are more supported. The more jobs that are offered in a technology, the more people there are to support it. It's all market driven.
shows me that there are a tone of java positions out there, and very few delphi positions available. While Delphi may be great, you're going to have a difficult time finding someone to support it. It also tells me that Java is probably a better development language as a whole (*waits for flames from the delphi community*), because more people are using it. People tend to use good technologies.
I don't know what kind of code you write, but I think you're wrong. If a company is paying for software, they should be paying for the fastest most reliable code available. Where I live (in the NYC/tri-state area), a good number of employers are from the investment banking and insurance businesses. They expect algorithmically well written code, much of it will be multi-threaded and will handle millions of financial transactions daily that will occure in dozens of protocols (FIX, EDI, SWIFT, ebXML, ACORD, not to mention specific ones developed by 3rd party companies). Those transactions will be written using in-house written API's that every staff developer and consultant will have to learn. For enhancements or maintenance, Thousands (or hundreds of thousands) of lines of source code will have to be sifted through, the changes made and put into source control, compiled, tested in QA and then moved into production.
In this area, you need both a college degree and experience. The college degree in Computer Science shows that you've been exposed to algorithmic software development. Experience is required because they generally don't teach you things like error checking in college:
#include<cstdio> FILE *Fp=NULL;
College: Fp = fopen("somefile","r+")..
College + Experience: if(!(Fp = fopen("somefile","r+"))){
printf("that sucks\n");
exit(1); }
fclose(Fp);
Beyond just hashing out code, someone with experience knows the importance of documentation.
some of the data you find with google is incorrect and/or unsupported. A monkey could have written 1/2 the stuff you find out there. Valid research is published in books or scientific journals.
I went to uni part-time thus it took me quite a while to graduate. During the years that I attended classes, the CS curriculum changed a few times. The language of choice went from C to C++ and then to Java. In truth, the skills of the student population declined with each change. The more abstract the programming language the less the students seemed to understand what they were doing.
so, whats the difference?
if you ask an undergrad with a "java education": "whats involved in creating a socket"? the reply is simply "create a new socket object"
if you ask the undergrad with a "C education" the very same question, the answer will be "create a socket descriptor, bind to a port, listen to a port, accept a connection, signal handling, etc..."
which student do you suppose knows more?
This is absolutely not a slam at Java. I truly believe that Java allows you to produce fantastic results with less effort. My real complaint is that for students, writing software in java abstracts the underlying logic. This is what uni students should be learning
3/4 of the things that make code good vs. bad is error checking and commenting. If you check the return code of everything and account for all possible errors in your code, you will become a good coder. As far as spacing and comments go, if you make your code neat and very readable by inserting comments where they should be, other programmers that have to read your stuff will appreciate it.
Sure there are other things that have been mentioned in this thread and I agree with a lot of them, but being anal about your error checking is the best way to start writing good code.
Slashdot Mirror
im going to have to agree. I'm dyslexic and am working on my Ph.D in Computer Science. Also, everyone in my house is using Linux now too since I refused to support Windows any longer. There hasn't been a single problem since. Dyslexics Untie!
go to http://www.craigslist.org/ (select your city) I live in NY and find loads of part time gigs when I search the jobs for "part-time" or I search "gigs" Good Luck
I think TIOBE is flawed. For real statistics I use indeed.com. It's the mother of all job sites, and it also does trending. http://www.indeed.com/jobtrends?q=%22C%2B%2B%22%2C+%22C%23%22%2Cjava%2C+Perl%2CPython&l= thats the view of the current job market. Perhaps C/C++ is slipping in some areas, but it will not go away. I work on Wall Street, and fast trading systems are written in either Java or C/C++. There will always be a need for speedy software. As for Perl/Python. Sure there are people using Python out there. I'm sure its a great language, but I haven't really found a reason to move off or Perl yet. Every systems engineer I know uses Perl. A while back some twit said that anything more then 100 lines of Perl becomes difficult to manage. This quote has gotten lots of publicity, but I don't agree with it. I've actually seen entire Quantitative Trading Systems written in Perl (thousands and thousands of lines of code) that were quite easy to maintain. The real issue with maintaining code is writing good code and commenting the code where it needs to be commented to begin with. Its really quite simple. As for not having a new release of Perl .. I fail to see why so many people make an issue of it. It works .. really well as a matter of fact. I could see getting my underwear in a bunch if it didn't work well; but it does.
I look at the popularity of a development platform.
.. that being said, it also offers tools that show trends in industry based on what jobs are posted and the key words associated with them.
indeed.com is the greatest job search engine on earth. It polls data from loads of other job sites and compiles the information in one place
So, if I look at some trending data like this:
http://www.indeed.com/jobtrends?q=jsp%2C+cgi%2C+asp%2C+php&l=
I can determine which platforms are popular and which ones aren't. That information will also tell me which ones are more supported. The more jobs that are offered in a technology, the more people there are to support it. It's all market driven.
For Instance
http://www.indeed.com/jobtrends?q=java%2Cdelphi%2C+perl&l=
shows me that there are a tone of java positions out there, and very few delphi positions available. While Delphi may be great, you're going to have a difficult time finding someone to support it. It also tells me that Java is probably a better development language as a whole (*waits for flames from the delphi community*), because more people are using it. People tend to use good technologies.
I don't know what kind of code you write, but I think you're wrong. If a company is paying for software, they should be paying for the fastest most reliable code available. Where I live (in the NYC/tri-state area), a good number of employers are from the investment banking and insurance businesses. They expect algorithmically well written code, much of it will be multi-threaded and will handle millions of financial transactions daily that will occure in dozens of protocols (FIX, EDI, SWIFT, ebXML, ACORD, not to mention specific ones developed by 3rd party companies). Those transactions will be written using in-house written API's that every staff developer and consultant will have to learn. For enhancements or maintenance, Thousands (or hundreds of thousands) of lines of source code will have to be sifted through, the changes made and put into source control, compiled, tested in QA and then moved into production.
..
In this area, you need both a college degree and experience. The college degree in Computer Science shows that you've been exposed to algorithmic software development. Experience is required because they generally don't teach you things like error checking in college:
#include<cstdio>
FILE *Fp=NULL;
College:
Fp = fopen("somefile","r+")
College + Experience:
if(!(Fp = fopen("somefile","r+"))){
printf("that sucks\n");
exit(1);
}
fclose(Fp);
Beyond just hashing out code, someone with experience knows the importance of documentation.
http://sdf.lonestar.org/index.cgi
One of the oldest and most respected Public Access UNIX Systems.
some of the data you find with google is incorrect and /or unsupported. A monkey could have written 1/2 the stuff you find out there. Valid research is published in books or scientific journals.
I went to uni part-time thus it took me quite a while to graduate. During the years that I attended classes, the CS curriculum changed a few times. The language of choice went from C to C++ and then to Java. In truth, the skills of the student population declined with each change. The more abstract the programming language the less the students seemed to understand what they were doing. so, whats the difference? if you ask an undergrad with a "java education": "whats involved in creating a socket"? the reply is simply "create a new socket object" if you ask the undergrad with a "C education" the very same question, the answer will be "create a socket descriptor, bind to a port, listen to a port, accept a connection, signal handling, etc..." which student do you suppose knows more? This is absolutely not a slam at Java. I truly believe that Java allows you to produce fantastic results with less effort. My real complaint is that for students, writing software in java abstracts the underlying logic. This is what uni students should be learning
3/4 of the things that make code good vs. bad is error checking and commenting. If you check the return code of everything and account for all possible errors in your code, you will become a good coder. As far as spacing and comments go, if you make your code neat and very readable by inserting comments where they should be, other programmers that have to read your stuff will appreciate it. Sure there are other things that have been mentioned in this thread and I agree with a lot of them, but being anal about your error checking is the best way to start writing good code.
http://www.google.com/codesearch apparently google has already done it.