In the industry there's always jobs that even crappy flash programmers could complete and the manager wouldn't be able to tell the difference. I guess some places have more of these jobs, and some have less. Earlier this year I found a gig doing english education games for kids. Typical stuff. Question comes up in text, sound, or image form, 3 answers show up, if they choose correct one, some success sequence plays on the "game" side of the screen, if they choose wrong failure sequence plays. (The API part was annoying though because they changed the way it works like 10 times along the project)
A personal note from me on this is I was amazed how much easier it is to make money working for some big company than by trying to produce your own projects. And it's really strange to work in an environment where no one has a clue of the difficulty or time requirement of the work you're doing, at best they could only ballpark it to a low multiple. If the funding is good enough, you could be spending 5 times the amount of time it should normally take you to do the work, and no one would be able to call the bluff. Then again, there is the opposite effect, where you're expected to do a completely unrealistic amount of work for a given funding / time allowance. The latter kinda happened to me, I was supposed to construct front-end UI for TV media software (yes, in flash ... loljapan) in about 2 weeks ... Turned out they barely had like 10% of the graphical assets complete during the time I was starting to work on it, so the project had the kaibosh put on it.
I think this story servers as a good lesson for beginner programmers to voice out their complaints to upper level / management when the conditions are just not right. The project I described was actually my first real professional work experience. I was both over-confident in my abilities and over-willing to do the project despite the visibly crazy time requirements, and I barely voiced out any complaints about other people not preparing things right, or project conditions being just unacceptable. We had a korean programmer come into our office as the project began, he was supposed to be here to assist with the workload. We had a tiny portion of assets available to us, and while I was trying to do as much work possible with the given assets, he pretty much recognized that the project was a ship about to sink, and he ditched out.
I think it's important to be firm with managers about bad conditions, and it also makes you look like a matured experienced programmer.