Using a calorie-tracking analogy, this piece argues that most engineering teams have no idea how much code (input) they're actually shipping relative to feature adoption (output). It explores why simple metrics like lines of code or PR counts are poor proxies, advocates for ML-based tools like Weave to estimate the real

7m read timeFrom newsletter.manager.dev
Post cover image
Table of contents
Engineering BodiesSo what are engineering calories?A note of caution
1 Comment

Sort: