<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vscode on Mat&#39;s Mind Dump</title>
    <link>https://mathieson.github.io/blog/tags/vscode/</link>
    <description>Recent content in Vscode on Mat&#39;s Mind Dump</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://mathieson.github.io/blog/tags/vscode/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Switching from PyCharm to VS Code for Maya Development</title>
      <link>https://mathieson.github.io/blog/posts/switching-from-pycharm-to-vscode-for-maya-development/</link>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://mathieson.github.io/blog/posts/switching-from-pycharm-to-vscode-for-maya-development/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been around here before, you might have seen my post on &lt;a href=&#34;https://mathieson.github.io/blog/posts/the-best-pycharm-mayapy-interpreter-setup/&#34;&gt;setting up PyCharm for Maya Python development&lt;/a&gt;. It&amp;rsquo;s been one of my more practical posts, and for a long time it reflected how I actually worked. PyCharm was my IDE of choice for Maya scripting, and I didn&amp;rsquo;t have much reason to look elsewhere.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;d tried VS Code over the years and never really landed on it. Getting it properly configured for Maya — pointing it at the right interpreter, getting reasonable autocomplete — always felt like more friction than it was worth. PyCharm just worked, and once you had a good setup going, it was hard to argue with.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
