I'm almost 50 and still do embedded systems programming, hardware design and development (because I want to). I can do C, C++, HTML, Javascript, assembler (any processor) and a lot of other stuff. I have worked on long projects (2+ years) and ongoing development as well as the small stuff. And just to rub salt into the wound, I have no university degree. I also know several others who have "gotten there" without the formals, and do very well for themselves. But we all pay our dues somehow- whether by working on that degree or by less formalized hard work and dedication.
If you really can't go get some formal education, you had better get all the informal you can. Read. Learn. Do. Read more. Study other people's work until you understand not just how they strung those lines of code together, but why. Learn the theoreticals, not just the practicals. Do not stop learning for any reason- you will be dead in the water. Unlimited emphasis on this.
Even when you get that dream job, Read more, learn more, do more. Also, brain-suck anyone you work with who is high-skilled. Most pros like to share (and return the favor when you can).
You can be a "coder"- which is the tech equivalent of a factory worker - just by going to school and having good specs to write from. But you and Mister Bsc need to bring much more to the job than the ability to string lines of code together. As others have mentioned.
Also, capitalize on what you do- which includes writing utilities such as you mentioned and make sure people know about them and critique them. This is critical: you must be known for the things you want to do and can do. Now stay in touch with these people as they move about. Be sure they know what your goals are. Sooner or later, someone will be in a position to say to their employer "I know a guy who does that and he's really good. Want me to give him a call?" This is an extremely powerful thing- the personal reference from soeone on the inside. Whatever happens, don't let them down or it will be your last.
There was a time when almost 100% of programmers in technical and embedded came from something else. I suspect it is still >30%. Consider: On small team and individual projects involving "the real world", sometimes the former help desk guy who can program might be the best geek for the job on that new in-house help desk app. Breadth of knowledge is very important when you are trying to get into the field. Bring more than the basics, bring problem-space knowledge whenever you can.
Still, if you can get it at all, get the formals. Thanks to my mispent youth and working class screw the elitist snobs attitude, I essentially blew away 10+ years of my career. Given a chance to do it over, I would be a most diligent student.
And stay focussed. Opportunities come by all the time when you know what to look for. Learn to see them. Take advantage of them. Sometimes, a little exposure to a particular field is more important the the pay. This need not mean taking a particular job, it can mean doing things like becoming part of an open source project, or doing some tech-head work for an organization that needs it.
Good luck.
Slashdot Mirror
Go to http://www.vmyths.com and search for mi2g under RANTINGS.
Credibility is not their strong point.
I'm almost 50 and still do embedded systems programming, hardware design and development (because I want to). I can do C, C++, HTML, Javascript, assembler (any processor) and a lot of other stuff. I have worked on long projects (2+ years) and ongoing development as well as the small stuff. And just to rub salt into the wound, I have no university degree. I also know several others who have "gotten there" without the formals, and do very well for themselves. But we all pay our dues somehow- whether by working on that degree or by less formalized hard work and dedication. If you really can't go get some formal education, you had better get all the informal you can. Read. Learn. Do. Read more. Study other people's work until you understand not just how they strung those lines of code together, but why. Learn the theoreticals, not just the practicals. Do not stop learning for any reason- you will be dead in the water. Unlimited emphasis on this. Even when you get that dream job, Read more, learn more, do more. Also, brain-suck anyone you work with who is high-skilled. Most pros like to share (and return the favor when you can). You can be a "coder"- which is the tech equivalent of a factory worker - just by going to school and having good specs to write from. But you and Mister Bsc need to bring much more to the job than the ability to string lines of code together. As others have mentioned. Also, capitalize on what you do- which includes writing utilities such as you mentioned and make sure people know about them and critique them. This is critical: you must be known for the things you want to do and can do. Now stay in touch with these people as they move about. Be sure they know what your goals are. Sooner or later, someone will be in a position to say to their employer "I know a guy who does that and he's really good. Want me to give him a call?" This is an extremely powerful thing- the personal reference from soeone on the inside. Whatever happens, don't let them down or it will be your last. There was a time when almost 100% of programmers in technical and embedded came from something else. I suspect it is still >30%. Consider: On small team and individual projects involving "the real world", sometimes the former help desk guy who can program might be the best geek for the job on that new in-house help desk app. Breadth of knowledge is very important when you are trying to get into the field. Bring more than the basics, bring problem-space knowledge whenever you can. Still, if you can get it at all, get the formals. Thanks to my mispent youth and working class screw the elitist snobs attitude, I essentially blew away 10+ years of my career. Given a chance to do it over, I would be a most diligent student. And stay focussed. Opportunities come by all the time when you know what to look for. Learn to see them. Take advantage of them. Sometimes, a little exposure to a particular field is more important the the pay. This need not mean taking a particular job, it can mean doing things like becoming part of an open source project, or doing some tech-head work for an organization that needs it. Good luck.