eonist

tell me 10 scams that has become established truths

Some scams and hoaxes don’t just trick a few people—they shape “common knowledge” for years (or even generations) before being exposed. Here are 10 well-documented examples where a deception was widely treated as true or used as “proof.”[^1_1][^1_2]

Ten “truth-like” scams

• Piltdown Man: A forged “missing link” fossil announced in 1912 was widely accepted for decades before being conclusively shown to be a composite forgery in 1953.[^1_2][^1_3]
• Cardiff Giant: A carved gypsum “petrified man” (1869) became a paid attraction and was treated by many as a real archaeological find until it was exposed as a hoax.[^1_4][^1_5]

eonist

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.

How to set it up (No new downloads)

You can build a simple "bridge" that takes your git diff, sends it to Apple Intelligence, and pipes the result back to your commit.

1. Create the Shortcut

1. Open the Shortcuts app on macOS.

eonist

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]

Scan for weak signals

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]

• Build a weekly “signal feed” from places where novelty appears early (new research, niche forums, small startups, policy pilots), and tag each item as “new capability,” “new constraint,” or “new behavior,” because weak signals are often subtle indicators of emerging issues.[2][4]
• Keep a “fringe log” and deliberately include signals from subcultures and non-obvious domains, since some public-sector scanning programs explicitly target fringe areas to broaden what gets noticed.[5]

Find lead users

The lead user approach focuses on people who experience needs

eonist

Task:

Primary objective:

Low-hanging fruit, low-risk refactoring items that don't follow the Architecture & Structure Guide and Code Style Guide

description

could you look at these documents: /Users/eon/conduit.design/_docs/code_style_guide.md

eonist

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 Blog Post: "Climbing the Wrong Hill" by Chris Dixon

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]

The Hill Climbing Problem

eonist

/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

eonist

hard problems

This is how I solve bigger code challanges. Like really complex features.

1. I asked for feedback on legacy code. pros and cons.
2. i made my idea for v2 how it should work etc. then i asked the AI to plan it out in detail in a plan.md doc.
3. i asked the ai to make readme doc for the feature before coding it.
4. then i gave the ai all of these docs, and asked it to code it. it took 2h for it to finish.

• four ais did this simultaniously. 2 in pplx. 1 cursor 1 cline. about 20$ each.

eonist

AI Coder Checklist: ts-prune Safe Removal

For Each Flagged Export

1. Grep the codebase for the export name (check for dynamic imports, string refs, config files)[1][2]
2. Only remove the export keyword - never delete the actual code (⚠️️ DO NOT REMOVE ANY CODE, ONLY export word. EXTREMLY IMPORTANT ⚠️️)
3. If unsure, skip it and move to the next one

Process

eonist

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]

What Are Branches?

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]

What Are Worktrees?

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

eonist

Open design format API Documentation

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.

Overview

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).

Architecture