Command Line Interfaces

Command-line interfaces remain essential tools for developers, enabling automation, scripting, and efficient interaction with development tools, cloud services, and build systems. This collection explores CLI tools, techniques, and productivity strategies for modern software development workflows.

CLI in Modern Development

Effective CLI usage accelerates development through automation, reproducible workflows, and integration with CI/CD pipelines. Whether using PowerShell, Bash, or specialized CLIs like the .NET CLI, Azure CLI, or kubectl, mastering command-line tools reduces manual overhead and enables scriptable, repeatable processes.

.NET CLI provides comprehensive project scaffolding, package management, build orchestration, and testing capabilities. Modern .NET development relies heavily on CLI-driven workflows that integrate seamlessly into automated pipelines.

Cloud CLIs (Azure CLI, AWS CLI) enable infrastructure management, resource provisioning, and deployment automation through command-line interfaces that support both interactive and scripted use.

Productivity and Automation

Articles in this section cover shell customization, command-line productivity tools, scripting patterns, and integration of CLI tools into development workflows. Topics include tab completion configuration, command history optimization, and building reusable scripts for common development tasks.

The goal is leveraging CLI tools for speed, automation, and scriptable workflows that eliminate repetitive manual tasks.

.NET CLI 10 – Microsoft Finally Realizes DevOps Exists

The .NET CLI? Reliable. Boring. You run dotnet build, dotnet test, dotnet publish, done. Real DevOps work happens in Dockerfiles, CI/CD configs, and specialized tools. The CLI does its job but was never built for actual operational workflows.

.NET 10 changes this. Four additions that sound minor but fix real problems I’ve hit in production pipelines for years: native container publishing, ephemeral tool execution, better cross-platform packaging, and machine-readable schemas. Not flashy. Not keynote material. But they’re the kind of improvements that save hours every week once you’re running them at scale.

Will they replace your current workflow? Depends on what you’re building. Let’s look at what actually changed.

Stop Typing: The .NET CLI Tab Completion You've Been Missing

One command to transform your .NET CLI workflow—tab completion so responsive you’ll wonder how you survived without it Finally, a productivity boost that’s actually worth your time