The Practical Developer

Introduction Every README on GitHub, every post on Dev.to and Hashnode (the platforms this blog distributes to), and most technical documentation is written in Markdown: plain text with a few simple marks for formatting. It was designed to be readable as-is — even before conversion — and to convert cleanly into HTML, PDF, slides, and more. If you write anything technical, Markdown is the format to learn first. The syntax in one minute Markdown's core is small enough to learn in a sitting: # Heading 1 ## Heading 2 **bold text** and *italic text* - A bullet list item - Another item 1. A numbered item 2. Another numbered item [link text](https://example.com) `inline code` and a fenced code block (shown in the draft file as a nested example) ``` a fenced code block ``` Headings, emphasis, lists, links, and code cover the vast majority of documents. Tables, images, and blockquotes extend it slightly, and "flavours" (GitHub Flavoured Markdown being the standard) add convenience...

Introduction You may never have installed Linux on your own computer, but you use it constantly: it runs most of the world's servers (including the ones serving this blog), every Android phone, and all of the top 500 supercomputers. Linux is not a company product — it is a kernel, created by Linus Torvalds in 1991, around which an entire ecosystem of free, open-source operating systems grew. Kernel vs distribution: the key distinction Beginners confuse two things. The kernel is the core program that talks to hardware — CPU, memory, disks, network — and schedules everything. A distribution (or "distro") is the kernel plus everything around it: a package manager, desktop environment, and tools, assembled into a usable system. Ubuntu, Debian, Fedora, and Arch are all the same Linux kernel with different choices around it — which is why "which distro should I learn?" matters far less than learning the shared core: the filesystem, permissions, and the shell. The comm...

Introduction Ask a room of developers what editor they use, and most will say the same name: Visual Studio Code, Microsoft's free, open-source editor. It won not by being the most powerful tool in any one area, but by being good enough at everything, extensible to anything, and free — a combination that quietly made it the default workspace for millions. Extensions: an editor that becomes anything Out of the box, VS Code is a capable editor with syntax highlighting, a file explorer, and a terminal. Its real power is extensions: tens of thousands of add-ons that turn it into a Python IDE, a Go IDE, a remote server editor, or a live-collaboration tool: Language extensions add autocomplete, error checking, and debugging for a language (the ESLint post's linter, for example, runs as a VS Code extension) Themes and icons change the look, which matters more than it sounds for a tool you stare at all day Remote extensions let you edit code on another machine, in a container, or in a c...