<?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 Some Guys Blog</title><link>https://someguys.blog/tags/vscode/</link><description>Recent content in Vscode on Some Guys Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 20 Jun 2026 22:21:29 -0500</lastBuildDate><atom:link href="https://someguys.blog/tags/vscode/index.xml" rel="self" type="application/rss+xml"/><item><title>A real editor: VS Code for Python</title><link>https://someguys.blog/posts/2026-06-21-a-real-editor-vs-code-for-python/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://someguys.blog/posts/2026-06-21-a-real-editor-vs-code-for-python/</guid><description>&lt;p&gt;So far in this series we set up &lt;a href="https://someguys.blog/posts/2026-06-19-setting-up-a-mac-for-python/"&gt;the terminal and Homebrew&lt;/a&gt;
, then &lt;a href="https://someguys.blog/posts/2026-06-20-installing-python-without-touching-the-system-python/"&gt;installed Python with asdf and gave each project its own virtual environment&lt;/a&gt;
. Now we need a place to actually write code. This is the one area where the book and I mostly agree, so this post is less about replacing its advice and more about finishing the job it starts.&lt;/p&gt;</description></item></channel></rss>