Editorial directory
Three tracks. One site. Much less orientation debt.
This is the topic directory for chudi.dev: instead of dropping you into a long undated archive, it routes every article into the three systems that define the site, AI product development, bug bounty automation, and neurodivergent systems design, so you can start from the track that matches why you came.
Total articles
74
Primary journeys
6
How to use this
Pick a journey, read the “start here” piece, then follow the path from the hub.
Cluster selector
What does each cluster route me into?
Each cluster is a guided entry point, not just a taxonomy label. Pick the one that matches the work you do today: AI visibility engineering, AI product development, or neurodivergent systems. The cornerstone read for each cluster sits at the top of its journey, with the supporting posts arranged in a recommended reading order beneath it.
ADHD programmer systems: build around the brain you have, not the one the productivity books assume.
This track reframes parallel thinking, novelty seeking, abstraction, and chaos tolerance as engineering leverage, then turns them into practical workflow scaffolding.
Best for
ADHD and neurodivergent developers, designers, and founders
Reading depth
13 core essays and workflow guides
Start here
GTD for ADHD Doesn't Work: The Energy-Based System I Built Instead
GTD doesn't work for ADHD brains. The energy-aware productivity system I built instead, hyperfocus scheduling, AI processing, and the workflow I use to ship.
A Claude Code workflow that ships products, not demos.
This track covers Claude Code workflows, WebMCP agent interfaces, context management, evidence gates, RAG, and the operational decisions that move an AI idea into production.
Best for
builders, founders, and engineers shipping with AI
Reading depth
20 implementation notes, case studies, and security-automation architectures
Start here
Claude Code Best Practices 2026: What the Official Docs Don't Cover
Claude Code best practices the official docs do not cover, tested across 36K lines of shipped code: two-gate quality control, context persistence, tokens.
Visibility engineering: SEO optimizes for rank, answer engines optimize for citation.
This track is the engineering playbook for the second game: entity coherence, schema specificity, originality signals, and the measurement loops that show whether ChatGPT, Perplexity, and Google AI Overviews are actually citing you.
Best for
content engineers and sub-DR-20 operators engineering for AI citations
Reading depth
16 foundational, tactical, and case-study notes
Start here
How ChatGPT and Perplexity Decide Which Sources to Cite
How answer engines like ChatGPT and Perplexity decide which sources to cite: six measurable factors, 2026 platform data, and the fix for each one.
Production trading systems under real market constraints.
Prediction-market automation, postmortems, and the operational math behind live trading systems.
Best for
quantitative builders and trading-system operators
Reading depth
7 posts
Start here
Polymarket Arbitrage Bot in Python: How I Hit a 69.6% Win Rate
How to build a Polymarket trading bot in Python: CLOB API orders, Binance WebSocket feeds, and the 30-90s latency arbitrage behind a 69.6% win rate.
Deploy agents on infrastructure you actually control.
VPS setup, systemd process management, and the operational patterns that keep Python agents running 24/7 for $6/month.
Best for
Python developers deploying bots, agents, and automation
Reading depth
5 posts and growing
Start here
Run Your AI Agent on a VPS: The $6/Month Always-On Setup
Your AI agent dies when your laptop sleeps. The $6-25/month VPS setup I use to run trading agents 24/7: specs, systemd, and when latency justifies more.
Make sites that AI agents can read, recommend, and transact with.
Implementation patterns for WebMCP registerTool, MCP server design, ACP-compatible payment surfaces, and the schema infrastructure that makes agent-readable sites also agent-actionable.
Best for
builders shipping agent-actionable websites and SaaS surfaces
Reading depth
5 implementation guides (rolling out May to July 2026)
Best for
Think Better with ADHD
ADHD and neurodivergent developers, designers, and founders
Start with GTD for ADHD Doesn't Work: The Energy-Based System I Built InsteadBest for
Build with AI
builders, founders, and engineers shipping with AI
Start with Claude Code Best Practices 2026: What the Official Docs Don't CoverBest for
AI Visibility Engineering
content engineers and sub-DR-20 operators engineering for AI citations
Start with How ChatGPT and Perplexity Decide Which Sources to CiteBest for
Quantitative Trading Systems
quantitative builders and trading-system operators
Start with Polymarket Arbitrage Bot in Python: How I Hit a 69.6% Win RateBest for
Python Agent Infrastructure
Python developers deploying bots, agents, and automation
Start with Run Your AI Agent on a VPS: The $6/Month Always-On SetupBest for
Agent Readiness
builders shipping agent-actionable websites and SaaS surfaces
All tags
Where do the long-tail tags live?
The long-tail tag taxonomy still exists for readers who prefer filter-and-search over guided journeys. The tag list below is the residual filter surface; it no longer leads the experience but it remains complete. Tap any tag to land on its filtered archive view inside the blog.
Frequently asked questions
Four questions that come up before someone commits to a journey on this site. The short answers live here; the deeper ones live in the cornerstone post each journey pins at the top.
How do I pick the right journey for my work?
Pick AI visibility engineering if you are publishing content and want AI engines to cite you. Pick AI product development if you are building agent-facing systems or shipping production AI features. Pick neurodivergent systems if you want metacognition pieces that pair with the technical work and explain how to scaffold ADHD cognition for engineering output.
What is a cornerstone read?
The cornerstone is the load-bearing essay each journey is built around. It answers the canonical question for that journey end to end and ties together the supporting posts in the same cluster. Read the cornerstone first to get the full argument, then dip into supporting posts for depth on a specific sub-topic.
Where do I find newer posts that have not been added to a journey yet?
The full archive lives at /blog, organized newest-first beneath the three journey clusters. New posts get a journey assignment as part of publishing; the residual archive section captures anything outside the three primary journeys.
How can I subscribe to a single journey instead of the whole newsletter?
The current weekly newsletter sends a digest of all three journeys. A per-journey subscription option is on the roadmap but not yet shipped. LinkedIn at LinkedIn is the primary channel for new posts; tag-specific filtering is available via the /blog page's filter UI.