https://aidealy.ai/en weekly 1 https://aidealy.ai/en/how-it-works weekly 0.8 https://aidealy.ai/en/examples weekly 0.8 https://aidealy.ai/en/pricing weekly 0.8 https://aidealy.ai/en/security weekly 0.8 https://aidealy.ai/en/faq weekly 0.8 https://aidealy.ai/en/about weekly 0.8 https://aidealy.ai/en/videos weekly 0.8 https://aidealy.ai/en/talk-to-us weekly 0.8 https://aidealy.ai/en/legal/privacy 2026-11-03 weekly 0.8 https://aidealy.ai/en/legal/terms 2026-10-08 weekly 0.8 https://aidealy.ai/en/legal/refund 2026-10-09 weekly 0.8 https://aidealy.ai/en/legal/cookies 2026-11-03 weekly 0.8 https://aidealy.ai/en/legal/accessibility 2026-07-24 weekly 0.8 https://aidealy.ai/en/legal/imprint 2026-10-07 weekly 0.8 https://aidealy.ai/en/legal/sub-processors 2026-11-03 weekly 0.8 https://aidealy.ai/en/legal/vulnerability-disclosure 2026-09-06 weekly 0.8 https://aidealy.ai/en/legal/product-privacy 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/dpa 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/terms-of-service 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/acceptable-use 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/sla 2026-07-18 weekly 0.8 https://aidealy.ai/en/legal/ai-addendum 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/extension-eula 2026-10-18 weekly 0.8 https://aidealy.ai/en/legal/extension-privacy-notice 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/claude-code-collector-eula 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/claude-code-collector-privacy-notice 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal/eu-data-act-information 2026-10-30 weekly 0.8 https://aidealy.ai/en/legal weekly 0.8 https://aidealy.ai/en/videos/dora-metrics-ai-era DORA engineering metrics when half your code is AI-written https://aidealy.ai/videos/dora-metrics-ai-era/cover.jpg DORA (originally DevOps Research and Assessment) metrics still work when half your code is AI-written, but only in pairs: a speed number is safe to read only next to a stability number. This video reads DORA's 2024 and 2025 findings on AI adoption and shows what to change in your next quarterly review. https://www.youtube.com/embed/m37kcUhJXGM 610 2026-09-14T12:00:39-07:00 2026-11-10 weekly 0.8 https://aidealy.ai/en/videos/why-productivity-measurement-fails Why measuring developer productivity keeps failing https://aidealy.ai/videos/why-productivity-measurement-fails/cover.jpg Measuring developer productivity keeps failing when you count one activity, from lines of code in 1982 to the AI token counts on Amazon's leaderboard in 2026. Apple's managers stopped asking one engineer for his weekly lines of code in 1982 after he wrote minus two thousand. Ron Jeffries, who says he may have invented story points, regrets how they're misused. Kent Beck and Gergely Orosz answered McKinsey's 2023 framework: nearly every measure it added counted effort or output. And Amazon shut down its token leaderboard in 2026 after employees cheated to climb it. Andy Grove wrote the fix in 1983: measure output, not activity, and pair every measure with a measure of its counter-effect. https://www.youtube.com/embed/1NF6cOnKC5s 606 2026-09-27T10:33:14-07:00 2026-11-10 weekly 0.8 https://aidealy.ai/en/videos/metrics-that-get-you-fired Developer productivity metrics that get people fired https://aidealy.ai/videos/metrics-that-get-you-fired/cover.jpg Developer productivity metrics that count a single activity, from lines of code to AI token counts, get cheated, and when they decide reviews or layoffs, the wrong people get hurt. Never read one alone: put next to each count the measure that goes down when the work is bad, and before you act on a number about a person, ask them. https://www.youtube.com/embed/YrdTr0A3w9I 628 2026-10-01T12:25:49-07:00 2026-11-10 weekly 0.8 https://aidealy.ai/en/videos/measure-developer-productivity-ai-era How to measure developer productivity with AI coding tools like Claude Code and Cursor https://aidealy.ai/videos/measure-developer-productivity-ai-era/cover.jpg To measure developer productivity when AI coding tools like Claude Code and Cursor write much of the code, put every number for speed or amount next to the number that drops when the work is bad. Start with 3 pairs: merged pull requests and the fixes they needed after the merge, review speed and the approved pull requests fixed later, and AI spending next to the merged changes it paid for. https://www.youtube.com/embed/moyOqqVYqJY 626 2026-11-03T09:15:59-08:00 2026-11-10 weekly 0.8