A Practical Developer Environment Setup 2026 Guide

Most 'developer environment setup 2026' advice is Mac-only. Luiz Carlos's setup from Full Cycle treats Linux, Mac and Windows as first-class targets, and his Windows path runs Linux tooling inside WSL2 with Docker Desktop on top. Here is the complete toolkit, pillar by pillar.

What Are the Three Pillars of a Productive Dev Environment?

A productive dev environment in 2026 rests on three pillars: a modern terminal, Docker for containers, and a well-configured IDE. The Full Cycle guide applies all three to Linux, Mac and Windows, and Luiz Carlos argues that skipping any one of them caps your day-to-day speed regardless of your stack. Each pillar is deliberately simple:

• Modern terminal: tabs, custom shells, plugins, themes, smart navigation and, optionally, AI integration that turns a plain-language request into a runnable command.
• Docker and containers: containers are unavoidable in modern backend work, so running them should be frictionless from the terminal or IDE.
• Configured IDE: installing VS Code alone is not enough. Settings, extensions and integrated terminal tooling are where the productivity gain lives.

The video also plugs Full Cycle's own training material, timed to its Black Friday week: three standing tutorials (WSL, productive environment configuration, and VS Code settings) plus a new MBA in AI-driven software engineering.

Which Terminal Should You Use on Linux and Mac?

On Linux, Luiz Carlos recommends WezTerm, a terminal written in Rust with multiplexing and GPU acceleration, two criteria he treats as non-negotiable for any modern terminal choice. On Mac, he sticks with iTerm2, a long-standing macOS terminal that now supports AI plugin integration, with WezTerm as a cross-platform alternative.

Both choices reflect the same logic: the default terminal that ships with your distribution or with macOS works, but it is a traditional terminal. Modern options add tabs, shells, autocompletion and AI hooks. Here is how the terminals in the video compare:

Terminal	Platforms	AI integration	Notes
WezTerm	Linux, Mac, Windows	None built in	Rust, GPU acceleration, multiplexing
iTerm2	Mac	Via AI plugin	Traditional but modern, long-standing favorite
Warp	Linux, Mac, Windows	Built in, most mature	Mandatory login, credit-based pricing
Windows Terminal Canary	Windows	Terminal Chat (GitHub Copilot)	First to receive new features
Default terminals (GNOME Terminal, etc.)	Linux	None	Traditional; no tabs plugins or AI

If you want the most AI-focused terminal available today, the video points to Warp, which Luiz Carlos describes as the most mature AI terminal even though he personally dislikes its mandatory login and its credit-based pricing, roughly 150 free AI credits with paid tiers renewing 1,500 credits per month.

For a free, flexible middle ground, the video names two shell-agnostic AI options: Shell GPT, which works in fish, bash or any shell with an OpenAI API key, and fish-ai, a fish plugin that needs an LLM API key.

How Do You Set Up Windows for Development in 2026?

Windows setup takes the longest section of the video because Windows historically shipped shells (DOS, PowerShell) rather than terminals. The recommended path has four moves, in order:

1. Install Windows Terminal, open sourced on GitHub in 2020, and pick the Canary build.
2. Install WSL2 with Ubuntu and move your toolchain into it.
3. Install Docker Desktop on top of WSL2.
4. Add PowerToys for window management and utilities.

Windows Terminal and Terminal Chat

Luiz Carlos has used Windows Terminal since its 2020 launch. The Microsoft Store carries three variants: the stable release, a Preview build that anticipates the next version, and a Canary build that receives features first. He uses Canary daily and reports it as stable in practice.

Windows Terminal Canary ships with Terminal Chat, described in the video as GitHub Copilot running inside the terminal, letting you ask about commands and insert them directly. That feature has not yet reached the stable release.

WSL2 as the real development environment

Rather than installing Node, PHP or Python natively on Windows, the video recommends running your entire Linux toolchain inside WSL2, the Windows Subsystem for Linux, with Ubuntu as the example distribution. Full Cycle maintains a WSL tutorial that the video calls the best WSL material on the internet; its GitHub repository sat at 4,400 stars when the video was recorded. The rule of thumb: unless your stack is Microsoft-native, treat Windows as the host and Linux as the workspace, opening projects through the VS Code WSL integration described below.

PowerToys utilities

PowerToys began life with Windows 95 and returned with Windows 10; it ships on Windows 11 too. Luiz Carlos enables only a handful of modules at a time: FancyZones for window regions, Text Extractor, Image Resizer, Color Picker, environment variable editing and Always on Top. Enabling everything keeps background processes running, so he toggles modules like the hosts-file editor only when needed.

Why Docker Desktop Instead of Docker Engine?

On all three operating systems, the video recommends Docker Desktop over a bare Docker Engine install. The reasoning is strongest on Linux, where Docker Engine originated: Docker Desktop isolates containers in a separate VM, so a broken environment means deleting and recreating the VM rather than repairing your host machine. Docker Engine, the video argues, was not built with development workflows in mind, and problems it causes on the host tend to resurface over time. Docker Desktop also adds visual container management, extra security isolation, and AI and MCP-related features for running models.

On Mac, everything runs through a VM regardless of the tool, and the video credits Docker with investing heavily in VM input/output performance in recent years, recommending the Apple Silicon or Intel build for your processor. The one caveat is resource consumption: Docker Desktop uses more memory and CPU than a leaner setup, so check that your machine can support it.

Which Shell and CLI Tools Speed Up Daily Work?

A terminal is only a shell aggregator, so the shell matters as much as the terminal. Luiz Carlos switched to fish, now built in Rust after its 2025 rewrite, replacing zsh, which he used for years but found degrading in performance over time inside WSL2 and VS Code. Fish ships smart history search, tab autocomplete and Git-aware prompts out of the box, features that zsh requires third-party configuration to match. His prompt theme is Starship, restyled minimal: pink directory, most modules disabled.

The Rust-built CLI layer includes four tools:

• eza, a modern ls replacement with colors and icons. He maps it to custom aliases like lz rather than overwriting ls itself, because AI agents such as GitHub Copilot or Claude Code expect standard ls output to parse correctly.
• zoxide, a smarter cd that indexes visited folders, so typing z plus a fragment jumps to the best-ranked match. He keeps the real cd for in-project navigation and uses z to open whole projects.
• fzf, a fuzzy finder that adds file trees with previews via Ctrl+T and command history search inside fish.
• Neovim, the Vim fork with syntax highlighting for Markdown, JavaScript, TypeScript and Go through language servers, which he finds far faster for quick file edits than stock vim or nano.

How Do You Manage Multiple Language Versions Safely?

Running Python 2 alongside Python 3, or Java 11 and Java 21, on one machine is a common pain point. Luiz Carlos previously recommended asdf but moved to mise, which he describes as doing the same job, faster, with fewer security concerns about installing third-party plugins. Mise installs and switches runtimes per project or globally, and remains compatible with existing asdf setups.

The upgrade motive is specific: the video argues that asdf can open security gaps depending on what you install, which is a speaker assessment rather than an independently verified finding. If you rely on asdf today, test mise's compatibility before migrating your project files.

Which VS Code Settings and Extensions Matter Most?

Luiz Carlos has maintained a public VS Code configuration for over four years and overhauled it in late 2025. His first recommendation is the VS Code Insiders build, which receives daily updates; he reports eight months of use with only a handful of critical bugs, in exchange for first access to new GitHub Copilot features. Configuration basics include the GitHub Dark Default theme and the JetBrains Mono font, plus wiring your fish shell into the integrated terminal.

Of the 94 extensions in his shared list, the ones he calls stack-independent are:

• GitHub Copilot: he keeps it alongside Claude Code as a fallback or primary assistant, and notes the separate GitHub Copilot extension was slated for deprecation in early 2026, with the Chat extension absorbing everything.
• Code Spell Checker: catches typos in variable names and comments, with a Portuguese add-on for non-English speakers.
• GitHub Pull Requests and GitHub Actions: manage reviews, issues and workflow runs from the IDE.
• REST Client: replaces Postman for simple API calls committed as .http files in version control, with support for variables holding sensitive credentials.
• WSL: required on Windows so VS Code opens projects inside WSL2 correctly, with extensions installed on the Linux side.
• Docker DX: Docker's own extension, which he recommends replacing Microsoft's older Docker extension with, citing its Dockerfile debugging and up-to-date Compose support; he adds Dev Containers for running VS Code inside a container.
• Peacock: colors the editor border per project or technology, so a Go project and a React project are distinguishable at a glance.

Beyond extensions, his settings file covers inlay hints that reveal variable types at a keystroke, font sizing, and GitHub Copilot tuning. Many of those options only activate on Insiders, but they are safe to paste into stable VS Code.

FAQ: What Else Do Readers Ask About This Setup?

Is this developer environment setup 2026 free?

Yes for the core stack. WezTerm, iTerm2, fish, eza, zoxide, fzf, Neovim, mise, WSL2 and PowerToys are free. Warp has a free tier, and Docker Desktop is free for personal use under Docker's current licensing terms.

Do I need WSL2 if I develop on Windows?

The video's position is yes for most stacks: run your Linux toolchain inside WSL2 and open projects through the VS Code WSL extension. Native Windows development remains reasonable only for Microsoft-centric stacks.

Why fish over zsh?

Fish delivers history search, autocomplete and Git-aware prompts with zero configuration, and its 2025 Rust rewrite removed the performance degradation the speaker experienced with zsh under WSL2. Fish is not POSIX-compatible, so some bash scripts need adjustment.

Can I replace cd with zoxide's z command?

The video advises against it: keep cd for navigating inside a project and use z to jump between projects, because AI agents and your own muscle memory still expect standard command behavior.

Should I use VS Code Insiders?

The speaker has run Insiders for eight months with few critical bugs and gets AI features first. Settings meant for Insiders are safe to paste into stable VS Code; unsupported options simply stay disabled.

How Do You Turn Your Own Setup Walkthrough Into an Article?

Every tool in this article earned its place by solving a real daily friction: slow shells, missing autocomplete, version chaos, lost project folders. If you have recorded your own environment walkthrough, an interview about your workflow, or a lesson that only lives inside a YouTube video, that same friction applies to your audience finding it in written form.

Skala Blog turns a YouTube video into a publishable article: paste the URL, the video is transcribed, and you get a structured draft you can edit and post. If your dev setup content deserves a written home next to your repository, that is the shortest path.

Source video