Greptile’s Post

If you're wondering if blogs are a good growth statergy - within 48 hours of writing this post: ✨ it got on the front page of hackernews ✨ drove 10,000 visitors to our site ✨ led to 5 demos booked with Fortune 500, 1 with an Fortune 10. Writing the type of technical content that YOU would like to read helps you connect with exactly the types of users you want to serve, plus if you're like me and enjoy writing, it barely feels like work!

🚨 New blog post on codebase semantic search! 🚨 A problem we spend a lot of time on at Greptile is finding ways to semantically search large codebases. The Cmd+F search in your editor is exact-search - you have to name the file or symbol you are looking for. Imagine if you could search semantically - your search query is a few words about the functionality you're looking for, like "code that handles refresh tokens", and you are able to identify exactly where in the codebase that code is. In this blog post, I talk about why that's specifically hard to do with codebases, and things that have worked well for us at Greptile.

This is the graph of PRs reviewed per *hour* by Greptile over the last two weeks Strangely there is a spike in PRs opened every weekday at 9am PT. No one team makes enough PRs to move our metrics so this is super interesting. Any theories?

This is a chart showing PRs reviewed by Greptile over time. Each dip is a weekend! Interestingly, PRs spike on Thursdays, presumably people want to get them reviewed and merged before the weekend. There is something beautiful about this chart that I can't quite put my finger on.

Last Friday I got to talk to Hahnbee Lee, CTO of Mintlify about an important and often underrated topic - documentation! Mintlify powers the docs of many fast-growing startups, as well as companies like Anthropic and Pinecone, and Hahnbee has spent years studying how to write excellent documentation. I had 3 major takeaways from our conversation: 🥅 Developers come to docs with a goal Developers usually come to your docs with a specific goal. Your goal as a doc writer is to get them to that goal as quickly as possible. The better you are at doing that, the more developers you can get using your product! 📚 Separate Knowledge from Instruction Your quickstart doesn't need "why's", it only needs "do's". Instead of: "Next, to your header add your GitHub token and Greptile key. The GitHub token allows Greptile to access your repos, and the Greptile key links back to your billing account." Say: "Add GitHub token and Greptile key to the header" 🔍 Attention to Detail The risk of a buggy or sloppy developer tool, especially one that might go into production, is *catastrophic*. Documentation with mistakes are almost a warning of what comes next, and can subconsciously scare away your users. High attention to detail has the opposite effect. It's a relatively low effort way to inspire confidence in your users. Think about the attention to detail in Stripe's docs, often considered the gold standard: - Your Stripe key auto-populates in all the code examples - When you set a code sample box to TypeScript, every other box on the docs site also changes! What does this level of user obsession and attention to detail on the docs tell you about the people who built this product? They care, and they are meticulous. Characteristics that you would want your payment processor to have! Check it out on YouTube, Spotify, or Apple podcasts!

We’re hiring our first full-time GTM person at Greptile. We have been founder-led in our sales so far and seen success with that, looking to scale that up. You would lead our enterprise/mid-market sales effort and work in-person at our office in San Francisco. This starts out as a BDR role, but is likely to expand to AE/full-cycle sales in the coming months! More details here -> https://lnkd.in/gXUJVZdx

Today, we announce Greptile's $4.1M seed round, led by Initialized Capital with participation from Y Combinator, Richard Aberman, and JJ Fliegelman. We are building the AI expert that *truly* understands your codebase. It can answer hard questions about your codebase, review your pull requests with full context of your repos, and much, much more. We even offer Greptile as an API so you can build custom internal tools with it. Greptile started as a hackathon project last July, and now serves developers at over 500 companies. We are growing very fast. If you're an engineer passionate about building the future of AI-enable software development, join us!

Greptile's new code review bot summarizes and reviews changes with full context of your codebase. It catches bugs, code repetition, and anti-patterns better than humans. No more waiting for review, no more interrupting your flow for reviews. It takes <15 minutes to set up on a Zoom call (cal.com/greptile/15min to book), it's free for the first month, and when it reviews your first PR, we send you this cool SHIP FASTER crew neck. Join the 500+ teams that use Greptile to ship faster.

🦎Greptile can now review your pull requests! The hardest part about reviewing PRs is having full context of the codebase, which is exactly what Greptile is great at! Greptile's PR review bot can comment on things like: ✨ potential bugs introduced by the changes ✨ potential security issues introduced by the changes ✨ duplicate code which may exist elsewhere in the codebase ✨ potentially missed edge cases ...and more! Learn more here 👉 https://lnkd.in/eiwnEiHx