I'm a bit uncertain about the first items, Lifecycle, Components, and Persistence. This is precisely the type of thigns I wouldn't expect a junior to actually know much about. It's a highly specific API set that wouldn't transfer from any other dev job. They can also be learned relatively quickly, especially with a mentor nearby that can quickly direct them to the right places.
Using shortcuts for the studio just seems like nitpicking. If you can do everything with a shortcut why even bother using the studio, wouldn't command-line tools be quicker? A major purpose of an IDE is to make functionality easy to discover and easier to remember.
Design patterns, and perhaps git, seem fair, but your other requirements go beyond what I might expect of a Junior programmer. Most of this I'd expect them to learn on job, as it's domain specific.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm a bit uncertain about the first items, Lifecycle, Components, and Persistence. This is precisely the type of thigns I wouldn't expect a junior to actually know much about. It's a highly specific API set that wouldn't transfer from any other dev job. They can also be learned relatively quickly, especially with a mentor nearby that can quickly direct them to the right places.
Using shortcuts for the studio just seems like nitpicking. If you can do everything with a shortcut why even bother using the studio, wouldn't command-line tools be quicker? A major purpose of an IDE is to make functionality easy to discover and easier to remember.
Design patterns, and perhaps git, seem fair, but your other requirements go beyond what I might expect of a Junior programmer. Most of this I'd expect them to learn on job, as it's domain specific.