Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

CanadianSchism writes "I've been in the public sector for the past 6 years. I started off doing my work study in web design and a bit of support, eventually going through the interview process to fill in a data processing technician post, and getting the job. The first four years of my work life were spent in various schools, fixing computers, implementing new hardware, rolling out updates/ghosting labs, troubleshooting basic network and printer problems, etc. I was eventually asked to work on the administrative information systems with an analyst, which I've been doing for the past 2 years. That's consisted of program support, installing updates to the pay/financial/purchasing/tax/energy systems, taking backups on SQL servers, etc. I've never had the opportunity to take time for myself, and jump back into my first love: programming. I've picked up Powershell books (have two here at the office), but haven't gotten anything down yet, as there are always other projects that come up and whittle my attention to learning a language down to zilch. This new year will see a change in that, however. I'll be setting aside an hour every day to devote to learning a new language, in the eventual hope that I can leave this company (take a sabbatical) and hop into the private sector for a few years. My question to you all is, what language should I start with, to learn and get back into the principles of programming, that will help me build a personal portfolio, but will also lend to learning other languages? At this point, I'm not sure if I'd like to make/maintain custom applications, or if back-end web programming would be more interesting, or any of the other niches out there."

You won't be dong it for a living anytime soon, but you could at least do something fun and personal. Try writing a game or app for Android. You can cover a lot of ground in an environment that is easy to use like that.

Please see this article [codinghorror.com]. Bad programmers actually create more work for the good programmers than they end up doing. If you want to be a programmer, fine. But it's not something I recommend you jump into with minimal training. There's almost no such thing as a "beginner" programmer job. Most good programmers have been programming for years (often a decade) at home or on their own before they start doing it for a living.

Right... but ideally a beginner programmer wouldn't be doing mid/sr. programmer work, it's more like add a textbox here & write this report here, not build this module or create this ETL process. Everybody's gotta start somewhere, but again I must stress, that approach isn't for most people.

Oh, and it's probably important to state your case beforehand somewhere between getting a job offer and getting hired that you're a true beginner, consider that the "beginner" leaving before you has probably learned their stuff and is moving on since nobody ever promotes inside IT, so that they don't expect you as a "beginner" programmer to fully dive in MVC or something. I've seen things more retarded in my career, and people either get canned or run out screaming.

Because someone coming in "6 years IT experience, no programming experience" is going to be an entry level programmer... He will either be put doing what he is most qualified for, or thrown in way over his head. Even if there was a "learn programming" job, it will be lightyears from his "seasoned admin" salary.

Gentlemen, I've actually trained a lady under me at a dif job and have a very good idea of how it works, I never assigned her super complicated crap I knew she'd struggle with, more like write a simple select and you can find your datafields in the following queries type stuff, or add this field to the corp app (I had to teach her MVP basics / resharper real quick for that one).

Let's be realistic though, it takes one dumbass mgr. or even sr. dev. to completely turn a beginner's job into a nightmare, esp

I'm not saying the senior developers are actually blowing up the database, but it does take them time and thought to write a half decent query. You can take a naive approach to the task and get something that works, but when you get a table that joins 3 others in that are anywhere between 3 million and 30 million rows you need to think your query through before you lock the entire damn database.

Entry level developers need to know this at the very least, and if you get someone in there that barely understan

The problem is that if you want a "beginner" developer to do the job right, you probably have to spend just as much of your own time explaining what needs to be changed, and verifying that the resulting changed worked correctly (often sending the change back, re-explaining what needed to be changed, and checking it over again), as it would take you to just do the change yourself in the first place. You can view working with beginners as an investment. But you have to be very careful that you are not pourin

The problem is that if you want a "beginner" developer to do the job right, you probably have to spend just as much of your own time explaining what needs to be changed, and verifying that the resulting changed worked correctly (often sending the change back, re-explaining what needed to be changed, and checking it over again), as it would take you to just do the change yourself in the first place.

Yes, to the beginner who stops the thought experiment right there it would seem like that it just cancels out,

Dear lord, no they are not. Yes Jr level positions are usually shadowed/mentored by some Sr level developers, but they expect you to have at least some experience. Now, obviously they don't expect you to necessarily have professional experience, otherwise no one would ever get into the field, but every software shop I have seen expects at least a few years of programming experience before they will even talk to you.

Most people don't start off their programming careers by writing games, eh nvm

What would you say most developers start out learning?

I have to admit that no matter what problem you're solving in programming, it can be as much of a rush as making a game, but I still think it's a good way to capture the imagination of a new programmer. It's good if your program is fun to test as well as to code. Even if it's just a basic text quiz type game, it's good to have such immediate feedback on what you're programming.

My first programming book was learning how to make games in Amos BASIC on my A

The courses I've seen start you off with flow charts to try and explain the flow and concept of stuff like boolean logic, variables, variable types, basic operators (+/-/*//), etc... moving into local applications, which I guess is the basis for a game. I remember though, when I took AP Java in HS, we wrote the fishes game in a command window towards the end of that course, and I think I spent most of college going "duh, that's how you do it" as a result of the challenge level of that class. So maybe ther

Well, I started off thinking 2D games, but then I was thinking for the absolute basics you could start off with very simple command line stuff, but you can even turn that into a game. For example a simple game where you are presented with 2 integers that the user has to add together and type in the answer. Then randomise the numbers. Put it in a loop. Then add in subtraction, multiplication and division. Keep track of how many answers the user got right or wrong. You could even add in a high score table and

You might want to look up the definition of niche, cause I don't think it means what you think it means.

I am pretty sure he is correct in using 'niche' as a way of describing a small segment of the programming market.

Languages such as Java, C/C++, C#, PHP, and Visual Basic are FAR FAR FAR more commonly used than Ruby or Python. Those two are niche languages by almost anyone's definition.

If the marketability of your skillsets is your primary concern, learning languages like PHP, Java, Javascript, or C# is clearly the best way to go. I sure wouldn't want a language like Ruby or Python to be the only one I am

I think that if a language is being used to power sites like Reddit, Quora, Pintrest, Instagram, Disqus, Mozilla, and various bits of Google, it's disingenuous to call it "niche" and suggest learning C.

I think that if a language is being used to power sites like Reddit, Quora, Pintrest, Instagram, Disqus, Mozilla, and various bits of Google, it's disingenuous to call it "niche" and suggest learning C.

He didn't say they were bad languages (although he did provide a small criticism of Python), he just said they were niche. Since when does calling something a niche product/market/industry imply that it is inferior? Lamborghinis are definetly part of a niche market, but I sure would trade in my current mainstream car for an exotic sportscar. That said, if I was going to choose to specialize in fixing either Lamborghinis or Fords, it would probably be an easy choice.

I'm not saying it's good or bad, I'm just saying he is grossly misinformed if he thinks Python is a niche language. It's used by huge sites and from what I've seen has replaced Java as the language most used to teach programming.

His whole point was that you'd be better off learning C (seriously, wtf?) and then C++ than Python, and I think that's just demonstrably not true across the board. Sure, there are still lots of areas where a language like C++ is superior, but for the vast majority of people lookin

While it may be a good language to teach first semester programmers how to program (since it is basically a scripting language), that doesn't mean it is a very marketable skill on its own. Learning Python as your primary scripting language is a great idea, but you better be very proficient in languages that are more commonly used.

I just got home from work and pulled up monster.com to see if Python actually was more commonly used than I thought. The results in the Chicago area when searching for Python was

Indeed, those results seem pretty conclusive. I yield in the face of my own apparent ignorance:)

The funny thing is, I actually do think Python is a great language for this submitter to learn. With his skills in IT, a good gateway job into a developer position could be working for a QA department. In fact most of the Python job postings I saw were for a QA departments. And at companys that really take QA seriously, there is little difference between QA and software development.

He should start learning either Java or C# IMHO, but Python would be a good start and put him into a QA position quickly.

You're wrong about Python, everybody's using it these days. It's probably more common than Perl now. I would say that most scripts that would have been written in Perl and many that would have been written in Bash are now being written in Python.

You're wrong about Python, everybody's using it these days. It's probably more common than Perl now. I would say that most scripts that would have been written in Perl and many that would have been written in Bash are now being written in Python.

Not so. Ruby continues to become more popular, and is already significantly ahead of JavaScript,.NET (except C#), LISP, etc. I don't see you can call anything in TIOBE's "A" list a "niche" product.

Ruby has moved down a notch in the list since 2007, but that's just because Objective-C suddenly jumped into the A list, near the top. Other languages like PHP and.NET (again, except for C# in particular) have gone down 2 or more notches during the same period.

TIOBE's A list just means it at least still has a sizeable niche. I never said Ruby or Python were dead languages. The kinds of languages that it considers B are Ada, MATLAB, and Assembly, among others. And if you rightfully ignore the A status and look at its actual rating of 1.7, you can see that even TIOBE regards Ruby as a niche language. I don't know how you can look at that rating and come to any other conclusion. But I think TIOBE's ratings are usually a bit odd (Javascript and C# being so low i

" But I think TIOBE's ratings are usually a bit odd (Javascript and C# being so low is astounding), so I wouldn't necessarily use this low rating to prove my point either."

Having been in the industry for many years, I do not find their placement of JavaScript or C# odd at all.

However, if you want to look at other sources, see that other poster's comment with all the links in it. Many of those sources rank Ruby higher than the TIOBE Index does.

Regardless, I disagree. Visual Basic.NET, for example, which is below Ruby in the list, is not a "niche" language either, since it can be used for creating general-purpose desktop apps or web pages or services, as the programmer d

Uhh... C# is more of a "niche" language than Python, and maybe even Ruby. Microsoft has all but killed C# on the desktop, which means its pretty much only useful as a server-side language, and is even more limited by the fact that you have to use a Windows server (unless you want to try running Mono).

C is a great language, but not nearly as friendly as Python. And Python doesn't have "whitespace issues" unless you're a moron or use a terrible editor. Lack of curly braces doesn't make a language immatu

That's because during much of the last decade, Java and C# were among the languages in high demand. Which establishes a code base, which then has to be upgraded and maintained. And as you probably know, there is generally more work overall in upgrading and maintenance than there is in writing novel code.

However, that is no indication whatever that very much new is being done with Java or C#. Something to keep in mind.

During that time, languages like Python and (in just the last 5 years or so, which is

Is it just my imagination, or are.asp sites blessedly becoming rarer? This [dmxready.com] site's spin on it is hilarious: "As mentioned above, programmers have moved away from Classic ASP and VBScript to other languages. However, that is not quite the same as dying". News for you! Oh yes it is. And do I even need to comment on the bad taste of trying to distribute this spin via pdf? Especially, DRM protected pdf? Say, this idiocy would not have anything to do with.asp dying would it?

I do it for free; usually for NPOs that can't afford programmers. Helps me to learn.

I don't particularly care whether or not it ever becomes "famous" (it won't because it addresses a very small, select audience). I just care whether or not it is the best quality I can do.

The nice thing, is that there is minimal pressure, which is good, as my "day job" gets first dibs on my time.

I don't watch TV. I don't hunt. I don't tweak cars, and I don't like to spend much time tending a server.

I just like to code. I also make sure that I don't write stuff that competes with my "day job." I like my company, and they could easily make my life miserable if I did. I also don't spend much of my "day job's" time on my personal stuff. I don't mind spending a bit of it, though, as they DEFINITELY benefit from my extracurricular work.

Good point, but I'd tell them anyway (I am very much a good company man). It would be their choice whether or not it was worth doing anything about it. If they made enough of an issue about it, I'd quit. I don't have a real problem with making a living.
I don't make a secret of my FOSS work, but I don't advertise it, either. Remember, I do this for free, for very altruistic organizations (not my church).
They would make themselves look like serious, serious crudmuffins, if they did, as they would be doing

The nature of my job doesn't allow me to do anything more than a quick check to see if the site is visible through a firewall. Since everything at work is monitored and controlled up the yin-yang, it's actually impossible to do more than that.

Let me break it into smal, easy-to-comprehend words:

I own the computer I do the work on (since I use Macs -that ain't cheap). I don't use the company kit for that.

Agreed. I've used a fair chunk of languages and you can learn from each of them (although sometimes what you learn is 'don't do things this way', I'm looking at your early versions of Visual Basic and all versions of brainfuck (i still prefer brainfuck to VB though). Python isn't perfect and it isn't for everyone (some people get real grumpy about meaningful white space), but if you haven't programmed before then it is a good place to start. If not python then something designed with teaching in mind, say P

Pick something you love, or an itch you're dying to scratch. If it's a passion you'll stick with it.

Then pick a language that fits the niche that you're working in. If you're gluing unix bits together that's one thing, if you're going to be pushing out a big web app, that's another, and if you're making meatspace things go "Bing" then that's a third.

As you said, an hour a day is a great way to get yourself to be serious about it.

How is Python "pedantic"? Because you can just dump out unreadable gibberish without bother to format your code in any sensible way? Because that seems to be the main complaint from those who dislike Python. This is also why I think it's a good language for beginners, better to have them learn right away how to use indentation and proper code formatting than have to deal with their unreadable code several years down the line (and boy have I seen some unreadable code by developers who, for some reason, never

My opinion here is you've developed skills in IT, but now you're looking to do a bit of a "paradigm shift" and go into Development. However, there's big money these days for Sysadmins who can code well, e.g. python, powershell, ruby, and use it it some type of framework like Puppet or CFEngine etc.

You can become a rockstar DevOps Sysadmin if you get this down

I'd suggest Ruby first, then Python...but of course, you'll want to make sure your Linux/unix sysadmin knowledge is top notch too. I'm self taught so I'm not very good at telling people how to learn it besides "eh figure it out", but I'm sure you are industrious enough:)

In conclusion: Stick with IT. Also add Programming. Collect $$ for being a DevOps specialist.

Become an IT consultant. You can get jobs at IT consulting companies at a junior to mid level, because that's how they make money -- paying junior guys little and then billing out at $125-$200 hour for them. Then, you will learn to get your skill level and job title up to that of "Systems Engineer", and then maybe "Senior Systems Engineer." During this time, you'll learn a lot more about tech, get out of just hardware/application support, and get exposed to lots of projects.

1. Get an FPGA devkit
2. Learn Verilog [fpga4fun.com]
3. Live on the bleeding edge between hardware and software. Dream of being a hardware guy that dreams of being a butterfly in the software world, and vice versa.
4.
5. Get chicks
6. Profit!

I was in a similar situation a few years ago. After working various IT positions for the past 15 years, it wasn't till about 4 years ago I decided to get involved with web development. I picked up a book from O'Reilly called "Head First in to PHP and MYSQL" which taught me an incredible amount of web fundamentals and seemed to have been geared towards people that already have a background in technology. Without meaning to give them a free plug, I really appreciate the "Head First" series of books that O'Reilly publishes. They are definitely fun and exciting. Not just for PHP and MySQL, but tons of other languages like Python, C#, Java, and more. I thought I was a lost cause when it comes to programming thanks to only having minor experience in HTML and QBASIC hehe. Needless to say, it definitely got me interested in programming again. Worked for me. Might work for you too.

Sounds simple but that's really all there is to it. Pick a language with a good support community and dive in. Python is a good choice because of it's versatility and support. Perl is still around and is a great scripting language. The important thing is pick something and stick to it. I've seen so many people with bookshelves full of programming books and they never got to the end of any of them. Professional dabblers. It's better to pick one or two languages and really know them well than to dabble in lots of them without any real expertise. Once you do that then picking up new languages will be easier because the core concepts will be familiar to you.

I used to work in the public sector so I'll share something with you. There is a stigma attached to being a public sector employee. I've been told this by more than one recruiter. It's a great training ground but at some point you have to make up your mind whether you want to stay there your whole career or venture into the private sector. The longer you stay the harder it will be to get out. Some recruiters will look at someone with 10-15 years of public sector experience and be reluctant to hire you for a private sector job. I met some smart people in public sector but I also met more than my share of lazy pricks. You sound like one of the former so just make the right choice for you. Good luck:-)

PHP. Classic procedural programming, object-oriented programming, & (as of PHP 5.3) functional programming...it's got it all. In addition, the syntax is very C-like, so making the transition to other popular languages such as C/C++, Java, C#, and Javascript isn't too difficult. Also, the documentation for PHP is very good (http://php.net/docs.php).

The current learning language for Computer Science is Java. It used to be Pascal. Switched to Java because of the importance of object oriented programming.

The language of choice for Linux/Unix system administration is Perl. Windows admins don't generally code though one of the dot-net's would likely be the choice if they did.

Pick one. Then buy a book and work through writing and running the example code. Then come up with an idea for a simple program you want to write. Then write it, referencing your books and Google search.

C# has the added benefit (for a Windows Admin) of being able to easily import and manipulate COM+ objects. Basically if it can be automated in Windows there's a COM+ API for it somewhere. Excel sheets, databases, you name it. Plus if you need.NET or actual Win32 API (*shudder*) you can hack that in too. Double plus added bonus: C# is syntactically similar to Java so if you need to go all platform independent on something a lot of the concepts will transfer nicely.

It's been my experiance that good programmers always have a project in the works. It's almost a disease. I can't go 2 weeks without writing something. So if you've gone 6 years without writing anything, I've got to wonder if it's really your thing.

That said, the next question is where to start. Pick something with high demand where it's relatively easy to get your foot in the door. The biggest problem you'll encounter is that everyone wants 5 years of experiance. If you can work programming into your current job, great. That's how I switch from systems administration to programming. I'd recommend learning C# and MVC. The tools are excellent and there's huge demand for it right now. The HTML and Javascript side of it will translate over to anything else you want to do.

Again, what he's saying is that if you really love it, you would be doing it instead of asking on Slashdot how to do it.

The other day my wife needed to turn an image into a PDF file. Not finding something that did it for free in the past, I wrote it myself. Another time I wrote a utility that split PDF files. And another time one that joined them together. With a little help, I got my wife setup to manage PDFs without paying a dime. All with stuff I wrote for fun when needed. (I really should merge th

Go through a recruiter and just go to the interview anyway. I have a BA in another field of study and not Comp Sci and nobody cares. I know high school dropouts that have no trouble getting work because they are awesome coders with great recommendations.

If you want to be a web developer, learn HTML, CSS, JavaScript, a web backend language, and SQL. If you want to do sysadmin type stuff, learn a scripting language or three (PowerScript, Python, Perl, UNIX shell scripts (ick!)). If you want to get into heavier programming, pick up languages used in the direction you want to head; that might be a scripting language or it might be a "real" programming language.

If you can, work your programming skills in to your current job. It's much easier to get a job progra

First of all, I feel like I'm wasting my time writing this because I have no idea what kind of learner you are.

Your type largely determines your approach to learning... anything, especially something more complicated like programming. I'm a kinesthetic & how I've picked up new computer concepts and programming languages either by jumping right into them (work related and situational mostly), or by reading a book and doing the examples. I'm dead serious, it's that simple (+/- motivation), read the chapter, put what you learned into a compiler, debug it (if you need to), play with it, try new methods, whatever... I picked up jquery & ajax mostly this way, the latter mostly through implementing on business systems, the former I read a "missing manual" series book on.

If you're feeling cocky, you can fake it till you make it, land a beginner programming job and get paid to learn it! I know it would work for me, but that's largely cause I'm a hands on learner (kinesthetic) and I learn by doing. If you're an auditory learner, you'd probably get chased out with fire with this kind of approach and would benefit more from online, or class lectures.

Note that they don't say that learning styles "don't exist", just that whether they exist or not, nobody has been able to demonstrably improve teaching or learning by conscious application of learning styles.

Good teaching is better for everybody, regardless of learning "style".

Second, look at the development technologies and tools that exist in that field and are used frequently and common. Games use C++ and assembly, ASICs use Verilog, pinniped databases are written in.NET.

Third, focus on learning the technologies that are used in your particular field of interest.

This will permit you to have a marketable skill in precisely the area of programming you want to accomplish.

I am aware that many programmers consider themselves "generalists" -- and heck, I do too. But the field of programming is now sufficiently wide that ALL programmers must, to an extent, specialize. Of course you can always apply your generalist knowledge to solving one-off problems. Instead, I suggest you focus on a particular area of expertise related to your dream job.

My question to you all is, what language should I start with, to learn and get back into the principles of programming, that will help me build a personal portfolio, but will also lend to learning other languages? At this point, I'm not sure if I'd like to make/maintain custom applications, or if back-end web programming would be more interesting, or any of the other niches out there."

Several languages are good and refreshing the basic principles of programming and as stepping-stones to learning other languages. If you need a list, just ask several high school or college CS department what languages they teach as 1st and 2nd languages.

You narrowed things down by saying you want to build a portfolio. What kinds of projects do you want in that portfolio? You don't seem to have decided yet.

Once you decide, that will be a major factor in choosing your language. You'll want to pick a lang

By and large, languages don't matter. It's the frameworks that do. Nobody* is looking for a ruby programmer - they're looking for a ruby on rails programmer. Nobody is looking for an Objective-C programmer - they're looking for iOS (and/or MacApps) programmers.

* yes, there probably are 3 ruby jobs, but you don't qualify and they are not near you/flexible enough/whatever.

I don't happen to like Java. I found python annoying when I last tried it (which was long ago). I think I'd like it more, now. php was meh. I really enjoy ruby and I liked Obj-C 15 years ago. Find out what you like to work with.

Check out the Seven Languages book. It's fun to take a few languages for a spin. If it's not fun for you, maybe you should stick with IT:-)

But you're really asking about finding a job.

By and large, jobs don't matter. Yes, you need/want to make enough to live comfortably, but it's amazing what you can be comfortable with. What really matters is what you work on, who you work with, and what you work with. Find a job in a field that interests you, working for/with folks that you get along with. Once you're there, fix the kinds of problems you enjoy fixing. Do some of the ones that need fixing, too. You do both software and IT - it should not be hard to find a great place to work and make it work for you.

1.) Something you won't get bored with.
2.) Something that's popular and not a niche language.

3.) Something that's platform independent.

I asked myself the same question several years ago. Because I was a hard care Unix admin at the time, I picked C# and DirectX development. I wanted something "easier" than my 50 hour a week job and different enough that I did not get sick of it. Also, I remembered Visual Basic from college and it was fun. I wrote about 40% of a pretty impressive game, all while teaching my

Seriously though, the cool thing about making a game, creative app or random "effects" is that you're totally free to experiment, while still learning a LOT, especially the higher you aim. Making a simple game or a starfield is easy, but there is just no ceiling to that stuff; while there are usually limits to how crazy you can get with "serious" apps etc.

My background included a significant amount of C and some assembly as well as a variety of other stuff including (not Visual) BASIC (workplace need, not my choice). I finally decided on JavaScript and probably also Node.js. I'm happy with the language itself and being useful in so many places and platforms and situations made it a no-brainer for me. I'd choose to use Linux everywhere, but being stuck with Windows also means that I can do a lot with WSH JScript, which is supported on everything from XP on (m

It's all well and good if you're learning but if you don't get to do it on the job then people might not think much of you practice as there is no one to vouch for you or verify your code is good. Put your stuff on Bitbucket or some other source sharing site or contribute to open source. At the very least you can then always point people to your repos when you're looking for a job.

We have a couple dozen computer user groups in our town. About a third focus on coding. Java, web-services, mobile computing, gaming are fairly hot topics these days. User groups are often in meetup.com. If you still have a computer print monthly in your town, they may list computer groups too. Some user groups are lecture oriented while others are show-and-tell their projects. Many of these project are more or less open-sourced on the github cloud code-base server. So you look for a project someone ha

Do you have a Bachelor's degree? I began working as a systems administrator before completing my Bachelor's degree. I have always done some amateur programming, but wanted to improve my skills to where I really was a "programmer". So I killed two birds with one stone and started taking one course a semester at a local college. I would go either at night, or on the weekend. Some semesters I took more than one course.

As I said, I already had written programs. I did not have the deeper understanding to write better, bigger and more complex programs though. The computer science program laid a foundation of calculus, statistics, and discrete mathematics. Then it went deeper into graph theory, and the theory of computation. Then we began learning C++. Then we learned more advanced C++, how algorithms and recursion and so forth worked. Then we learned Java. Then we learned about data structures, and the relationship between data structures and algorithms.

If you just want to learn a little Perl to write some simple scripts, you don't need to do all of this. It sounds like you want to have a deeper understanding of programming though. So this is necessary. I think it is best done at a college, although theoretically someone can learn much of this on their own.

I think the idea of learning programming by "I want to learn one language well" is an amateur mistake. Our learning initially was almost purely mathematical. If you read volume I of "The Art of Computer Programming", he doesn't get into (M)MIX programming until pretty far into the book, the beginning is math. The cursory learning of a programming language was just a byway to then teach us about recursion, backtracking and the like. We immediately moved onto Java instead of going deeper into C++, to see that there were different ways of doing programming by different languages. We later learned radically different languages using different paradigms like logical programming (Prolog), functional programming (Lisp) on top of the object-oriented programming (C++, Java) languages we had already learned.

Eric Raymond once said "Lisp is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days, even if you never actually use Lisp itself a lot." Other experienced programmers have agreed with this sentiment. As you said you're still an amateur, it's probably beyond your capacity right now to understand why someone should "waste time" learning a language like Scheme Lisp which they might end up never using. An ounce of prevention is worth a pound of cure though. The opinion of most expert programmers is that understanding the core ideas of computer science and programming is more important than domain expertise in a particular language. You say "I'll be setting aside an hour every day to devote to learning a new language, in the eventual hope that I can leave this company (take a sabbatical) and hop into the private sector for a few years." You should ask yourself if this is enough. Yes, knowing at least one commonly used programming language is important to get a job as a programmer. You will never really understand that language, and its limitations and advantages, until you learn some other languages, and some of the general concepts behind all programming and computer science. You said you were a novice programmer, and I think putting too much emphasis on learning one language well is an amateur mistake. There's a lot of steps you should be doing before deciding to become an expert in one language.

I'll give a personal example. I do a lot of Android (Java-like) programming. I also need a web API for some of the programs. A server-side Java solution is just too expensive for what I'm doing - sites like Bluehost and Dreamhost don't really support Tomcat and the like for $9 a month. So I use other languages for my web API than Java. Do a Google, or more importantly, a Craigslist job search for "full s

If you want something that will help you learn other languages, don't make the mistake I made. Don't learn Perl.If you learn Perl, you will rapidly lose all interest in other languages, because any time you try to pick one of them up, you'll be reading through the documentation and examples, and your brain will go, "All THAT just to accomplish THAT little thing? That's, like, eighty lines, and in Perl it would be, like, three lines. I'm gonna just go do it in Perl. Yep, see? Three lines, like I said.

After you've written enough Perl you feel like doing it any other way is an uphill battle. Nevertheless, once you grok/accept its peculiarities, Python is a pretty good replacement. You can even be as concise as with Perl after a while. Plus the young'uns like Python more than Perl because Perl's sigils freak them out and make them want to cry.

Just don't jump into projects involving involving the technologies (i.e. platforms and tools) of the now. The number of subjects you have to "learn" about are so fragmented it's an utter nightmare. You'll get lost, feel incompetent, and give up; I've seen it a hundred times. What you are going to do is reinforce and awaken your incommunicable knowledge of programming fundamentals; not in a formal, theoretical way, not with simple practice (though consistent routine is required to turn this into a habit agai

The dirty little secret of the programming world is that the vast majority of jobs aren't really all that different than what you're doing now. Sure a few folks work in C on the bare metal, and a few people do some really high level stuff for companies like Google or Microsoft, but the vast majority of people working as programmers are making LoB apps used by maybe a few hundred people accessing a dozen or so tables from either an existing LoB system or a custom database. For the most part these apps are ac

Even better, write stuff that's hard. Read stuff. Read really complicated stuff, and try to make it do other stuff. Nothing will teach you good programming practices like knowing why you follow them, and nothing will tell you why like seeing the hell that comes of not following them, which any large project is almost guaranteed to contain plenty of examples of. From misnamed or misused variable/functions, to multiple (and therefore slowly diverging) implementations of the same logic, to spending weeks reinventing something already solved in your programming language's standard library because they didn't like the order of arguments on a function, to bringing in a massive overcomplicated framework to solve a simple problem due to a too-strong avoidance of NIH (not that you shouldn't beware of NIH, you just shouldn't let it lead you into trying to pound a space shuttle into a square hole), you'll see it all.

Fix some bugs for a large FOSS project. Pick things that are just slightly over your head, and then pretend someone's breathing down your neck to get it done yesterday. Pick a project where you don't just get to commit changes, find something where your code is reviewed before it's accepted. You'll find a lot of honesty in people that aren't getting paid and don't give a shit about alienating you, and if you can handle a bruised ego you'll learn a lot.

One thing I wouldn't suggest doing is writing code for other people on your own, not right away. It's not that you shouldn't do that eventually, just don't do it when you care more about accomplishing your goal than you do about learning until you've got some good habits firmly established. Otherwise, your bad habits will just become reinforced, since they're usually easier especially when you're only looking at your own code, and to to be honest, you probably don't know the difference between a good habit and a bad habit until you've worked on a large project with a lot of people.

The best thing about working on FOSS projects is, you'll actually be able to demonstrate work to future employers. That goes a long way in an interview or on a resume.

The question was what language to learn. Before working on FOSS code, you should choose a language.

Java does a decent job at teaching the kinds of things you might need to know, and it's applicable to web, desktop, and mobile platforms. Lots of people knock it - I hate it, even though I did adopt a Java FOSS app.

I would recommend C# 4, which is good for servers as well as desktop, and with a bit of help from Mono can work on Linux. A serious Fortune 500 job is probably going to involve C#, and getting us

Rofl, a tape measure might've helped too, but everybody has their thing:)

But ya, I remember folks in college wanting to become programmers and just not being able to adapt their style of thinking to it. I'm curious as to what makes a programmer a programmer, book smarts have a lot to do with it, but there's plenty of people out there that have failed at coding and succeeded at something else. Critical thinking is a part of it too, but it's almost like you have to tailor your thoughts a certain way to

I thought the reason was that they are individual contractors, not employees, so that they are responsible not only for income taxes, but self-employment tax, their own health insurance, their own retirement and any other "benefits." But then, I could be wrong. I'd also question that above $100/hour figure, at least in the midwest portion of the US. $60/hour seems more like it (which is nothing to scoff at, but after withholding all of the things mentioned above, it isn't a lucrative as it sounds).

Actually, the hourly rate and what a contractor makes depends on a lot of factors. I've contracted a lot ( almost 10 gigs in my career ) as an LCC, Sub Chapter-S corp and as a W-2 Employee ) and basically:

1. You can setup a sub-chapter S corp and work for a company as another corporation.2. You can just do 1099 self-employeed as sole-propritor, LLC or partnership if you have others involved.3. You can work through a contracting company as their "employee" where they pull out the FICA, Social Security, etc and provide benefits at a cost to you and you get billed at X dollars an hour and get paid X - Y dollars an hour ( Y being the contracting companies cut ).

There are probably other options I don't know about.

So when someone says 100 bucks an hour, it doesn't mean much until you look at HOW they are earning 100 bucks an hour: W-2 or Independent as S-Corp, self-employed, etc , how they are filing their taxes, what expenses and other deductions they are taking, etc. In fact, I would say that at least in my experience I actually earned more of the rate as a sub-chapter S then any other way. Its just some extra work to keep track of all the expenses, run your own payroll, pay estimated taxes, file taxes and make sure you take all the deductions for the right expenses, etc.

Also rates depend very much on skills and demand. 100 dollars an hour is not that unrealistic. SAP and other ERP software packages and specialists can easily go over 100 an hour even being paid as a W-2 employee no matter where you are.

On the other hand, if a programming language or skill is "saturated" with a lot of programmers and the supply of talent exceeds the demand, rates drop like bricks. This seemed to happen with Java a few years back. I had some people calling me offering 30-40 bucks an hour for Java. I either ignored or laughed at most of them. Thankfully Java rates seem to be going up again, although I'm not doing much Java these days so I can't comment on what the going rates are for Java right now.

But the previous post was right. You have to "live" it. Even when I take time off between jobs, I spend some time reading technical books, checking out new languages, and writing code to keep my skills current. An hour a day probably isn't enough to learn a new language.