<?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>Development on Technical Notes</title><link>http://luispa.com/en/tags/development/</link><description>Recent content in Development on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sun, 03 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>A Decent Windows</title><link>http://luispa.com/en/posts/2025-08-03-win-decente/</link><pubDate>Sun, 03 Aug 2025 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2025-08-03-win-decente/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-win-decente.svg" alt="linux development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>This post is about deflating, removing what I personally believe is unnecessary in Windows 11. In English they call it &lt;em>debloat&lt;/em> or &lt;em>bloatware&lt;/em> removal. In this post I explain how to do it on a fresh Windows install, but it also works on an existing one.&lt;/p>
&lt;p>The point is to remove apps, services and pre-installed junk that aren&amp;rsquo;t essential, consume resources and worst of all, affect performance and UX.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><item><title>VMWare on Windows</title><link>http://luispa.com/en/posts/2024-08-26-win-vmware/</link><pubDate>Mon, 26 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-26-win-vmware/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-vmware-vm.svg" alt="vmware win logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>Virtualization allows running multiple operating systems on the same machine without making changes to the main disk. In this post I show how I install &lt;strong>VMWare Workstation Pro&lt;/strong> as a host on a Windows 11 Pro and how I create a Windows 11 Pro Guest without TPM 2.0, for the purpose of having an isolated development environment.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><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>A Decent Windows (Obsolete)</title><link>http://luispa.com/en/posts/2024-08-24-win-decente-obsoleto/</link><pubDate>Sat, 24 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-24-win-decente-obsoleto/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-windows.svg" alt="windows logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I explain how I configure a Windows 11 that I&amp;rsquo;m going to use for software development, testing or demos. I don&amp;rsquo;t need frills since it won&amp;rsquo;t have sensitive data, I want its essence, bare-bones, with few applications, some browsing and that&amp;rsquo;s it. In the end it became a technical exercise &amp;ndash; removing everything I can, ads, Edge, extras, installing minimal drivers, a local account, having it boot and be available as soon as possible.&lt;/p>
&lt;p>Note: a year later I decided to create a new &lt;a href="http://luispa.com/en/posts/2025-08-03-win-decente/">decent Windows 11&lt;/a> (2025).&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><item><title>Dualboot Linux Windows</title><link>http://luispa.com/en/posts/2024-08-23-dual-linux-win/</link><pubDate>Fri, 23 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-23-dual-linux-win/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-dual-boot.svg" alt="dualboot logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>Dualboot means having two operating systems on the same computer and choosing which one to boot during the boot phase. My goal is to prepare my PC for dualboot and install Windows 11 Pro. Normally you install Windows first and then Linux, but in my case I already have Linux (Ubuntu) working perfectly and using the entire 4TB disk.&lt;/p>
&lt;p>I&amp;rsquo;m going to &amp;ldquo;add&amp;rdquo; Windows to enable dualboot. I describe the entire process, how I did it, how I resized the hard drive, added Windows and customized the boot menu.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><item><title>Linux for Development</title><link>http://luispa.com/en/posts/2024-07-25-linux-desarrollo/</link><pubDate>Thu, 25 Jul 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-07-25-linux-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-linux-desarrollo.svg" alt="linux development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe my configuration log for setting up a Linux (Ubuntu) machine as a development workstation. I install several graphical and command-line applications that are essential for my workflow.&lt;/p>
&lt;p>Starting from a fresh Ubuntu installation, the installation order can be varied, but I recommend (if your Ubuntu is freshly installed) that you follow the same order to see the same results.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Terminals with tmux</title><link>http://luispa.com/en/posts/2024-04-25-tmux/</link><pubDate>Thu, 25 Apr 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-04-25-tmux/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-tmux.svg" alt="tmux logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://github.com/tmux/tmux/wiki">&lt;code>tmux&lt;/code>&lt;/a> is a terminal multiplexer that allows you to have multiple sessions (shells) in a single window. From your Mac, Linux, or even Windows (with WSL) terminal, in a single window you can have multiple active sessions, switch between them, view them simultaneously, enter one and disconnect (they keep running in the background), and reconnect to it in the future.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Goodbye Bash, Hello Zsh!</title><link>http://luispa.com/en/posts/2024-04-23-zsh/</link><pubDate>Tue, 23 Apr 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-04-23-zsh/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-zsh.svg" alt="zsh logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>I&amp;rsquo;ve decided to migrate my CLI from the reliable and well-known &lt;em>&lt;code>bash&lt;/code>&lt;/em> to the powerful and versatile &lt;em>&lt;code>zsh&lt;/code>&lt;/em>. It&amp;rsquo;s an extended evolution of the Bourne Shell (sh) &amp;ndash; it not only inherits many of Bash&amp;rsquo;s familiar features but also introduces a series of new functionalities, plugin support, and custom themes. Apple adopted Zsh as the default shell some time ago, and I still needed to make the switch on my Linux systems, including WSL2 on Windows.&lt;/p>
&lt;br clear="left"/></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><item><title>MAC with Vagrant</title><link>http://luispa.com/en/posts/2023-04-23-mac-vagrant/</link><pubDate>Sun, 23 Apr 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-04-23-mac-vagrant/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-mac-vagrant.svg" alt="vagrant kvm logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://www.vagrantup.com/">Vagrant&lt;/a> lets you create and configure virtual development environments that are lightweight and reproducible. It does so by creating virtual machines and requires a &lt;strong>Hypervisor&lt;/strong>. It doesn&amp;rsquo;t care which hypervisor you use &amp;ndash; it supports VirtualBox, KVM, Docker, VMWare, and &lt;a href="https://github.com/hashicorp/vagrant/wiki/Available-Vagrant-Plugins#providers">30+ others&lt;/a>. It&amp;rsquo;s a fantastic tool for spinning up &lt;strong>Servers&lt;/strong> for our software development projects.&lt;/p>
&lt;p>This guide only works, for now, with &lt;strong>INTEL&lt;/strong> chips. I haven&amp;rsquo;t been able to make it work on a Mac with ARM (Apple Silicon) as the host yet.&lt;/p>
&lt;br clear="left"/></description></item><item><title>MAC for Development</title><link>http://luispa.com/en/posts/2023-04-15-mac-desarrollo/</link><pubDate>Sat, 15 Apr 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-04-15-mac-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-mac-desarrollo.svg" alt="mac development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe my configuration log for setting up a Mac (INTEL or ARM) as a development machine. I install several graphical and command-line applications that are important for using a Mac as a development workstation.&lt;/p>
&lt;p>The installation order can be varied, but this is what I recommend starting from a fresh macOS installation.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Vagrant with Libvirt KVM</title><link>http://luispa.com/en/posts/2021-05-15-vagrant-kvm/</link><pubDate>Sat, 15 May 2021 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2021-05-15-vagrant-kvm/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-vagrantkvm.svg" alt="vagrant kvm logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://www.vagrantup.com/">Vagrant&lt;/a> creates and runs virtual machines, relying on virtualization providers such as Virtualbox, KVM, Docker, VMWare, and &lt;a href="https://github.com/hashicorp/vagrant/wiki/Available-Vagrant-Plugins#providers">30+ others&lt;/a>. It will always default to launching the VM with Virtualbox unless we explicitly specify a different provider. In this guide I explain how I set up &lt;strong>Vagrant with the Libvirt KVM provider on Linux&lt;/strong>.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>