Many of us do the vibe coding these days, and GitHub Copilot (GHCP) takes the key role of the vibe coding. You might simply enter prompts to GHCP like "Build a frontend app for a marketplace of camping gear" or even simpler ones like "Give me an app for camping gear marketplace". This surely works. GHCP delivers an app for you. However, the deliverable might be different from what you initially expected. This happens because GHCP fills in uncertainties with its own imagination unless we provide clear and detailed prompts.

Let's recall the basics of product lifecycle management (PLM). You're a product owner or product manager about to launch a new product or develop a new business to sell values to your prospective customers. Where would you start from? Yes, it's the fist step to perform market analysis – whether your idea is feasible or not, whether the market is profitable or not, and so on. Then, based on this analysis, you would generate a product requirements document (PRD). The PRD describes what the product or service should be look like, how it should work, what it should deliver. In addition to that, the doc should also contain user stories and acceptance criteria. The user stories define what the app should expect, how it should behave, and what it should return. The acceptance criteria defines how you test the app to accept as a final deliverable.

So, is a PRD is important for vibe coding? YES, IT IS! As stated earlier, GHCP tries really hard to fill some missing parts with its full of imagination. Therefore, the more context you provide to GHCP, the better GHCP works more accurately. That's how you get more accurate results from the vibe coding. But how do you actually practise this type of vibe coding?

Introducing GitHub Copilot Vibe Coding Workshop

I'm more than happy to introduce this GitHub Copilot Vibe Coding Workshop, a resource available for everyone to use. It's based on a typical app development scenario – building a web application that consists of a frontend UI and backend API with database transaction. This workshop has six steps:

1. Analyse a PRD and generate an OpenAPI document from it.
2. Build a FastAPI app in Python based on the OpenAPI doc.
3. Build a React app in JavaScript based on the OpenAPI doc.
4. Migrate the FastAPI app to Spring Boot app in Java.
5. Migrate the React app to Blazor app in .NET.
6. Containerise both the Spring app and the Blazor app, and orchestrate them.

This workshop is self-paced so you can complete it in your spare time. It's also designed to run on GitHub Codespaces, since not everyone has all the required development environment set up locally.

Throughout this workshop, you'll learn:

• How to activate GHCP Agent Mode on VS Code,
• How to customise your GHCP to get the better result, and
• How to integrate MCP servers for vibe coding.

Do you prefer a language other than English? No problem! This workshop provides materials in seven different languages including English, Chinese (Simplified), French, Japanese, Korean, Portuguese and Spanish so you can choose your preferred language to complete the workshop.

It's your time for vibe coding!

Now it's your turn to try this GitHub Copilot Vibe Coding Workshop on your own, or together with your friends and colleagues. If you have any questions about this workshop, please create an issue in the repository!

Want to know more about GitHub Copilot?

• GitHub Copilot in VS Code
• GitHub Copilot Agent Mode
• GitHub Copilot Customisation
• MCP Server Support in VS Code

This episode discusses why perfection is a dangerous and fragile goal, explaining how striving for 100% leads to unsustainable outlier states. It highlights how setting perfection as a bar can cause commitments to break and plans to fail due to a lack of slack, and offers strategies like building redundancy and planning with slack to achieve goals more effectively without relying on perfection.

• Uncover why perfection is a dangerous and fragile goal, as it often requires exorbitant, unsustainable effort and creates outlier states that are unlikely to be maintained, referencing the "Wedies effect" where things tend to regress to the mean.
• Learn how planning for 100% utilisation or setting perfection as a commitment can lead to fragility, causing plans to fail when unexpected changes occur or leading to giving up altogether once a "perfect" streak is broken.
• Discover practical strategies to avoid fragile perfectionism, such as planning with slack to accommodate change and building redundancy into your systems and personal commitments for more robust outcomes.
• Explore why actively avoiding requirements or expectations of perfection is crucial, as investing in it can be an exponential or even asymptotic step, leading to an unsustainable and fragile state.

Note: sorry about the plane noise in the background. I decided to publish it, since it's imperfect (and that's kind of making the point!).

📮 Ask a Question

If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.

📮 Join the Discord

If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!

🧡 Leave a Review

If you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.