Joe Walnes joewalnes

Run Qwen 3.5 Locally with Claude Code — Zero API Bills, Full Agentic Coding

Your Mac has a GPU. Your Mac has RAM. Why are you paying someone else to think?

This guide gets you a fully local agentic coding setup: Claude Code talking to Qwen 3.5-35B-A3B via llama.cpp, all running on your Apple Silicon Mac. No API keys. No cloud. No surprise invoices. Just you, your M-series chip, and 35 billion parameters doing your bidding on localhost.

Based on this article.

Self-Improving Claude Code: A Bootstrap Seed

The Hypothesis

A single prompt (~1400 tokens), placed in a project's .claude/CLAUDE.md, can bootstrap a Claude Code instance into a self-improving system — one that captures learnings, extracts patterns, evolves its own configuration, and gets meaningfully better at helping its user with each session.

No pre-built infrastructure required. No user-level config. No hooks, skills, templates, or elaborate folder hierarchies. Just a seed and the affordances Claude Code already provides.

Background

macOS Internals

Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.

Starting Points

How to use this gist

You've got two main options:

Creating a redis Module in 15 lines of code!

A quick guide to write a very very simple "ECHO" style module to redis and load it. It's not really useful of course, but the idea is to illustrate how little boilerplate it takes.

Step 1: open your favorite editor and write/paste the following code in a file called module.c

#include "redismodule.h"
/* ECHO <string> - Echo back a string sent from the client */
int EchoCommand(RedisModuleCtx *ctx, RedisModuleString **argv, int argc) {

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

	/*
	* Copyright 2020 The Netty Project
	*
	* The Netty Project licenses this file to you under the Apache License,
	* version 2.0 (the "License"); you may not use this file except in compliance
	* with the License. You may obtain a copy of the License at:
	*
	* https://www.apache.org/licenses/LICENSE-2.0
	*
	* Unless required by applicable law or agreed to in writing, software

	"use strict";
	/* This is mostly just an example workflow to illustrate how a combination of ES6 generators and promises
	* fully allow you to write your asynchronous workflow in a single synchronous-looking block.
	*
	* Unlike most such workflows which give you a really short snippet that can hide all of the thornier
	* problems, this one is approximated from some of my work at IntegriShield: this is all of the real
	* stuff that an actual daemon might have to do: manage a queue or three of concurrent workloads; load
	* each item of each queue in order; make a bunch of concurrent requests on each item; preprocess each
	* of these requests; save preprocessed results to a cache in the database; if all of them have completed
	* successfully, report success, or else report failure.

	/*!
	* Copyright 2015 Google Inc. All rights reserved.
	*
	* Licensed under the Apache License, Version 2.0 (the "License");
	* you may not use this file except in compliance with the License.
	* You may obtain a copy of the License at
	*
	* http://www.apache.org/licenses/LICENSE-2.0
	*
	* Unless required by applicable law or agreed to in writing, software

	#!/bin/bash

	usage() {
	cat << EOF
	Usage: $0 [OPTION]... COMMAND
	Execute the given command in a way that works safely with cron. This should
	typically be used inside of a cron job definition like so:
	* * * * * $(which "$0") [OPTION]... COMMAND

	Arguments:

	.PHONY: me\ a\ sandwich

	me\ a\ sandwich:
	@echo "What? Make it yourself"