<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Corey Daley</title><link>https://coreydaley.dev/tags/productivity/</link><description>Recent content in Productivity on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Feb 2026 19:28:28 -0500</lastBuildDate><atom:link href="https://coreydaley.dev/tags/productivity/rss.xml" rel="self" type="application/rss+xml"/><item><title>Finding Each AI's Place in My Workflow</title><link>https://coreydaley.dev/posts/2026/02/finding-each-ais-place-in-my-workflow/</link><pubDate>Thu, 12 Feb 2026 19:28:28 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/finding-each-ais-place-in-my-workflow/</guid><description>&lt;p&gt;I&amp;rsquo;ve stopped trying to pick the &amp;lsquo;best&amp;rsquo; AI tool—instead, I&amp;rsquo;m letting each one find its place in my workflow. Here&amp;rsquo;s what&amp;rsquo;s emerged: Codex, Claude Code, and GitHub Copilot CLI handle my command-line coding from simple to complex. ChatGPT web is my go-to for image creation (oddly, ChatGPT Desktop lacks this). GitHub Copilot in VSCode crushes code completion. Claude Code and Claude Desktop excel at blog writing with Notion integration.&lt;/p&gt;
&lt;p&gt;Each tool has found its niche, and I&amp;rsquo;m more productive because of it. I&amp;rsquo;m still exploring how to use AI as a peer for bouncing ideas off, especially in planning mode.&lt;/p&gt;
&lt;p&gt;The future isn&amp;rsquo;t about one AI to rule them all—it&amp;rsquo;s about orchestrating multiple specialists. How are you integrating AI tools into your workflow? Have you found similar specialization patterns, or are you using a different approach?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/finding-each-ais-place-in-my-workflow/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/finding-each-ais-place-in-my-workflow/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Automate Your Blog with Notion and AI: A Self-Demonstrating Workflow</title><link>https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/</link><pubDate>Tue, 10 Feb 2026 21:41:59 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/</guid><description>&lt;p&gt;This post you&amp;rsquo;re reading right now? It was created by an AI reading a to-do item from my Notion database. That&amp;rsquo;s the power of combining Notion with AI assistants. The problem every blogger faces: brilliant ideas die in the gap between inspiration and execution.&lt;/p&gt;
&lt;p&gt;My solution: a Notion to-do list where I capture ideas, and AI assistants (Claude Code and ChatGPT) read from it via Model Context Protocol, generate complete posts, publish them to my Hugo blog, and mark the to-dos complete. It&amp;rsquo;s self-demonstrating—this very post was created that way. The workflow transforms content creation from manual drudgery into an automated pipeline.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re drowning in blog ideas but low on execution energy, this might be your answer. Are you using Notion for content management? Have you explored AI integrations for your blog?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>The Art of Iterative Cycles with AI: Why Your First Prompt is Never Your Best</title><link>https://coreydaley.dev/posts/2026/02/iterative-cycles-with-ai/</link><pubDate>Wed, 04 Feb 2026 19:50:00 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/iterative-cycles-with-ai/</guid><description>&lt;p&gt;Here&amp;rsquo;s something I&amp;rsquo;ve learned about AI coding assistants: the first response is rarely perfect—and that&amp;rsquo;s actually a good thing. When I started using GitHub Copilot and Claude, I expected instant perfect code. Reality? AI interprets your instructions based on patterns and context, so the first attempt is often close but not quite right.&lt;/p&gt;
&lt;p&gt;The key is treating AI like a junior developer: start with clear instructions, review the result, provide feedback, and iterate. Each cycle gets closer to what you need. This isn&amp;rsquo;t a limitation—it&amp;rsquo;s how effective collaboration works.&lt;/p&gt;
&lt;p&gt;The developers who succeed with AI aren&amp;rsquo;t the ones with perfect prompts; they&amp;rsquo;re the ones who embrace refinement. Have you experienced this iterative dance with AI tools? How many rounds does it usually take you to get the result you want?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/iterative-cycles-with-ai/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/iterative-cycles-with-ai/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Managing Blog Posts with GitHub Copilot</title><link>https://coreydaley.dev/posts/2026/02/managing-blog-posts-with-github-copilot/</link><pubDate>Wed, 04 Feb 2026 16:25:00 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/managing-blog-posts-with-github-copilot/</guid><description>&lt;p&gt;Managing a blog used to mean juggling multiple tools—notes apps for ideas, editors for drafting, task trackers for progress. It was fragmented and exhausting. Then I discovered GitHub Copilot can work directly with GitHub Issues and Projects, creating a seamless workflow.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s how it works: I create issues for blog post ideas, GitHub Copilot reads the issue, generates the complete post with proper frontmatter and content, and automatically closes the issue when I publish. No context switching, no lost ideas, just a smooth pipeline from concept to publication. The best part? Everything lives in one place alongside my code.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re blogging and using GitHub, this workflow is a game-changer. How are you managing your content pipeline? Have you tried integrating your blog workflow with your code repository?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/managing-blog-posts-with-github-copilot/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/managing-blog-posts-with-github-copilot/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>How GitKraken Simplified My Git Workflows and Boosted Productivity</title><link>https://coreydaley.dev/posts/2026/02/gitkraken-simplified-git-workflows/</link><pubDate>Wed, 04 Feb 2026 12:05:00 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/gitkraken-simplified-git-workflows/</guid><description>&lt;p&gt;Git is powerful but complex—until you add GitKraken. After years of command-line Git, switching to GitKraken completely transformed how I work. The interactive commit graph alone is worth it: complex branch structures become instantly clear, and you can navigate your entire repository history with simple clicks.&lt;/p&gt;
&lt;p&gt;But it&amp;rsquo;s not just pretty visualization. GitKraken&amp;rsquo;s merge conflict resolution is intuitive, the built-in code review tools streamline collaboration, and integrations with GitHub, GitLab, and Bitbucket make everything seamless.&lt;/p&gt;
&lt;p&gt;Whether you&amp;rsquo;re a Git beginner finding your footing or a pro looking to boost productivity, GitKraken removes the intimidation factor and makes version control visual and accessible. Have you tried visual Git clients? What&amp;rsquo;s been your experience with GitKraken or similar tools?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/gitkraken-simplified-git-workflows/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/gitkraken-simplified-git-workflows/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Building with AI: Copilot and Claude</title><link>https://coreydaley.dev/posts/2026/02/building-with-ai-copilot-and-claude/</link><pubDate>Tue, 03 Feb 2026 21:02:25 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/building-with-ai-copilot-and-claude/</guid><description>&lt;p&gt;Building websites has changed dramatically—I&amp;rsquo;m no longer staring at code for hours. Instead, I&amp;rsquo;m collaborating with Claude and GitHub Copilot to build this Hugo blog. Here&amp;rsquo;s what I&amp;rsquo;ve learned: Claude is my architect. When I need structural changes or new layouts, Claude generates complete solutions and explains every decision.&lt;/p&gt;
&lt;p&gt;GitHub Copilot is my coding assistant, finishing my thoughts as I type and handling routine tasks. Together, they create a powerful workflow where Claude handles the big picture and Copilot speeds up execution. The result? I spend less time debugging and more time creating.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re curious about AI-assisted development or wondering which tool does what, this post breaks down how they complement each other. Are you using AI tools in your workflow? How do you divide the work?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/building-with-ai-copilot-and-claude/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/building-with-ai-copilot-and-claude/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>