Skip to content

Instantly share code, notes, and snippets.

View stevegt's full-sized avatar

Steve Traugott stevegt

View GitHub Profile

Stack-Based TODO Handoff

Date: 2026-10-22

Repository: /home/stevegt/lab/cdint-grid-planner

Planner branch at handoff: planner

Planner commit inspected: 8179fd4215a793c1289f9cc8d65db19e5395be1c

Conversation Stack Analysis

Yes. The arrangement helps because it acts as an external attention-control system, not merely a record.

Structure Why it keeps work on track
Resume checkpoint Removes the cost of reconstructing “where were we?”
Accepted/proposed distinctions Prevents reopening settled decisions or implementing drafts
Numbered focus stack Serializes a highly branching design discussion
One-question-at-a-time rule Reduces decision fatigue and context switching
Note: For clarity we're using some shorthand in the examples below.
The full URL for e.g. common.conf would instead be
https://raw.githubusercontent.com/stevegt/tuios/refs/heads/main/common.conf
- we could keep the code simple and require users to use the full URL
- we could complexify the code and make it figure out the correct URL,
but that is going to be github and gitea specific, and fragile
- we could use a clone and copy method, but that should use some specific
statements about where to place the clone, etc.
=== procedural ===
@stevegt
stevegt / spec-graph-howto.dot
Created October 7, 2026 02:56
using graphviz DOT files as top-level specifications
// Intent: Show how a project can adopt Graphviz DOT as a reviewable
// top-level specification while keeping decisions, explanatory prose, tests,
// and work tracking in their proper roles.
digraph specification_graph_handoff {
graph [
rankdir=TB,
label="using DOT for a top-level specification",
labelloc=t,
fontsize=18,
fontname="sans-serif"
@stevegt
stevegt / nv
Created December 20, 2025 03:13
a script that i use to manage neovim shada files and start neovim accordingly
#!/bin/bash
# if -c flag is present, then use/create shada file in the current directory
if [ "$1" == "-c" ]
then
usecurdir=1
shift
fi
fn=nv.shada
@stevegt
stevegt / gist:50f5e20777c15bdeae20a9e160a94f47
Created September 3, 2024 01:00
example ollama client in python
from ollama import Client
import os
# derived from https://github.com/ollama/ollama-python
host = os.getenv('OLLAMA_HOST', 'http://localhost:11434')
client = Client(host=host)
response = client.chat(model='llama3.1:8b', messages=[
{
'role': 'user',
@stevegt
stevegt / gist:c912c4708e8181cecc6d2ba588c20620
Created September 3, 2024 00:43
example Ollama client in Go
package main
import (
"context"
"fmt"
"log"
"os"
"github.com/ollama/ollama/api"
. "github.com/stevegt/goadapt"
@stevegt
stevegt / got-loop.sh
Created May 29, 2024 01:42
a much simpler script for an automatic go vet loop
#!/bin/bash
winid=$(getwinid)
while true
do
inotifywait -r -e modify *
sleep 1
go vet || continue
wmctrl -ia $winid
@stevegt
stevegt / watch-test-commit.sh
Created May 29, 2024 01:39
a script I use to automate the go test/git commit cycle when doing rapid development and refactoring
#!/bin/bash
if [ -z "$1" ]
then
echo "Usage: $0 <paths-to-watch>"
exit 1
fi
# get current window id
window_id=$(xdotool getactivewindow)
// Single line comment
/* Multi-
line comment */
// A package clause starts every source file.
// Main is a special name declaring an executable rather than a library.
package main
// Import declaration declares library packages referenced in this file.
import (