First off, as said above QA is not a shit job. A good QA person is worth their weight in gold. They have a good overview of the entire system and they enjoy "destroying" which is the opposite mindset from a developer. A QA person also has the disadvantage of being the person to have to block or delay the release and always has to deal with this pressure. If you can do it well, there's no reason that it's a shit job. Second: If you are still chomping at the bit to go into dev, then start developing stuff at your company. Little tools for testing pieces of the code, dll's etc. Pick a person you work with in dev that's a good person as a mentor and start flying. A good dev person will appreciate the effort and the extra set of eyes. If you can do this well, you can perhaps start fixing some of the problems you find and keep going from there.
Slashdot Mirror
First off, as said above QA is not a shit job. A good QA person is worth their weight in gold. They have a good overview of the entire system and they enjoy "destroying" which is the opposite mindset from a developer. A QA person also has the disadvantage of being the person to have to block or delay the release and always has to deal with this pressure. If you can do it well, there's no reason that it's a shit job.
Second: If you are still chomping at the bit to go into dev, then start developing stuff at your company. Little tools for testing pieces of the code, dll's etc. Pick a person you work with in dev that's a good person as a mentor and start flying. A good dev person will appreciate the effort and the extra set of eyes. If you can do this well, you can perhaps start fixing some of the problems you find and keep going from there.