<?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>Visual on Technical Notes</title><link>http://luispa.com/en/tags/visual/</link><description>Recent content in Visual on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sun, 25 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/visual/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows for Development</title><link>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</link><pubDate>Sun, 25 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-win-desarrollo.svg" alt="Windows for development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe the steps to set up a Windows 11 machine as a development workstation for a cross-platform environment — Linux, macOS, and Windows. This is not oriented towards &lt;em>Microsoft/Windows-only&lt;/em> software development, but rather for those who like to develop on and for multiple platforms and environments.&lt;/p>
&lt;p>I start from a clean Windows installation (in English), with nothing installed. I took advantage of needing to set up a &lt;a href="http://luispa.com/en/posts/2024-08-23-dual-linux-win/">dual boot&lt;/a> and configured the operating system in a &lt;a href="http://luispa.com/en/posts/2024-08-24-win-decente-obsoleto/">lightweight&lt;/a> manner. The post starts with the CLI and WSL2, and in the second part I cover the tools and programming languages.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><item><title>Customizing VSCode</title><link>http://luispa.com/en/posts/2023-06-20-vscode/</link><pubDate>Tue, 20 Jun 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-06-20-vscode/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-vscode.svg" alt="vscode logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I cover how to customize VSCode. I work with GitHub in a cross-platform, multi-account environment and want to sync my settings, use the same extensions, and leverage licenses. I explain the multi-account topic, synchronization of my global and per-project preferences (settings), and extensions.&lt;/p>
&lt;p>I normally use Windows, Linux, and macOS, and I&amp;rsquo;ve chosen VSCode as my editor/IDE. The goal is to have a unified work experience &amp;ndash; launch VSCode on any operating system, clone a personal or professional project, keeping the same extensions and settings, and even using the options to connect to a host, tunnel, WSL, etc.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>