You better ask yourself, is it too soon for this game?

The most powerful engine which can give you the best start is your motivation.

The most important thing is that now you already know what do you want to do with your career. Basically, after school, it is too soon to know what we want. It takes time and life experience to find out what you are good at. And what kind of activities makes you satisfied.

I had this kind of experience very soon in my life. I was 7–8 years old when I started to learn to play on a musical instrument similar to the guitar. It is called “Тамбура” in Bulgaria. But I started without the confidence that I want this. I had to learn the basics in 5 years. And I had friends that started later than me and learned that for 1 year. But they had the motivations, and they enjoyed that. So again, the keyword for your everything you do is the motivation.

My first job after school was in the glass manufacturing industry. I realized that this job is not for me. I did feel it deep in my heart. Remember that every new beginning is difficult. But there always an internal voice in you which says “Try again, try again, don’t give up!”. So if you don’t hear this voice, you should quit.

Three months later, I started on a telecommunication company. I was a customer service support, and that was very difficult for me. But this time I did feel this internal voice which said to me, “You are in the right place, keep trying!”. I was there on a test period, and they did not hired me. But I did visit the office to help and learn new things without asking for a salary. And three months later, guess what? They did call me and send me an offer.

I was 20 years old, and that was a good start for me. And I have never thought that I will be working in a telecommunication company as customer service support. But life always takes you to the right place if you are patient enough. Three months later, they send me an offer for a PHP Developer. I was interested in the billing system software of the company, and the management had seen that. And that is important. To find something interesting to you.

I used my computer only for gaming. Any of my friends had more knowledge and IT skills than me, but they did not have the motivation I had. So I had zero IT knowledge and skills. I first thought that it is impossible to go in that direction, but I was wrong. Everything is possible when you want it. Well, I wanted it, and the results had come soon.

When I was 24 years old (just like your age now), I decided to start to learn Informatics. Did I think it is too late? Yes, I did! But then I did realize that every try you give to change something, opens new doors for you. And you can look at this situation just like that. Every step you take will open new doors for you. I even know people who start at 30 and even 40!

Even I started to learn something new for me two years ago. I am 33 years old now, and I am a PHP Drupal Team Manager in a leading digital agency company.

I have never shared my experience with such a large audience, but do you remember? It is never too late to try something new!

I'm 32 years old and just got my first full-time job as a software engineer. After spending most of my twenties partying and traveling, living a gloriously unproductive bohemian life, I had gone back to school to finish my undergraduate degree in classical languages (i.e., Latin and Ancient Greek).

Right around the end of fall semester of my last year in college (age 29), I panicked. I realized that even if I went to a top-5 grad school in my field, I had very little chance of getting a job. But a fortuitous thing happened.

I had bought a Toshiba NB-255, a $300, 11" netbook, and I was frustrated with how slow Windows was running. I was back home for Thanksgiving, and my sister suggested I check out Ubuntu. She told me she'd installed it on an old laptop and it ran great. So I gave it a try.

Once I had Ubuntu installed, I did some Googling for a basic Linux tutorial (since I knew nothing about Linux) and found one that including a brief tutorial on writing Perl scripts and Bash scripts.

I'll never forget that first Perl script. It was like smoking crack for the first time.

I began scouring the Internet for anything and everything about programming I could find. I quickly found Harvard's CS50 course. I watched the lectures and did the assignments. I was well and thoroughly hooked. I moved back to North Carolina to be close to my family and started on a post-bacc Computer Programming certificate at NC State. This led to a part-time programming gig, and now, three years later, I've finished the certificate and the part-time programming gig has turned into a full-time position as a software engineer.

Understand that you don't have to be motivated by a desire to get rich or conquer the world. I just wanted a job that I was passionate about and that paid reasonably well.

So, take heart. At 24, you're a spring chicken!

I started two years ago, when I was 25. I went to course for beginners among many 17 and 18 year old guys, real computer nerds, and I was beating them in terms of learning. One year and a half later I had a job as a web developer at a very respectable company in my town. Now I am developing entire systems myself, including front-end development.

There is a myth about programming, which is the same myth about mathematics. This myth says that you've got to give up all your life for it, and that it is hard. It is not hard, is just another language. You've got to get used to it, and once you do, any idiot can program. Well, idiots might build buggy monsters, but they can still program. You'll have to drop this genius-programmer stereotype: I've met much more intelligent people while studying social sciences than when I was studying or working with programmers. They are normal people!

Now, you have to like it, and it has to be fun. Otherwise you won't practice, and if you don't practice, you don't learn. It is all about repetition. That's why crafts like music and programming are usually learned when you are very young. They demand repetition, and repetition demands passion. And once you cross the 20's barrier, you start, step by step, to give up your passions for money, position, social validation and so forth. The programmers I met that started when they were 15 can't learn anything else, at least it seems so. They are so worried about their careers that the only thing they can study is IT-related stuff, and usually those boring and somewhat useless development paradigms, as well as little pieces like libraries and development patterns. They can't even learn another language, and not because they are not capable of, but because they don't listen to themselves, only to their careers.

See if you like it, and if you do, enjoy fully, like a 15-year-old discovering a new video game. There is a secret about social rules like that one: they are all BS - belief systems.

Work harder, work smarter. There is a lot to learn, but if you are good, then it's still easy to get up to speed and moving. The tail end of the learning process is long and time consuming, but you'll be functional from scratch (and easily better than most other engineers who don't put effort into learning things properly) within a few months to a year.

Consider the controversial Jeopardy contestant's learning strategy: figure out all the fundamentals and basics and learn those, yes, but learn the more commonly used, relevant, and high impact things first. Pick the "right" (ie, widely used) languages to start with (Java, Swift, Python, Javascript..), then learn others to have a different point of view (Haskell, OCaml..).

Remember that the basics you learn at first are just that: the basics. With that in mind, always pay attention to what's currently relevant, what is actually used in the real world, and what is actually a good (right way) to do things. Use this knowledge (freely available if you search online) to order properly how you learn things.

It's very important that you immerse yourself in the process of learning (not just peck at it for 5 minutes here or there) and that you actively try to develop programs and rethink your approach as you go.

There will be a lot of talk about what's important in software development (maintainability and readability), but remember that this is mainly said by corporate drones, and while there is some truth to the idea, most of them just pump out average to mediocre code that does nothing. Yes, it will be important to roll these things into your approach to development, but remember to put them where they belong (that is, correctness, creativity, inventiveness, algorithmic elegance, and efficiency are much more important). Also, while you may not have all the knowledge and awareness of best practices (be wary of these, and hold on to them weakly as you learn, so you can let them go once you see how things really are) a seasoned Software Engineer would, if you are smart and technically brilliant, then there will quickly be room to do great things.

That is, knowing to use list comprehensions rather than for loops in Python is a good thing, but more important is to have something that's worth doing with those list comprehensions. And if you have something worth doing, then whether you do it with a list comprehension or a for loop is largely irrelevant, and comes after everything else.

Also, weakly hold on to the idea of OOP (object-oriented programming) as you learn it. While it will probably be incessantly repeated where you end up working (along with a lot of other things), you will probably be better off sticking to fundamental ideas and only using OOP when it actually makes sense (and as just another part of an overall design strategy, not some be all end all concept that has to be used everywhere).

Get the idea? You'll learn a lot of things, and hear of a lot of best practices, and you should get a good handle on them, sure, but only after you master knowledge and concepts that are actually relevant, and that actually make you better (it's worth the time to figure out what these are and do them in order of importance once you learn the basics).

Immerse yourself constantly, seek out multiple forms of input (books, online videos, questions on forums, Udacity, Coursera, etc), read code furiously (Github has a lot of code in many languages), and constantly design, redesign, evaluate, re-evaluate, and re-think what you do.

Remember these terms: concurrency, parallelism, AI, machine learning, metaprogramming, automation, etc. Some of them are played out (over hyped), but you'll want to keep these things in mind as you learn what you learn. Most Engineers are ignoring these things or talking about them, but not diving into them or thinking creatively with regard to them, etc, and so are falling even further behind. Don't let this be you! If you get overwhelmed or swamped, then don't even worry about it. Being overwhelmed is a temporary feeling that you'll learn to ignore and is something that will eventually go away. More important is to ensure that what the feeling is warning you about (having too much to do, and so little time that you won't finish) is not an actuality. That is, you don't want what's locking you up and making you panic to be something that you need to learn and do now, now, now!

Overloading yourself with relevant information from different points of view is actually a good thing (especially if you do it before you go to sleep) and can greatly accelerate the speed at which you learn what you need to learn. You may feel confused at first, but that is only a sign to put more things on your mind (even if you aren't understanding all of it), because after you get a good night's rest, you'll return to it all completely clear, or much clearer, and will be amazed at what you know.

The main problem with most Software Engineers is not that they do or don't follow best practices, it's that the don't want to, don't care about, or don't try anything new/creative/innovative. Also, they tend to look for the most half-assed solution that works, rather than learning how to quickly and correctly craft an elegant and complete solution that stands by itself. You will easily be the best Engineer in most rooms you enter (even as a beginner) if you don't fall into this trap, but then you have to also know when to feed others the bullshit, because that is the definition of most rote/routine corporate jobs (passing bullshit around without actually doing anything). Avoid that hell if you can, so you can spend most of your time developing new things, or more importantly, things that are worthwhile.

I remember what I was like when I first started programming (over 10 years ago, even though I only have a few years professional experience), and I've thought back many times over what I was able to accomplish after a few months, and I realize that, while I didn't know much or everything, that I could pretty much tackle and come up with a good, working solution to most problems. And that was the most important thing to be able to do, and is something most people can't (until you start hanging around great or exceptional developers, you won't be able to help but notice that no one can do anything, and that everyone will try to get in your way and hold you back once they figure out you know something about anything). Once you have an idea of what you want to do, or how to make something work and real, then comes the process of making the code cleaner, more efficient, more elegant, etc.

Never fall into the trap of thinking "throwaway code" or "scratchpad code" is a bad idea. When in doubt, write the code! Once written, things usually clear up, you see exactly what you're trying to do, you see gaps in your thinking, and you can play around with what you've written (no matter how crappy it is) and can use that knowledge to write a better program. Never underestimate the effect of just getting on with it, writing what's on your mind, then assessing it to see what you really want/need to do. No, it's not wasted effort, duplicated effort, lack of experience/training, or anything else that will be told to you, it's an absolutely brilliant approach (well, not in general, but more because the powers that be speak against it). The more important idea is to not leave your code in that shitty/half-assed state, but to then improve it once you have a good sense of what you are trying to do.

Also, while it can take a long time to become a good developer, that's a truth that is relevant to most people, and most average to sub-par developers, not everyone! Some people are good before they even start, and it's a matter of how quickly they can learn the syntax, details, and best practices. And others instantly click with and recognize all the approaches that most have to spend years learning, as it's just intuitive to them. Don't let all the blah blah blahs (usually from people who had to spend an eternity to still not know anything and who are doing nothing but trying to hold everyone back and slow everyone down) get in your way, or stop you from doing what you're doing. Most advice is shit. Start with anything. Start with whatever will get you learning and up to speed with what you need to know, then ditch it for what you figure out is actually the truth or the reality.

Read a lot of code, write a lot of code, look for random challenges (not just topcoder type challenges, but actual problems that people have solved or that are worth solving) and develop solutions to those as you learn.

It's all about the ability to solve problems, to come up with elegant/efficient/correct algorithms, and to think differently. Anything that's said suggesting otherwise is a reflection of the corporate BS designed and heavily pushed with the sole intention of making everyone mediocre. Playing the "yes master" game with all that nonsense is part of advancing your career, and is not something you should make a part of who you are, or accept blindly. Keep that all at arms length, and view it as something to be handled with a facade, much like politics and bureaucracy. Nothing will make you a mediocre and useless developer faster than listening to that garbage.

Get started, do it, get it done, then do it right, make it better, then repeat.

Also this is something to remember and something that is relevant once you past the beginner stage: even when you are 10+ years into your career, you should remember to not mess around with all the BS, but to instead get right to it, throw away whatever's irrelevant, and move on. Unlike what you hear from everyone, things shouldn't take an eternity, and in most cases, it won't take long to learn what you need to know.

Remember, remember, remember: there are a lot of people that will try to hold you back, and that will try to keep you from being able to do anything, and most "advice" is stated with the sole intention of doing this! Always remember that hindsight will paint this reality quite clearly, and the last thing you want to end up doing is regretting your decisions. Just realize that some people, good or bad, skilled or mediocre, well intentioned or not, have it wrong, or have had a lot of crap beaten into them, and they may be trying to push it all onto you.

Always try to get as much as possible from what you're learning, but never get stuck on it, settle into it, or get accustomed to what you've picked up, because it's not always relevant, it's not always that great once you're past the clueless phase, and it's not always complete, advanced, or what you'll end up seeing as correct. A message/reminder for a time when you start questioning things: "Yes, it's what it looks like. Move on to whatever you think is better."

If you enjoy the process of learning and of learning how to code, design, and piece together solutions, then this will be an incredible and satisfying experience (it never ends, but in a good way). And it's even better now that you won't be limited by or constantly bombarded with the "write documentation, write proofs" BS that most professors/teachers push. The internet provides a great deal of information and live knowledge, and while there is a lot of crap as well, if you never get stuck to anything, then you'll be able to let go of those things once you realize what they are. Also, it's good that you won't have overly competitive annoying idiots constantly breathing down your neck and getting in your way trying to ensure that you never get better than them (ie, that you never go anywhere past mediocre, because that's all they are) and that you have the time, space, and freedom to learn things in exactly the way you want.

Get a few books, etc, and jump around as you need to in order to piece everything together. The great thing about this is that many beginner questions have already been asked and answered on sites like StackOverflow, so whenever you have a question and it really won't help if you figure out the solution yourself, then it's great that you can just search online.

Also, don't underestimate how well-rounded and strong multiple perspectives will make you. At the end of the day, engineering is about solving problems and getting on with it, not about this rote, repetitive, regurgitated, best practice conformant crap that you'll keep hearing about. Remember to ignore that garbage! For example, the few things I learned from Electrical Engineering courses (Kalman filters, designing hardware/circuits, etc) have all been used and applied to programming problems time and time again. Also, the user-centered design and user interface design skills that I've developed have repeatedly offered me insight and clarity into what needs to be solved (and how to do it) in many situations. Don't be afraid to learn as many different perspectives as you can, then tie them together. Scratch that. Learn things from as many different perspectives as you can, and see as many points of view as you can, and learn things from whatever disciplines you can, then hold onto that knowledge, because you'll need it (and will find it relevant and something that sets you apart and makes you great once it's time to actually do anything).

Also, at the end of the day, it's about the problem you're solving, solving the right problem, solving the problem well, wrapping your mind around what is actually needed, and coming up with something that works well to address the issue, not about using all the right "best practices," etc. Remember that most people are dissatisfied with the solutions they are offered by most programs, websites, apps, etc, and if you do the same thing those creators/designers/developers are doing, rather than what you should be doing, then what you produce will be much the same crap.

People don't pay enough attention to correctness, algorithmic elegance, efficiency, user experience, solving the problem, or anything else that actually makes things better. And if you become one of those, then you now know what's waiting for you. Once you've gotten a good handle on what I've just said, then sure, work on making your code maintainable, documented, conformant to best practices, etc. But you should never trade correctness, elegance, efficiency, etc for this other crap. Always remember what really matters!

Back in 1985, after four years of college, three years of law school and four years of practice, at 30 years old, I was palpably unhappy with my choices. I took some aptitude tests ("Johnson O'Connor Research") and they made it clear I had aptitudes that were not being used in my practice.

I quit my job, moved from Texas to California, and planned to get into some technology related law like intellectual property. While I was waiting to take the California bar, I took a couple of classes (one on C Programming and one on the UNIX operating system) at U.C. Berkeley Extension. I took the bar, and, while I was waiting for the results, decided to try to find a job programming to learn a bit about the industry. I got a job with a guy who was writing a cross-compiler for Motorola chips. I got to write a command driver and an ANSI C runtime library. I passed the bar a few month later, but I was having so much fun it didn't occur to me to go back to practicing law.

I'm still at it, thirty years later. Best decision I made in my life. The truth is that if you love what you're doing and you have a knack for it, you'll learn everything you need to know. Your passion will make you an incredibly valuable resource to anyone you work with or for. You are by no means too old to pursue your passion. Go for it.

Hell, no. I'm 41. I began teaching myself web programming four years ago. I audited one computer programming class at a local college, read computer books voraciously and started trying to write useful code immediately.

I got my first paying gig building web sites less than six months later. I maintained a steady, small income freelancing for six more months. I worked a year doing desktop support and then got my first programming job.

Now, I build awesome web applications full-time working from the bare metal on up for University of Texas faculty and staff in three different programming languages. I'm not unusual in any way. Just a regular guy, with a regular brain, a regular computer and the ability to read.

I'm well over fifty. As a programmer, I have to keep up with new technologies every day - right now I am learning about sip protocols, a new framework called Famo.us (check it out, it is great), and how to implement big data solutions on Linux. You don't ever stop learning in this game - one of the great things about it is that you have to keep using your brain! On the downside it means spending long hours figuring out stuff with a manual in one hand and hope in your heart - and you probably won't get paid for much of that time, either. And it also means that most people won't understand what you do, and only a few will ever appreciate how elegantly you do it, so be prepared for that too.

When I was in my mid forties I started learning Russian. Five years later I married a Russian, and now we have two kids - so I didn't start learning how to be a dad until I was fifty.

One of the most annoying things about life is that people keep on limiting themselves and each other by applying silly notions about how old you should/should not be to do stuff. Being an older dad, has its downsides - you can never be sure how long you'll be around for your kids (but that is true for everyone, it just feels a bit more real when you're older). But it also has upsides too - I would have made a lousy father in my twenties when I was being crazy and playing in a rock band. For other people it will be different and they probably think I am mad wanting to bring up kids rather than relaxing at the weekends.

Finally I would agree with other posters - programming is something you have to be committed to. Most people who are really good at this stuff are self taught - I studied to be a zoologist!! Haha. To be honest, a lot of people in the UK here who learn programming at University learn how to do the wrong stuff the wrong way using the wrong techniques and the wrong technology and what's worse, they come out with the wrong attitude too! I reckon it should be more of a vocational thing and if you can do some college courses and get a job actually programming as soon as possible you will stand a better chance. Freelancing is fun too - I have spent most of my career as a freelance developer, and I wouldn't do anything else.

Go for it - if you want to do something in life take a deep breath and get stuck in - it's one of the best things about being alive.

In short my answer is NO.

First of all, being a good programmer is independent of programming languages. What I want to say is that, a person who knows only one programming language can be a better programmer than a person who knows many programming languages.

Now, back to the question.

Computer programming is an art.
- Donald Knuth (father of the analysis of algorithms)

If you want to be an artist, you need basic tools and basic understanding of draw mechanism (developed by practicing over time). After that you are on you own. Creativity is the limit.

Similarity, if you want to be a programmer. You need basic understanding of computer logic/mechanism i.e. algorithms and data structures. And, you need tools compiler/IDE etc. Again, creativity is the limit.

Computer programming is an art and also a science. But, since question states a programmer not a researcher so I'm not discussing science aspect of it. Although, it's not mandatory but if you're good in maths than it'll really boost your learning process (sometimes exponentially).

If you're good in other fields than you can make it an advantage, as it's relatively easy for you to do something new in your field (there are many fields which still don't have enough programmers that means many new things to do), which will increase your interest in programming.

Some people also states that programming is a skill. The more you code the faster and better you get. That's also true in case of an artist but as you know skill solely won't make great artists (that's why it's an art not sketching).

Believe me, if you are a technical person it'll only makes your life easier. And, future demands it. Play the GAME then decide it's good or not :)

I'll give you my own example. I started programming at the age of 12 (familiar with computer from the age of 5). One of my good friend hadn't worked on computer till the age of 17. We did a project together and there was a time when I gave-up but he found the solution.

PS:
Please ignore grammar or spelling :D

As many others have said, it’s never too late. But one thing you need to be a good programmer in my humble opinion is a genuine interest. I have had many friends who want to be programmers, who want to make computer games or apps as they see major success of other people and want part of it. They went to university and learnt there and when they come out they struggle for work, the reason for this is simple. If you have a genuine interest in the subject, you will self explore. I got into programming when I was younger when my dad taught me some BBC basic and I started making text adventure games. As I got older I’d buy books and start learning other languages and self exploring. There is only so much other people can teach you. Part of the journey is learning yourself and having that drive to overcome any obstacle. While getting a qualification will help, and will hopefully teach you some best practices and help fast track you through some rookie mistakes. It will not put you at the top of the pile when somebody looks to employ you. If you live and breathe it with enthusiasm, work on lots of things as you learn, publish them online for people to see. This way when you go for an interview you can show your work, which will show how much enthusiasm you have for the job.

You will make lots of mistakes. I look back at old code I wrote when I was younger now, and see so many things I’d do different. You are always learning, if you’re not, then you’re not progressing. I always give myself a bit of time here and there to explore something new that I’ve not done before. These are all things you can do at home. Download visual studio or another IDE and start today! Create, share, make mistakes, get better and have fun. The world is your oyster.

No! I am 50, and although I got a grounding in coding on a Sinclair ZX-81 in Z80 assembler and Sinclair Basic in 1981, and did a bit of 6502 Assembler and BBC Basic on the Acorn BBC Micro, since about 1986 I have not done any more programming other than the odd HTML/CSS on the web, opting to be a designer instead because complex maths and algorithms messed with my brain. (It's a creative thinker thing!)

However, sensing that like a good wine my intellect had in fact improved with age, earlier this year (2014) I bought that well known O'Reilly book on PHP, MySQL, CSS, JavaScript, HTML5, etc., etc. on my Kindle, and read it. To my surprise, I understood it all, and if it wasn't for the fact I lack the time to re-start programming full time (I run a company), I would do so. I will however help organise and tidy up code developed by my engineers.

The point is, if you have the mental clarity, self control (to focus on learning rather than reading Quora - ha ha!), then like anything in life, educating yourself is probably the best thing you can do with your time. Most of the other things we do in life, (which remind me of the iPad's use VS a Galaxy Note), involve consumption and entertainment, NOT creation and productivity. (Think about that one!)

Yes, coding is as many of us creative visual thinkers say, a bit of a 'mind f*ck' due to the sometimes complex array structures, algorithms, formulae, etc., but if you get some help and really make an effort, and you do have the intellectual chops, it is worth a try. And don't forget, our brains, like muscles, do improve with use.

To make things easier: Get a good night's sleep, go for an early morning run, have ONE good ground coffee with your protein-rich breakfast, if you cannot get peace and quiet (kids, etc.), invest in a pair of Bose QC15s (awesome!) and try to get some quality time alone, such as in a library. You really do not want to be destracted, although you should take short breaks to delay fatigue and loss of focus. This comes highly recommended as a GTD method: The Pomodoro Technique®

Finally, my No.1 bit of advice is that before or after you have finished any books, look at well-written source code from other applications, sites, etc., and try developing your own project/application where you'll be forced to learn how to do things that may not have been covered in any educational materials. You have the benefit that we did not in the 1980s of vast sources of information online, not to mention Stack Overflow and when you join a team, GitHub.

Programming is a skill that is essential throughout a career in technology. First and foremost, it is never too late to become a good programmer. Every day, you should practise programming.

The biggest obstacle you'll have is deciding what kind of programming you want to pursue, not "coming late to the game." Think about Bill Gates, Mark Zuckerberg when they start learning coding.

There was no YouTube, Google, or anything else. Because you have all of these resources at your fingertips, your ability to accelerate will be determined by your thinking and, ultimately, your desire to reach your goals.

Here are few things that I believe any fiery student or person should do now to improve their programming skills and self-guide their career choices.

1. If you're passionate about coding, you should always consider the situational circumstances of your code, rather than the code itself. That's something you should leave to your subconscious mind and brain. Problem solvers are programmers.
2. Look for a mentor. Someone with 10+ years of experience and a portfolio of projects completed or participated in.
3. Find high-value learning sites... one of my favourites is Logicmojo. I adore what they're doing and wish I had more time to spend there. You'll find some of the world's smartest people volunteering their time.
4. When people realize you started learning programming at this age, they are less likely to believe you. It can take some time for people to recognise you based on your abilities rather than your past. Simply learn at your own pace, and you'll be no different from other programmers after a few years (for me, it took about two years). You're capable of going above and beyond.
5. Make something! (Practice, practice, practice!) It is insufficient to simply listen to the lectures and take notes. Make programmes and complete assignments. Doing assignments taught me the most, although at the cost of restless nights. I didn't have time, but you should create your own projects depending on your passions. The most enjoyable aspect of studying is creating something. It will astound you how much you can do and how it is never too late to begin.

So don't worry, my friend, you're still young and your options are endless; it's never too late!

No, it is not too late.

I was 24 when I started learning to code in 2012. I graduated with a bachelors in theatre in 2011, and now, almost three years later, I am working at an amazing tech company in Michigan. Like Erin said, read everything, do every tutorial, then do it again. I would highly recommend CS50X from edX.org. David Malan is an incredible professor. The class is hard as hell, but I learned a TON. http://Codecademy.com <--Code Academy is a fabulous resource, as well as many other programming classes available at edX, Coursera, and Udacity. If you want to learn Ruby, Ruby Koans are a great way to do that as well.

Another suggestion that I found equal parts terrifying and extremely helpful: go to conferences and meet ups. A lot of conferences will have financial assistance for attendance, and even more meet ups are free.

But the best thing is repetition. And, Do. Not. Give. Up.

I was unhappy and lost before I discovered programming and my only regret is that I didn't discover how much I loved it sooner.

Don't do it for what you think will be all the money you'll make. If you don't love it, it will make you miserable. Being stubborn almost to the point of stupid is helpful as well, especially up against a bug after three days of trying to figure out what the hell is happening.

Don't be afraid to ask for help or questions.

And read http://stilldrinking.org it gives a hilarious perspective of web development that is well worth the read if you are considering that.

It is never too late to start learning and pursuing a new career, especially in the field of programming. While it is true that some people may start learning coding at a younger age, that does not necessarily mean that they will be more successful or have an advantage over those who start later in life.

Many successful programmers have started learning coding later in life, and there are numerous resources available for those who want to get started. Online courses, bootcamps, and even self-study materials can all be useful in helping you learn the skills you need to become a programmer.

Additionally, the field of programming is constantly evolving, meaning that there will always be new technologies and languages to learn and master. This means that you can continue to learn and grow throughout your career, regardless of when you start.

It is important to remember that age should not be a barrier to pursuing your goals and dreams. If you are passionate about programming and have the motivation to work hard, there is no reason why you cannot succeed in this field.

So, to answer the question, no, it is not too late for you to start learning programming and pursue a career as a programmer. The most important thing is to be dedicated, work hard, and continue learning and improving your skills. With these things in mind, you can achieve your goals no matter when you start.