Yes, you can. You can use Apple Intelligence’s local on-device models to generate commit messages without downloading anything new.
The "secret" backdoor to accessing these models from the terminal is the Shortcuts app, which has a command-line interface (shortcuts) and exposes Apple Intelligence actions.
You can build a simple "bridge" that takes your git diff, sends it to Apple Intelligence, and pipes the result back to your commit.
Finding divergent “fringe” ideas that might solve emerging problems works best as a repeatable practice: systematically scan for weak signals, spend time with lead users at the edge of need, and then rigorously stress-test the ideas before investing heavily.[1][2]
Horizon scanning is a structured way to look for early signs (weak signals) of potentially important developments that sit outside mainstream attention today.[3][1]
The lead user approach focuses on people who experience needs
Perfect! I found the blog post you were looking for. It's "Climbing the Wrong Hill" by Chris Dixon (not from mathewanders.com), published in September 2009. This is the exact post that uses the mountain peak and local maxima metaphor you described.
The Core Metaphor:
Chris Dixon uses a computer science concept called "hill climbing" to explain why smart, ambitious people often get stuck pursuing the wrong career path. Here's how he explains it:[1]
/Users/eon/conduit.design/_docs/architecture_and_structure_guide.md /Users/eon/conduit.design/_docs/code_style_guide.md please read these documents. then scan the code base for lowkey low hangingfruit low risk items that doesnt follow these guids. then make a list of at least 20-40 items and save it to a markdown file for later refactoring. do not refactor yet. just search analyse and make the list
This is how I solve bigger code challanges. Like really complex features.
export keyword - never delete the actual code (
Git worktrees and Git branches are related but fundamentally different in how they let you interact with your code. Both are part of Git, but they solve different workflow challenges.[2][5]
Branches are Git's way of diverging from the main line of development to work on different features or fixes. In standard Git branching, you work in a single working directory and switch between branches using commands like git checkout or git switch. When you switch branches, Git updates the files in your current directory to match the branch you're switching to. This means you need to either commit or stash your work-in-progress changes before switching, which can disrupt your workflow.[1][5][2]
Git worktrees allow you to check out multiple branches from the same repository simultaneously, each in its own separate working directory. Instead of switching branches by changing what's checked out in one directory, you switch branches by literally moving between different d
Open design format is a declarative design system that uses JSX-like syntax to create responsive layouts and UI components, specifically designed for Figma integration. Based on the Figma Widget API, it provides a comprehensive set of components for building sophisticated user interfaces with automatic layout management, styling, and effects.
Open design format enables designers and developers to create UI components using a JSON-based JSX format that maps directly to Figma's widget system. It supports real-time design collaboration through a WebSocket-based communication layer between AI agents and Figma via the Model Context Protocol (MCP).