https://ripp.dev/https://ripp.dev/about/https://ripp.dev/archives/https://ripp.dev/components/https://ripp.dev/posts/https://ripp.dev/posts/build-the-prototype-then-throw-it-away/https://ripp.dev/posts/code-review-is-unblocking-work/https://ripp.dev/posts/code-reviewers-should-push-back/https://ripp.dev/posts/companies-reflect-their-founders/https://ripp.dev/posts/how-i-make-sense-of-complex-backends/https://ripp.dev/posts/optimizing-ai-code-for-review-throughput/https://ripp.dev/posts/the-ai-trap/https://ripp.dev/posts/the-value-of-ux-in-enterprise-software/https://ripp.dev/posts/two-touch-points-for-small-features/https://ripp.dev/posts/why-backend-code-felt-harder-to-understand/https://ripp.dev/search/https://ripp.dev/series/https://ripp.dev/series/ai-workflows-for-team-delivery/https://ripp.dev/series/making-sense-of-backends/https://ripp.dev/tags/https://ripp.dev/tags/ai/https://ripp.dev/tags/backend/https://ripp.dev/tags/code-review/https://ripp.dev/tags/company-culture/https://ripp.dev/tags/engineering-leadership/https://ripp.dev/tags/enterprise-software/https://ripp.dev/tags/leadership/https://ripp.dev/tags/management/https://ripp.dev/tags/software-engineering/https://ripp.dev/tags/ux/https://ripp.dev/topics/