I could do it, if I had "X years of experience in the field"... but that illustrates another problem: companies want workers "cookie-cutter made" for the position and are unwilling to expend time/effort in training. (This is regardless of programming language and even a quality of the "entry-level positions.")
it's another one of the side effects of the fact that neither companies nor employees have any loyalty to each other these days. Why train someone if they can just take their knowledge somewhere else? Why should an employee have any loyalty to a company when so many are run by folks who see their employees as just another 'resource' to be slotted? One ot the things that I see that is really tragic is that companies put no value on institutional knowledge. I recently was eventually passwd over at a company that I used to work for because I was considered "too expensive", even though I had over 10 years worth of institutional knowledge of processes, procedures, and environments (I built a lot of the infrastructure). I was quite clear with them that they were going to have to pay some kind of premium for that knowledge if they wanted me back. The delta I was asking for wasn't really all that much, but to me the principle was important enough to push for it. They choked on it anyway, and I simply wasn't willing to accept their lowball offers. In the long run, I guess that's a good thing because I left the place for a reason, but it was disappointing to see that even with the huge turnover they have had in the past year, they just couldn't see any value in that kind of institutional knowledge.