To what use would you put mature-age beginner programmers?
If you were a potential employer, what would you hire them to do, and what skills would you want from them?
My thoughts so far: - I think it's necessary for students to understand ticketing (e.g. Jira) and how to commit code to git, what branches are and so on. I can't imagine a job where this isn't a required job skill. - An option: I can include Selenium in the course, so they could be employed in QA/test. - Or, maybe I could teach them about the imortance of unit tests and the like; then they could be employed writing all those tests that you code-base doesn't have, but should have. - Should I double down on (for example) Django? - I won't have time to do a full machine learning course, but I could teach pandas and guide students towards data analytics roles in the sorts of organisations that do data analytics in Python (rather than Tableau or other BI tools).
What would help your job hiring pipeline?
13 comments
[ 4.4 ms ] story [ 42.8 ms ] threadIs that the sort of thing you would want to see?
I can probably come up with some way of doing a pair programming exercise (the course is fully remote because of lockdowns).
Git Ci/cd Scrum/agile/standups Jira Etc
That stuff alone is more than enough imo
My challenge to you as a teacher would be
Can you get them relatively comfortable with git?
Like actually comfortable?
I suspect no, but that is on git not you
Not just git but github etc
How to debug?
How to set up a virtual environment and why.
Diff between 2 and 3 and why.
How to dive into a code base you don't know shit about, run some broken web app in your dev env, then find the broken code, pull/clone/branch/commit/push, etc.
Ideally maybe push them for a particular position that may interest them
QA and Support are good starting points for any aspiring dev
Really my advice is for old and young
If you're able to, I'd talk to folks about how much they actually like or hate this stuff
Most will likely not want to be honest but you might be able to pull it out of them depending on what your goals are
Talk about other positions dev evangelist/marketing, pre-sales engineer, tam, product/project manager, etc.
Where the challenge lays in my opinion is how to pass on the knowledge required to start coding. I feel Selenium is quite nice start because by writing simple few lines of code the newbie can see the actual action on the screen. I also feel the attitude is important too - I still remember 20 years ago when I was at the beginning of my journey I was thinking about a programming like about solving puzzles, and after watching tron I always wanted to build a perfect system whatever that means :) I feel it's quite difficult to pass on this kind of weird motivation.
You should seek some direction from the employers where they will be placed. Unless they give an indication towards QA and ML or other niches, I would just make sure they are well grounded in the basics and have full-stack web experience.
> employed writing all those tests that you code-base doesn't have, but should have.
Writing tests is usually more difficult than writing code. Writing tests which the programmers who wrote the original code could not figure out how to write is exponentially more difficult.
I am sure you will be able to add a line to your resume, these folks will enjoy their time and free money, but I do not envy the people who'll have to endure their certified 40 hr skillz.
Finally, if you do good work be pleased with yourself. The government money meets unrealistic business expectations for short term training is not a new story :-)