>Match the person with the job Absolutely. >or train them if they aren't a 100% match. If they're close, sure. If they're not, then odds are unfortunately go

>Match the person with the job Absolutely. >or train them if they aren't a 100% match. If they're close, sure. If they're not, then odds are unfortunately good that they aren't trainable, at least with respect to certain categories of advanced programming. I could probably train anyone with decent technical aptitude to do web page work, or simple CRUD backend server work. There are probably still people who couldn't learn it; I think there needs to be an aptitude regardless. But core game programming (engine work, graphics work, but not simple scripting) and certain kinds of embedded development (especially if video is involved) are realms that I'm familiar with that have a higher barrier to entry, and where "training" is probably going to fail more times than not. As in fail 90% of the time or more. I think the cutoff is when you go beyond the point where a topic can be completely "taught" at all, and instead the task itself requires the developer to have exceptional learning and analytical skills. If a developer is good enough at figuring things out to actually get the work done, then any training would be unnecessary, because you would be able to learn what you need to know to get started on the job. Then what a new developer needs isn't "training" but just "orientation" to the tools and methods used in the domain in question.