The Terminal Made Me a Better Developer (And Not for the Reasons I Expected)

Description and use

Using the terminal shifted the author from GUI‑centric workflows to a deeper, investigative approach, enhancing understanding of filesystem structure, process management, permissions, networking, and error interpretation.

Problem

Developers often rely on graphical interfaces and click‑through workflows, which can obscure underlying system behavior and hinder deep understanding of processes, files, permissions, and networking.

Outcome

The terminal transformed the author's development workflow from reactive clicking to proactive investigation, improving problem‑solving efficiency and system comprehension.

Workflow

• Use pwd, ls -la, find to understand project layout
• Use ps aux, pgrep -af node, ss -ltnp to locate running processes and listening ports
• Use ls -l, stat to inspect file permissions and ownership
• Use dig, curl -I, ss -ltn to diagnose networking issues
• Read and interpret error outputs from compilers, servers, and tools

Evidence

I started paying more attention to hidden files, symbolic links, absolute versus relative paths, and where applications store their configuration.

Source

I started learning how to see what was actually running.

Source

I could check who owned the file and what permissions it had.

Source

The terminal gave me a way to start narrowing those things down.

Source