Start here

New to The Practical Developer? This page is the fastest way in. It gathers the most useful posts by topic, so you can start with the basics and move on to the languages, frameworks, and tools you need next.

Start with the basics

Languages

Web frameworks

Databases

Testing and code quality

Tools and DevOps

Data and machine learning

For the full list of posts, see the Table of Contents.

Comments

Post a Comment

Popular posts from this blog

Swift Explained: Apple's Language for iPhone, Mac, and More

A bike shop wants an iPhone app for its mechanics. The mechanic scans a repair job, the app totals the parts, applies a membership discount if the customer has one, and shows the amount to collect at the counter. It must never crash in front of a customer holding a bike. struct Order { let id: Int let total: Double let paid: Bool } let orders = [ Order(id: 101, total: 120.0, paid: true), Order(id: 102, total: 45.5, paid: false), Order(id: 103, total: 300.0, paid: true), Order(id: 104, total: 12.0, paid: true) ] let paidTotals = orders.filter { $0.paid }.map { $0.total } print(paidTotals) print(paidTotals.reduce(0, +)) Output: [120.0, 300.0, 12.0] 432.0 The filter and map calls read like the request itself: keep the paid ones, take their totals. Swift's main idea sits underneath that short code. Values that can be missing are marked as optionals, and the compiler makes you deal with the missing case instead of letting the app crash on it later. W...
Read more

Zig Explained: A Modern Systems Language Without the Magic

A community theatre totals its weekend ticket sales with a small command-line tool. The tool has to run on the old machine in the box office, start instantly, and print totals the treasurer can trust. The obvious choice is C: fast, small, and already installed everywhere. The trouble is that C hides its costs. A library call can allocate memory without saying so, an error can be ignored by accident, and a counter can overflow silently. The treasurer does not need a new language for its own sake. The question is whether a language can keep C's control while making every cost visible, so the person maintaining the tool can see what it does just by reading it. Quick answer Zig is a systems language that keeps C's control while making every cost visible: every allocation names its allocator, and every fallible call is marked with try or handled explicitly. It fits small command-line tools and programs that call C libraries, where you want the compiler to catch an overflow instead...
Read more

Rust Explained: Memory Safety Without a Garbage Collector

You run a small command line tool that parses a daily export file, and twice a month it crashes on a row nobody expected. The file is fine on Monday, a supplier adds a column on Tuesday, and by Wednesday your tool has died at 3 a.m. with a message nobody on call can explain. The crash is a memory or data handling mistake that a stricter language would have caught before the program ever ran. That is the problem Rust is built to solve: programs that are fast and also refuse to compile when they mishandle memory. Rust gives you C level speed without a garbage collector pausing your program. The trick is a set of rules, checked by the compiler before your program ever runs, called ownership. Every value has exactly one owner, the variable that holds it, and when the owner goes out of scope the value is cleaned up automatically. Move the value to another variable, and the first one can no longer use it. fn main() { let line = String::from("A1,2,120.50"); let moved = lin...
Read more