<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>development on toorun.dev</title><link>https://toorun.dev/tags/development/</link><description>Recent content in development on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Copilot for Developers: Step-by-Step Approach Instead of Asking for Everything at Once</title><link>https://toorun.dev/posts/github-copilot-practical-guide/</link><pubDate>Sun, 31 May 2026 08:00:00 +0000</pubDate><guid>https://toorun.dev/posts/github-copilot-practical-guide/</guid><description>GitHub Copilot for Developers: A Step-by-Step Approach One of the tools I use daily and that has genuinely helped my productivity is GitHub Copilot. My company purchased accounts for our team, so we can use it in development. But through real experience, I&amp;rsquo;ve learned that using Copilot wisely is a skill in itself. This post is about that.
How I Use Copilot in Daily Development I mainly work in VS Code with Copilot active for tasks like:</description></item></channel></rss>