Technical bootcamp 3/1 to 3/2 Retrospective - Please answer the following questions

[dkalmin]

What do we do well?

What could we have done better?

Ideas and suggestions?

[Paraya001]

I thank you for the bootcamp, it provide me a better perspective on GH and the functionality we can use for migration but specially the security features it has, I feel the format is correct.

[francislacroix]

Generally, I felt the the workshop was good. Especially liked the labs, since I'm more of a hands on learner. If there is one thing I would improve, is reduce the amount of overlap with the Overview Bootcamp, and enforce it as a pre-requisite. But it didn't remove much from the workshop overall.

Thank you very much for the great delivery and information.

[dachou]

What do we do well?

Labs allowed for hands-on tinkering and learning. Nothing beats hands-on experience for learning. Instructors/proctors were very helpful in troubleshooting issues and helping us move along. The structure of labs (repos) and organization setup (which required invites, etc.) helped instructors to look into issues right away, as opposed to needing us to share screens on our own individual and disconnected repos/environments. Love that we did everything in GitHub (even discussions like this). This bootcamp really gave us a great overview of features in GHE, and how things worked.

What could we have done better?

Some parts of the labs were missing some minor details that have caused confusion for people (e.g., the AzDevOps personal access token that we don't have access to, needing to 'cd valet' before running valet (and enable permissions), etc. Although, some of these omissions of details made us poke around and try to troubleshoot and learn, as opposed to blindly follow the steps. It's not a bad thing, but for some people this may have made things more difficult than necessary.

Ideas and suggestions?

Takeaways, swag, next-steps, etc. Things that can help us take these learnings further.

[ckellywilson]

What do we do well?
The materials were well organized and easy to follow.

What could we have done better?
It would be good to have more explanation for more new folks to GitHub Actions. There could have been 2 full days on just configuring Actions.

Ideas and suggestions?
Deeper dive on Actions and leave GHAS for a separate Bootcamp. Just my thoughts.

[sriniambati]

What do we do well?
Simple, easy to follow, and understand labs. Three hours session vs. all day was a big help. Delivered very effectively by GH team, especially David Kalmin.

What could we have done better?
Provide more use cases and labs on GH actions.

Ideas and suggestions?
Include new features like GH Project (Beta).

[asalbers]

What do we do well?

What could we have done better?

Ideas and suggestions?

I really liked how the content was presented and the hands-on lab did a great job of reinforcing the concepts. A few things that could be improved upon would be better communication on invites to orgs/repos and maybe more details on the steps in the hands-on labs. I have worked with actions and other github pieces a decent amount, but if someone that isn't as familiar them and went through those same labs they might run into some issues.