The Curious Engineer

All blogs / Dev tools / editors / IDEs

Graphite blog

graphite.com

Graphite helps teams on GitHub deliver higher quality software, faster.

Dev tools / editors / IDEsSoftware / engineering practice

’23’24’25’26
Posts
99 from 26 Sep 2023 to 2 Apr 2026
Posting
monthly (6 in the last year)
Kind
company blog
Feed
https://graphite.com/feed.xml

2026 2

  1. Introducing Code Tours: a new way to review
  2. Introducing Cursor Cloud Agents in Graphite

2025 23

  1. Building the future of software development with Cursor
  2. Reimagining the PR Page: Designing for speed and focus
  3. Graphite changelog [11-20-2025]
  4. Graphite changelog [11-04-2025]
  5. Graphite changelog [10-16-2025]
  6. The future of engineering is collaborative (and already here)
  7. Meet Graphite Agent: The next evolution of AI code review
  8. Introducing frozen branches: A safer way to build on your teammates’ work
  9. Graphite changelog [09-17-2025]
  10. How we sped up code search for Graphite Chat
  11. Introducing Graphite Chat
  12. AI is writing code—here's why it also needs to review that code
  13. How I got Claude to write code I could actually ship
  14. How we built the first stack-aware merge queue (and why it matters)
  15. How we organize our monorepo to ship fast
  16. Graphite brings stacking to Tower
  17. Code review tooling: Should you build or buy?
  18. Making AI code review available to everyone
  19. Introducing: The new Graphite + Linear integration
  20. Graphite raises $52M and launches AI code review agent Diamond
  21. Why AI will never replace human code review
  22. How stacked PRs unblock distributed development teams
  23. Graphite is going to Developer Week 2025

2024 56

  1. Beating the end of year code freeze
  2. How Graphite’s eng team ships code remarkably fast
  3. Why we chose Anthropic's Claude to power Graphite Reviewer
  4. AI code generation will remain fragmented
  5. How we redesigned Graphite's landing page in-house
  6. Introducing Graphite Reviewer: your AI code review companion
  7. How AI code review reduces review cycles to improve developer productivity
  8. What if you could get instant feedback on your code?
  9. The new developer toolchain for the age of AI
  10. Not Rocket Science - How Bors and Google’s TAP inspired modern merge queues
  11. State of code review 2024
  12. How Google migrated billions of lines of code from Perforce to Piper
  13. Going from 0 to 1: How to write better unit tests when there are none
  14. Speed up your merges: Parallel CI is now generally available for teams using Graphite’s merge queue
  15. Down for less than four minutes a month: how AWS deploys code
  16. BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days
  17. Graphite is now free for startups and open source projects
  18. Launch week wrap-up (May 2024)
  19. Reduce CI costs for Buildkite and GitHub Actions
  20. Cheaper CI & faster merging with batching
  21. How Google does code review
  22. The technical learning curve at a startup is gentler than you might think
  23. Graphite will now automatically rebase your partially-merged stacks
  24. Multiple engineers can now seamlessly collaborate on the same stack of PRs
  25. Do you ever outgrow GitHub?
  26. From the 80's to 2024 - how CI tests were invented and optimized
  27. Graphite changelog [4/10/2024] 🎺
  28. Graphite changelog [4/25/2024] 🐸
  29. How Stack Overflow replaced Experts Exchange
  30. How GitHub replaced SourceForge as the dominant code hosting platform
  31. Graphite changelog [3/27/2024] 🤝
  32. The core principles of building a good AI feature
  33. Onboarding roulette: deleting our employee accounts daily
  34. Graphite changelog [3/13/2024] 🚁
  35. Why Facebook doesn’t use Git
  36. How to recreate the Phabricator code review workflow
  37. Types of code reviews: Improve performance, velocity, and quality
  38. What's the best GitHub pull request merge strategy?
  39. Phabricator vs GitHub vs Graphite: How do they stack up?
  40. Improving team velocity through better pull request practices
  41. Moving fast breaks things: the importance of a staging environment
  42. Building trust as a software engineer
  43. Keeping code simple: moving fast by avoiding over-engineering
  44. GitHub pull request filters alternative: The Graphite pull request inbox
  45. 7 Best Phabricator alternatives for PR stacking & code review [2024]
  46. Accurate eng estimations: predicting and negotiating the future
  47. Tracking and understanding GitHub PR stats: A step-by-step guide
  48. 8 best practices for pull requests in software engineering
  49. Graphite Q1 launch week: What’s next for Graphite
  50. Graphite Q1 launch week: Stacking with the tools you love
  51. Graphite Q1 launch week: Making stacking seamless
  52. Graphite Q1 launch week: Accelerating code review
  53. The "Mom Test" in software development: asking good questions when everyone is lying to you
  54. How to use stacked PRs to unblock your entire team
  55. Graphite Q1 launch week 2024
  56. The practical and philosophical challenges of AI code review

2023 18

  1. Empirically supported code review best practices
  2. Call site attribution: how to pinpoint rogue SQL queries throttling database performance
  3. Every engineer should understand git reflog
  4. Post mortem: our outage took 124 seconds from you, here's 378 back
  5. Your GitHub pull request workflow is slowing everyone down
  6. Optimizing CI/CD workflows for trunk-based development
  7. Why we use AWS instead of Vercel to host our Next.js app
  8. How large pull requests slow down development
  9. 3 key lessons in Node.js server optimization
  10. Trunk-based development: why you should stop using feature branches
  11. Understanding Git: The history and internals
  12. Why large companies and fast-moving startups are banning merge commits
  13. How long should your CI take?
  14. Experimenting with AI code review
  15. CRA to App Router in 5 Steps: A case study with Graphite
  16. Graphite changelog [10/18/2023]
  17. The comprehensive guide to writing the best PR title of all time
  18. How 10,000 Developers all Contribute to the Same Repo