" Now, at my new job as a software dev, I'm working with a lot of non-devs that are fresh out of college and extremely frustrating to work with (some are barely literate)."

"the bad [non-devs] are the ones that monopolize all of my time."

It sounds like there are specific aspects of your job that you find irritating. I don't know much about your situation, but I think that it might help to have a chat with your line manager to review your role and responsibilities.

A badly defined role can do wonders to make an employee quit.

This chat might clarify the extent of the help and support you are supposed to be giving to those 'non-devs'. If helping them out is expected from your role, then you should definitely keep doing it and eventually find a more satisfying role elsewhere. But, if it turns out that you don't really have to spend so much time with them, then it's important to understand who is supposed to coach and train these 'non-devs' to help them get up to speed.

Now, at my new job as a software dev, I'm working with a lot of non-devs that are fresh out of college and extremely frustrating to work with (some are barely literate).

the bad [non-devs] are the ones that monopolize all of my time.

It sounds like there are specific aspects of your job that you find irritating. I don't know much about your situation, but I think that it might help to have a chat with your line manager to review your role and responsibilities.

A badly defined role can do wonders to make an employee quit.

This chat might clarify the extent of the help and support you are supposed to be giving to those 'non-devs'. If helping them out is expected from your role, then you should definitely keep doing it and eventually find a more satisfying role elsewhere. But, if it turns out that you don't really have to spend so much time with them, then it's important to understand who is supposed to coach and train these 'non-devs' to help them get up to speed.