All Posts
2026
- Rewriting a Resume for the Reader Who Won't Read It
- Reading Someone Else's Code to Build a Hardware Checklist
- Filling In the Other Half of the Lab
- Writing Robot Code Before Touching the Robot
- Three Review Comments and an Appendix from Scratch
- A Hardware Puzzle and Six Documents in Parallel
- Why Your Content Pipeline Needs a Kill Switch
- When Your Editor Reviews a Post That Doesn't Exist
- Two Hardware Puzzles and Six Documents in Parallel
- Daily Development Log - February 18, 2026
- Turning Eight Lectures into One Crib Sheet with Claude Code
- The Quiet-Day Problem: When Your Automated Pipeline Has Nothing Worth Saying
- When Your Blog Pipeline Blogs About Itself
- From Scattered Notes to a Full GitHub Roadmap in Ten Minutes
- Daily Development Log - February 13, 2026
- When Your Automation Works Everywhere Except Where It Matters
- Designing a Robot Stand: Why Dynamic Forces Will Ruin Your Day (If You Ignore Them)
- How a Mislabeled Test Point Nearly Derailed My Debugging Session
- Context-Switching Through FPGAs, Robots, and the Chaos of a Real Engineering Day
- Why the Backtick Key is Perfect for Developer Shortcuts (And Why Tab Nearly Broke Everything)
- Silent Failures and Systematic Debugging: A Day in AI-Assisted Development
- Four Ways to Customize Claude Code for Your Workflow
- When Your Automation Quietly Breaks: A Lesson in GitHub Actions Permissions
- Daily Development Log - January 14, 2026
- From Code to Physics: Using Claude Code to Design a Ball Launcher
- Solving a Projectile Motion Problem with Claude Code
- When Your Bug Could Break a Tool: Building a Safer CNC Postprocessor
- Debugging CNC Visualization: When Your 3D Preview Lies to You
- Beyond 90 Degrees: Adding Arbitrary Rotation to PenguinCAM
- When Your Automation Silently Fails: Debugging Empty Transcripts
2025
- Scanning for Secrets: A Security Audit with Claude Code
- Why Your Bot Works Fine Until It Restarts: A State Synchronization Bug
- Why Your Bot Works Fine Until It Restarts: A State Synchronization Bug
- Why a One-Line Config Change Made Me Appreciate Infrastructure as Code
- When Two Player Counts Are Both Right
- When Your Control Systems Final Becomes a Week-Long AI Collaboration
- When Your Control Systems Final Becomes a Week-Long Engineering Marathon
- When Your Control Systems Final Becomes a Multi-Day Journey with AI
- When Your Control Systems Final Becomes a Week-Long Coding Sprint
- When 50 Documents Meet 20 Pages: A Context Management Problem
- How AI Helped Me Find the Story Buried in My Engineering Final
- From Kinematic Chains to LaTeX: AI-Assisted Academic Writing
- Why My Discord Bot Was Announcing Villager Funerals
- When Your Automation Silently Fails: Debugging Empty Transcripts
- When Everything Lies About Its State: GIF Frames, Exam Deadlines, and a Discord Bot That Couldn't Accept Reality
- The 2:47 PM Pivot: When Finals Week Becomes a Context-Switching Marathon
- When Day-One Upgrades Should Be Boring
- The Day-One Upgrade: Keeping a Minecraft Server on the Bleeding Edge
- From Kinematic Chains to LaTeX: How I Built an Exam Cheat Sheet with Claude Code
- Building a Two-Day Exam Reference Sheet with AI: When Dense Physics Meets Dense PDF
- When Your Academic Report Needs a Corporate Scrub: AI-Assisted Document Editing
- When Your Academic Report Needs a Corporate Scrub
- Turning Engineering Code Into a Graded Report: The Self-Grading Loop
- When Physics Intuition Meets ISO Standards: Debugging My Understanding of Rotor Runout
- When Physics Intuition Meets Vacuum Thermal Models: Debugging a Flywheel Energy Storage Simulation
- When Physics Intuition Meets Vacuum: Debugging a Flywheel Thermal Model
- Why Custom AMIs Beat Containers for My Minecraft Server
- When Your Script Declares Victory Before the Server's Ready
- Reverse-Engineering Black-Box MATLAB: When Your Flywheel Analysis Hits a Wall
- Debugging a Minecraft Server on AWS: From CloudFormation Limits to RCON Credentials
- When File-Based Detection Lies: Switching to RCON for Minecraft Server Auto-Shutdown
- When File-Based Detection Lies: Switching to RCON for Minecraft Server Status
- Feedback Loops: How Verifying Against Solutions Changed My AI Workflow
- Three Scales of Verification: What a 22-Degree Discrepancy Taught Me About Trusting My Tools
- How Claude Helped Me Learn PLC Ladder Logic in One Session
- Five Polling Loops and Zero Communication: An Architecture Archaeology
- When Your CAD Construction Lands the Pivot 20 Inches Away
- The Line Between Learning and Formatting: AI in Engineering Education
- Five Polling Loops and Zero Communication: An Architecture Archaeology
- Why My Linkage Optimizer Returned Infinity for 188 Generations
- What 188 Deleted Files Taught Me About Project Hygiene in Linkage Synthesis
- The Last 10% of a Six-Bar Linkage
- The Last 10% of a Six-Bar Linkage
- When Your Mechanism Works Until It Doesn't: Debugging Kinematic Limits
- When Your Mechanism Works Until It Doesn't: Debugging Geometric Constraints with AI
- How Claude Helped Me Decode My First Ladder Logic Program
- Ghost Commands and PID Controllers: A Day of AI-Assisted Debugging
- How I Turned Exam Panic into a Constraint Satisfaction Problem
- Two Optimization Problems, One Day: From Linkages to CloudFormation
- From Dense PDF to Bench-Ready Checklist: Reformatting a Motion Control Lab
- The Mohr's Circle That Lied: How Treating a Report Like a Test Suite Revealed Hidden Errors
- When Research Is the Foundation: Four Projects, One Day, One Pattern
- When Your Optimization Breaks Physics: Debugging a Wind Turbine Model That Beat Thermodynamics
- The Day I Let Claude Organize My Dev Folder
- The Arithmetic Isn't the Point: What I Actually Learned Using AI for Lab Reports
- When Your Session Transcript Becomes an Archaeological Dig
- When Your Logging Breaks: Debugging a Silent Failure in My Blogging System
- When Elimination Is Progress: Debugging Linkages and Fatigue in One Day
- The Last 10% of a Six-Bar Linkage
- From PDFs to Polished Code: When Your Engineering Project Gets Real Data
- When Your Data Acquisition System Needs to Remember What It's Testing
- When Your Lab Report Needs 23 PNG Files by 11 PM
- When Your Transcript System Captures Everything Except What Actually Happened
- When Your Logging System Logs Nothing: Thirteen Empty Tool Calls
- From Napkin Math to Full Simulation: Building a Supersonic Trebuchet Optimizer
- NaN: Three Characters That Mean Your Script Ran Successfully and Told You Nothing
- The Staircase Cosine: What a DAC Taught Me About Debugging
- When Your Transcript System Captures Everything Except the Conversation
- The Five Minutes That Saved Me Forty: Why I Read Before I Copy
- Reading Before Refactoring: What My Stirling Engine Code Actually Taught Me
- The 90% Problem: Why AI-Generated Code Passed Every Check Except Understanding
- When 0.00001 Doesn't Matter (But Two Degrees Does)
- When Your Code Is Right But Your Model Is Wrong
- When Your Code Runs Perfectly and Still Produces Nonsense
- The Thirty-Second Edit That Made Me Question Everything
- When My Shading Logic Was Inverted and I Didn't Notice
- The Ghost in My Stirling Engine: When Code Runs Perfectly But Physics Doesn't
- AI-Assisted Engineering Homework: Lessons from Three Courses in One Day