惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Last Week in AI
Last Week in AI
有赞技术团队
有赞技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
人人都是产品经理
人人都是产品经理
博客园 - 司徒正美
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 叶小钗
罗磊的独立博客
IT之家
IT之家
博客园 - 三生石上(FineUI控件)
V
Visual Studio Blog
T
Tailwind CSS Blog
大猫的无限游戏
大猫的无限游戏
Hugging Face - Blog
Hugging Face - Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
Netflix TechBlog - Medium
MyScale Blog
MyScale Blog
J
Java Code Geeks
L
LangChain Blog
S
SegmentFault 最新的问题
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Apple Machine Learning Research
Apple Machine Learning Research
G
Google Developers Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Using AI to Build Your Year-End Performance Case
Phaneendra K · 2026-04-24 · via DEV Community

Phaneendra Kanduri

Most engineers lose their appraisals in June. Not because they underperformed — because they forgot what they shipped. Your manager tracks 8-12 reports across 40 weeks. If you walk into December with "I think I did good work?" you've already lost.

The problem is mechanical. Brag documents require weekly discipline most people don't have. Miss one week, friction compounds, you stop forever. Claude can automate this if you build the right scaffold.

This article walks through a working system: a bash hook that captures daily commits, a Claude prompt that extracts signal, and a cron job that writes progress summaries every hour. By December you have timestamped evidence of shipped work your manager can't dispute.

The Hook

#!/bin/bash
# ~/.git-hooks/post-commit

PROGRESS_FILE="$HOME/.work-progress/$(date +%Y-%m).jsonl"
COMMIT_MSG=$(git log -1 --pretty=%B)
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")

echo "{\"timestamp\":\"$TIMESTAMP\",\"message\":\"$COMMIT_MSG\"}" >> "$PROGRESS_FILE"

Enter fullscreen mode Exit fullscreen mode

Fires after every commit. Appends to monthly JSONL file. No Claude yet, just durable capture.

The Summary Layer

#!/bin/bash
# ~/.work-progress/summarize.sh

COMMITS=$(cat "$HOME/.work-progress/$(date +%Y-%m).jsonl")

curl -s https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "content-type: application/json" \
  -d "{
    \"model\": \"claude-sonnet-4-20250514\",
    \"max_tokens\": 2000,
    \"messages\": [{
      \"role\": \"user\",
      \"content\": \"Extract work from these commits. Group: shipped features, infrastructure, cross-team contributions, bugs. Ignore: deps, formatting. Output markdown bullets.\n\n$COMMITS\"
    }]
  }" | jq -r '.content[0].text' > "$HOME/.work-progress/$(date +%Y-%m)-summary.md"

Enter fullscreen mode Exit fullscreen mode

Add to cron: 0 * * * * $HOME/.work-progress/summarize.sh

Runs hourly. Claude rebuilds your summary all month.

What You Get

## Shipped Features
- OAuth2 migration with PKCE (Nov 3-7)
- FCP 1.8s → 0.4s via lazy loading (Nov 12)
- WCAG 2.1 AA modal system (Nov 18)

## Infrastructure
- Pre-commit hooks block console.log (Nov 5)
- CI: 12min → 6min build time (Nov 20)

Enter fullscreen mode Exit fullscreen mode

Timestamped, categorized, backed by Git history.

Beyond Commits

Extend the JSONL for non-code work:

{"timestamp":"2025-11-15T14:30:00Z","type":"mentorship","summary":"Debugged Redux with Sarah, 2hrs"}
{"timestamp":"2025-11-18T10:00:00Z","type":"incident","summary":"Fixed payment 502s, 8% of checkouts"}

Enter fullscreen mode Exit fullscreen mode

Update the prompt to handle these. Now you're logging the IC2→IC3 behavior managers actually reward.

December: The Final Pass

cat $HOME/.work-progress/*-summary.md | \
curl -s https://api.anthropic.com/v1/messages [...] \
  -d '{"messages":[{"role":"user","content":"Rewrite into self-assessment. Lead with impact, quantify, group by velocity/quality/leadership."}]}' \
  > self-assessment-2025.md

Enter fullscreen mode Exit fullscreen mode

Consolidates 12 months into one appraisal document. Copy-paste into your company's form.


Why It Works

Removes two failure modes:

  1. Retroactive memory (March work recalled in November is lossy)
  2. Manual upkeep friction (one missed week = death spiral)

Hook captures everything, Claude filters signal, zero ongoing effort. Manager reads a structured promotion case in their language, verified in Git.

Extend to JIRA (story points, cycle time), Zendesk (tickets closed), Slack (incidents resolved). Same pattern: auto-capture, Claude extracts narrative, deliver when it matters.