#tools
8 posts
-
Agentic coding: a great pair programmer, if you know what to ask for
What it's like to build with a coding agent like Claude Code, why being specific matters so much, and why knowing your tools and technologies matters more than ever.
-
C++ with CMake, Conan and Ninja
A complete, tested walkthrough: choosing packages from ConanCenter, building with CMake and Ninja, linking the libraries, and producing static executables.
-
Writing tests: what they prove, and what they don't
How to write useful tests, what Go, Python, C++, Rust and PHP use to run them, a closer look at GoogleTest, and why a green test suite proves what works but never that there are no bugs.
-
Issue tracking: from bug report to commit
Tracking bugs and features with GitHub for public projects, or self-hosted Gogs or Forgejo, and linking every issue to the tests and commits that resolve it.
-
uv: Python versions, venvs and projects, with examples
A hands-on guide to uv: installing Python versions, managing virtual environments, building a complete project, single-file scripts, tools, and whether you really need a src directory.
-
Python: what it does best
Where Python shines, and a tour of the libraries we reach for most: requests, pendulum, pandas, Django, Jinja2, SQLAlchemy, Black, Pylint and pytest.
-
Git for every project
Why git is the version control tool we use for everything: cheap branches for refactoring and experiments, smooth collaboration, and the commands you'll use every day.
-
The right tool for the job
PHP, Python, Go, C++ and Rust: what each is good at, where each hurts, and how to choose a language and its libraries.