“Knowledge is power.” – Francis Bacon

Rust makes concurrency safe and predictable. You can create threads using std::thread, and communicate between them using channels from std::sync::mpsc. This lets you write multi-threaded programs without fear of data races or unsafe behavior. The first time I used threads in Rust, I was surprised by how easy it was. Coming from JavaScript’s async world, […]

In this project, you will build a basic command-line to-do list app in Rust. It stores tasks in a SQLite database using rusqlite, and accepts commands from the user via clap. This teaches you real-world CRUD operations: create, read, update, delete. When I first built a Rust CLI with persistent data, I wanted something minimal

The rusqlite crate is the easiest way to interact with SQLite databases in Rust. It allows you to create tables, insert rows, query data, and handle results using type-safe Rust code. When I needed to save user data in a Rust CLI app, I wanted something simple: no servers, no networking, just a file-based database.

Borrow checker errors in Rust usually mean your code is accessing memory in an unsafe or conflicting way. These errors often look cryptic at first, but they are actually protecting you from common bugs like use-after-free, data races, and memory leaks. When I started learning Rust, the borrow checker felt like a strict teacher that

Rust gives you full control over memory without needing a garbage collector. It uses the stack for fixed-size, known-at-compile-time values, and the heap for dynamically sized data. Understanding how Rust chooses where to store data helps you write faster and safer programs. I did not think much about memory layout before Rust. But once I

The regex crate gives Rust full support for regular expressions. It lets you search, validate, extract, and replace text using familiar patterns just like in JavaScript, Python, or other languages. I found myself reaching for regex when parsing logs in a CLI tool. Rust’s approach is different: regexes are compiled ahead of time, which makes

The chrono crate is the standard way to work with dates and times in Rust. It helps you parse, format, and perform arithmetic on dates and times, whether you are building logs, schedulers, or working with timestamps from APIs. I first used chrono when logging events in a CLI tool. I needed readable timestamps, but

In this mini-project, you will build a simple command-line application that fetches real-time weather data from a public API. You will use reqwest to make HTTP requests, serde to parse the JSON response, and clap to accept city names from the terminal. This is the kind of CLI I wish I had built earlier while

The serde crate is the standard for serializing and deserializing data in Rust. It allows you to convert Rust structs to JSON and back using powerful macros. Combined with serde_json, it gives you type-safe and flexible control over reading and writing structured data. I first used serde when building a CLI tool that needed to

The reqwest crate allows you to make HTTP requests in Rust with ease. You can perform GET, POST, and other HTTP methods, handle JSON responses, set headers, and deal with networking errors, all using an ergonomic API similar to popular libraries in other languages. When I first tried to call an API in Rust, I