greenyouse

Heya HN!

I'm exploring ways to integrate GitHub Copilot more effectively into my daily development work across different domains: web, backend, and mobile app development. My idea is to create a "prompt book" for each domain, containing common tasks and queries. This would allow me to quickly use Copilot to generate detailed code snippets based on a curated list of prompts tailored to the task at hand.

As an example Copilot for security has a prompt book pre-built by MS for security tasks: https://learn.microsoft.com/en-us/security-copilot/using-promptbooks

In the domain of backend programming this could help with:

  - stub code for endpoints
  - stub code for common file types
  - stub code for types of integration and unit testing
  - answer common questions like whether an API change is breaking
  - give tips on common logging and error handling cases

It's all meant to help speed up development but a strong understanding of the material is still required to avoid wonkiness.

I'm curious to know if anyone in the community has experience creating or using prompt books with Copilot. Are there existing resources out there, or has anyone found this approach beneficial for their development workflow? Any insights, examples, or resources you could share would be greatly appreciated. :D

What books/talks/articles did you love having learned from before doing a big legacy migration?

I'm looking for any good material on upgrading legacy systems from both an engineering and product management point of view. War stories are also welcome since they're fun to hear. Thanks for any help!