Developer shares 'Short Leash' method for controlling AI coding assistants

·1 views

A developer published a blog post on okturtles.org describing a technique called the 'Short Leash' method for working with AI coding tools. The approach appears aimed at maintaining tighter human oversight and control during AI-assisted software development. The post gained attention on Hacker News, accumulating 13 points and at least one comment. The method is presented as a strategy for avoiding common pitfalls when using AI to write or assist with code. Full details of the technique are available on the author's blog at okturtles.org.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

IT Tech Builds No-Install USB Diagnostic Toolkit to Skip Repetitive Setup

A developer and IT technician grew frustrated with repeatedly assembling diagnostic tools on every new machine or client site, prompting them to create a portable USB-based toolkit. The kit is built around a strict rule: all tools must run directly from the USB drive, install nothing on the host machine, and leave no trace after removal. It is organized into three functional areas — system health checks, network diagnostics, and user profile management — covering the most common IT troubleshooting scenarios. The author notes that using a fast USB 3.0 or higher drive is important, as slow hardware can make portable tools appear broken. While the toolkit can be assembled for free using existing portable utilities and built-in Windows commands, the author also packaged and released it commercially for $34 as a one-time download.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Coding Skills: Why Structured Workflows Beat Simple Code Prompts

Most developers use AI coding assistants with simple one-line prompts, but this approach often produces inconsistent and shallow results. Developer Matt Pocock's open-source Skills repository proposes a better method: giving AI structured, reusable engineering workflows instead of ad-hoc instructions. These workflows guide AI through processes like writing Product Requirements Documents, test-driven development, systematic debugging, and architecture reviews. The approach mirrors how experienced software engineers actually think, making it useful for both greenfield projects and legacy codebases. By treating AI as a process-following collaborator rather than a code generator, developers can achieve more reliable, maintainable, and professionally structured outputs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a developer shipped a libmpv-based video player on the Mac App Store

Developer Reel, a local video player and library app for macOS, was successfully submitted to the Mac App Store despite most mpv-based players distributing outside it. The process took about a month from first commit to approval, with the biggest hurdle being a JIT-related crash caused by LuaJIT's memory allocator conflicting with App Store sandbox entitlement rules. The fix was a single build-flag change to disable Lua entirely, since the app never used mpv's scripting features, which also eliminated the need for two otherwise-required entitlements. Additional challenges included LGPL compliance with static linking, two sandbox traps that only surfaced after local testing, and a design rejection. The developer published the experience as a field guide for anyone integrating FFmpeg or libmpv into a sandboxed Mac app.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Browser-Based SysEx Librarian Using Web MIDI API, No Install Needed

A developer has built knob.monster, a browser-native librarian tool for vintage synthesizers like the Yamaha DX7 and Roland Juno-106, eliminating the need for legacy desktop utilities such as MIDI-OX. The tool leverages the Web MIDI API, available in Chromium-based browsers, to capture and restore SysEx patch dumps directly from a connected USB-MIDI interface. Raw SysEx data is streamed as byte arrays, parsed server-side into readable patch names, and stored in a PostgreSQL database for cloud backup and one-click restoration. Because each synthesizer manufacturer uses a unique SysEx handshake, the tool implements model-specific dump request sequences, and clearly communicates hardware-side steps — such as the Juno-106 requiring a manual panel button press. The solution currently works only on Chrome, Edge, and Opera, as Safari and Firefox do not support the Web MIDI API.

0 comments Read more at DEV Community