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

Description and use

Using the terminal enabled the developer to gain a deeper understanding of the filesystem, processes, permissions, and networking, improving diagnostic skills and fostering a systematic problem‑solving approach.

Problem

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

Outcome

The developer gained deeper system knowledge, improved troubleshooting skills, and a more analytical approach to problem‑solving by routinely using terminal commands.

Workflow

• 1. Open terminal in project directory and run pwd, ls -la, find . -maxdepth 2 -type f to understand current location and file visibility.
• 2. Start a development server, then use pgrep -af node and ss -ltnp to locate the process and its listening port.
• 3. Inspect file permissions with ls -l <file> and stat <file> to see ownership and mode bits.
• 4. Perform network diagnostics with dig <host>, curl -I https://<host>, and ss -ltn to verify DNS resolution, HTTP response, and local listening sockets.
• 5. Read and analyze error outputs from compilers, dependency managers, and servers, focusing on specific messages rather than generic fixes.

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

I started reading what my tools are telling me.

Source