Create a Guide/Template: Professional Development

[gregpawin]

Overview

We need to create a guide to making professional development: a checklist of things that every developer should prepare in order to successfully promote themselves in order to find a job.

See https://github.com/hackforla/engineering/issues/14#issuecomment-1711831590

Action Items

• [ ] Gather examples of how other projects have done it, adding each example as a link in the resources section
  • [ ] Once done, remove the "TG: Gather Examples" label and add the "TG: Draft Template" label
• [ ] Create a draft template, either in markdown format in this issue or a google doc in the Engineering google drive
  • [ ] Once done, remove the "TG: Draft Template" label and add the "TG: Create Guide" label
• [ ] Create a guide on how to use the template
  • [ ] Once done, remove the "TG: Create Guide" label and add the "TG: Review Guide" label
• [ ] Review the guide with product management communities of practice
  • [ ] Once done, remove the "TG: Review Guide" label and add the "TG: Leadership Review" label
• [ ] Present to Hack for LA leadership team for sign off
  • [ ] Once approved, remove the "TG: Leadership Review" label and add the "TG: Place Guide" label
• [ ] Possibly create an issue template on .github
  • [ ] Include link to template under resources if you add it as a template in .github

Resources

Update tracker issue (TBD) with the name of item you are working

[gregpawin]

Notes from last week's discussion about professional development:

• Slack channels a major source of job recommendations
• Alternatives to traditional job postings ie. Indeed
• Development of StackOverflow rating used to be a useful tool
• Pre-COVID Meetups were important
• Microblogging: Dev.to, Medium, Twitter
• Website/Github/Portfolio
• Only list skills that you really know
• Don't sell yourself short, don't label yourself as a beginner
• Publishing articles about how to do things shows that you can communicate

[ExperimentsInHonesty]

@Olanrewaju-Ak Please provide update

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

[Olanrewaju-Ak]

@ExperimentsInHonesty my sincere apologies. I had been MIA for a while now due to some personal issues and haven't made any progress on the issue.

[ExperimentsInHonesty]

This will need to be broken down into multiple guides. And they should be full of examples from Hack for LA alumni. But each needs to be very how-to