(August 17, 2019 at 6:56 pm)Jackalope Wrote: Mathilda makes some really great points - though I fully expect a junior programmer will make a lot of those mistakes, at least in the beginning. Proper code review should correct it in time.
The #2 skill I want in a junior is a willingness and ability to understand the workflow that the code they are working on supports. #1 is the ability to work as a team member, with all that entails. Technical prowess is #3 - especially for a junior.
And that's a supervisory level job. I used to help test student software at Purdue. (I frequently had lunch with the senior members of the CS Dept.) When called I'd walk in, slam my hands repeatedly on the keyboard and walk out. If it passed that test they would proceed. The students used to glare at me when I walked past them on the mall.
