View organization page for GitHub

5,534,845 followers

Two Copilot tips to speed up your debugging: 1. Paste a screenshot of your error. 📸 2. Drag & drop files from anywhere (not just your project) to add context. 💡 Here are both in action. ▶️

Karl Wallenius

Software developer @ bba;

1d

Or you know, actually read the error messages, ponder about the implementation and learn something?

Ihor M.

Software Engineer

1d

Nice. The sooner AI will take over programmer, the big amount of job places will be in 5 years after 🤔😁

Aryan Ritwajeet Jha

PhD ECE (Power Systems) at Washington State University, Pullman

1d

If error is in a terminal session copilot ran it should probably be able to 'see' the error, but yes sometimes copy-pasting screenshots is necessary.

Like
Reply
Gabriel Gorta

JavaScript Developer - Svelte - VueJS - NodeJS - NoSQL

1d

You are absolutely right!

Like
Reply

Handy Copilot debugging hacks, pasting error screenshots and dragging files for extra context makes troubleshooting faster and more seamless!

Like
Reply
Andrew M. Ihnativ

I build secure data platforms, apps, and real-time dashboards with artful visualization. Full-stack: prototype → deployment; batch & streaming analytics, ML, agentic AI. And with full CI/CD.

17h

What's the link to the full episode?

Like
Reply
Juan Pablo Díaz Saba

Ingeniero Informatico | Desarrollo Rápido con IA | Soluciones Técnicas Especializadas & Adaptables

1d

I don't like debugging, thats why I developed flowtrace: https://github.com/Rixmerz/flowtrace-debugger

Like
Reply
Daniel Zhou

Software Development Director

1d

Love these practical tips! Context is everything when debugging, and Copilot makes it easier than ever to turn more information into actionable suggestions.

Like
Reply
Leon Whelan, BEng (Hons)

Founder and Aspiring Tier 1 SOC Analyst

23h

Just don't paste your secrets or .env files 👍

Like
Reply
See more comments

To view or add a comment, sign in

Explore content categories