Too late to learn programming?
Nope. I learned at 30, employers snapped me up half way through the last year of my degree and been working software development for 9 months now.
If it's what you want to do go for it. Never too late and you're only 26.
_________________
Your neurodiverse (Aspie) score: 133 of 200
Your neurotypical (non-autistic) score: 85 of 200
You are very likely neurodiverse (Aspie).
RAADS-R: 141
AQ Test: 34
EQ: 20
It's never too late to learn anything. Learning only requires dedication and effort, it's not about how 'smart' you are or how quick you can think, it's about hitting the books, focusing and absorbing that information. "Programming" is a large concept, you need to figure out what fields you want to enter to choose the appropriate language. If you're interested in developing games, javascript is a poor language to learn, likewise if you want to work on web apps C++ is terrible language to learn. Each language has it's own niches based on the performance and compatibility of the language. Also, I forgot robotics, probably the hottest field out there right now, but you'll need a firm grasp of physics as well as programming to excel at that.
Truth be told most 4 year institutions don't teach programming, they teach data theory (how efficiency is created, how to avoid poorly designed structures, etc.) and while data theory is important it's not near as important as actually being able to write good clean logical code in your language of choice. My recommendation is find a language that's used in a sub field of programming you're interested in and find online tutorials. Books are ok, but in the modern era books become outdated rapidly, whereas an online tutorial site will have a high probability of being up to date. Also, look for tutorials that have you build something, not just random functions and objects with no real purpose-- that's the easiest way to kill your enthusiasm. You want a result from your learning effort, some program to show that you can then alter or build upon after the tutorial is over, which can also be the first piece of a portfolio.
Truth be told most 4 year institutions don't teach programming, they teach data theory (how efficiency is created, how to avoid poorly designed structures, etc.) and while data theory is important it's not near as important as actually being able to write good clean logical code in your language of choice. My recommendation is find a language that's used in a sub field of programming you're interested in and find online tutorials. Books are ok, but in the modern era books become outdated rapidly, whereas an online tutorial site will have a high probability of being up to date. Also, look for tutorials that have you build something, not just random functions and objects with no real purpose-- that's the easiest way to kill your enthusiasm. You want a result from your learning effort, some program to show that you can then alter or build upon after the tutorial is over, which can also be the first piece of a portfolio.
Excellent advice.
_________________
"There once was a little molecule who dreamed of being part of the crest of a great wave..."
(From the story 'The Little Molecule' - Amazon Kindle, 2013)
I'm 28, and just started learning to code a couple of months ago! There are great online classes now, such as Coursera, Udemy, and Codecademy, among others. Learntocodewith.me is also a helpful site by a successful woman self-taught programmer. As long as you start, and don't stop (for too long), you will surely get there!
It's not like you can't learn data theory online too. The two institutions I went to though, I noticed that was the majority of the computer sciences classes were data theory type classes. Neither one had actual programming classes, they kind of expect you to learn the languages on your own I believe. Job title wise though, I'd say DBA (database administrator), and SE (systems engineer). The DBA oversees the formatting and maintenance of a database. The database needs to efficiently store data, so there's one location. Systems Engineers generally design the what I would call the 'backbone' of an application and set style guidelines, everything the programmers and developers (in today's world those two are basically the same thing) need to do their job so you'll need a good idea of efficiency and performance at that job. Someone who currently works in the field would have a better idea though, I haven't been in the business since pretty much right out of college ~2005.
I would think so. That said the IT job market has changed drastically in the decade since I was in it, the financial collapse hit IT just like everyone else, so that increased competition may mean companies require more official documentation of your skills than before (i.e. more degrees/certificates).
Similar Topics | |
---|---|
Grace Hopper - Pioneer of Computer Programming |
24 Oct 2024, 10:47 pm |
I want to learn flirting |
20 Aug 2024, 9:39 am |