Technical bootcamp 5/17 to 5/18 Retrospective - Please answer the following questions

[dkalmin]

What do we do well?

What could we have done better?

Ideas and suggestions?

[rochabr]

What do we do well?

Labs were pretty simple to follow and explained the functionalities really well. It was as great way to get my feet wet. 9/10!

What could we have done better?

The presentation layer felt rushed at a few times.

Ideas and suggestions?

An advanced version of this workshop would be great. Focusing more on different actions, best practices and customer stories.

[SenthuranSivananthan]

What do we do well?

• Good level of content for theory
• 3 hours per day is a nice balance
• Hands on exercises

What could we have done better?

• More hands on exercises with GitHub Actions (i.e. instead of copy/paste code from exercise). Similar to OpenHack format.
• Valet is very cool, but we glanced over the content.

Ideas and suggestions?

• This bootcamp gave a nice baseline on capabilities. How do we get more training on each concept?
• Customer examples would be nice so we can see more advanced content such as use cases for Valet.

[ricardocovo]

What do we do well?

• Love the Labs. Great combination of presentation/labs

Ideas and suggestions?

• I want to keep going 😄 - Having other labs that we can continue post-Bootcamps would be great.

[rjayapra]

What do we do well?

Labs were planned and documented well
Hands on exercises and Valet was helpful

What could we have done better?

Instead of copy paste the content, an exercise to create actual workflows would create more impact

Ideas and suggestions?

Outline on setting up the organization, AD integration , some exercise on setting up Projects would be good too. Can include the part of disabling workflows in documentation.

[dkalmin]

The "Outline on setting up the organization, AD integration , some exercise on setting up Projects " is all done in the Overview bootcamp!

[iloveck]

What do we do well?
Excellent! Lots of insight and super supplement information, for my MIP "WorkshopPLUS - Secure DevOps: Application Security Principles and Practices - Closed Workshop" deliver to my customer.

What could we have done better?

advanced/ Deep topic sessions

Ideas and suggestions

GitHub is a strategic / prioritized product for my team (Customer Sucess - App Innovation), we are planning to develop GitHub Managed IP and delivering this year, not sure if any way the 2 teams can collaborate.

[PennStateLefty]

What do we do well?

Well delivered, and structured, 200 level content. I particularly appreciated David weaving in anecdotes from his experience on the subjects of CI/CD, how teams handle using issues, and where he sees the sharp edges of the migration tooling. That sort of content is invaluable when working with customers in the field where challenges rarely match lab conditions.

What could we have done better?

The GitHub Learning Path content is quite similar in depth but goes to a broader set of subjects. Perhaps Provide attendees with a list of those as next steps should they want to continue learning on a particular subject.

Ideas and suggestions?

The topics of Designing CI/CD with Actions and Migration would each make for a great standalone workshop if taken to a 400 level. I personally would find a workshop structured around a scenario to solve rather than pure step-by-step instruction to be incredibly valuable.