The Illusion of My Own Efficiency: How Claude Exposed My Arrogance and Lack of Planning at Night

Source: Dev.to

Conversations with AI are not for improving skills, but for recognizing your own arrogance

I, Shossan, have taken pride in automating my environment and controlling it efficiently. Analyzing my shell history while conversing with Claude Cowork revealed an unplanned, bias‑laden workflow—embarrassing, to say the least.

Being prompted by AI to improve feels like a defeat for an engineer, but that defeat can be the gateway to growth.

People mistake unconscious repetition for effort

Why couldn’t I notice my own inefficiencies? A bias called familiarity had crept into my daily work.

When Claude analyzed my past command history, three blind spots emerged:

• Collapse of time management: Activity peaked at 21:00, a time when I should have been resting. This wasn’t diligence; it was repaying debt caused by poor daytime planning.
• Hollow automation: I manually executed ansible-playbook 31 times. While I thought I was using automation tools, the process remained highly analog and dependent on manual work.
• Tool dependency: Relying on convenient tools (Keyboard Maestro, Stream Deck, Claude Code, etc.) gave me the false impression that there was no room for improvement.

The cold data‑driven insights and the automation functions I immediately implemented

Claude’s analysis showed my activity concentrated at 08:00 and 21:00. Hammering commands at 21:00 after a bath is a bad habit that degrades sleep quality and next‑day performance. Accepting this fact, I adopted the improvement proposals Claude suggested.

Custom LaunchAgent manager

Previously I typed commands while trying to remember paths or searching history. The new svc function now handles the cognitive load.

# ~/.config/fish/functions/svc.fish
function svc --description "LaunchAgent service control"
  set -l action $argv[1]
  set -l name $argv[2]
  set -l plist ~/Library/LaunchAgents/com.oshiire.$name.plist

  switch $action
    case start
      launchctl load -w $plist
    case stop
      launchctl unload -w $plist
    case restart
      launchctl unload -w $plist; and launchctl load -w $plist
    case status
      launchctl list | grep $name
    case '*'
      echo "Usage: svc [start|stop|restart|status] [service_name]"
  end
end

Short ap wrapper for ansible-playbook

Claude also proposed a concise ap function that eliminates common mistakes such as missing arguments or forgotten options, streamlining the workflow.

Looking into the mirror called AI, strategically updating yourself continuously

If you merely praise AI’s suggestions, you remain a consumer. The real learning lies in converting AI‑pointed negatives into positive system solutions.

Abandon the assumption that you are doing well, and set aside time to regularly dissect yourself with objective data. Use AI not just as a code generator but as a behavioral analysis partner.

From here, I will continue to cut away waste, one step at a time. Try exposing your terminal and behavioral history—your embarrassing parts—to AI and see what it reveals.