patrickdevivo's comments

patrickdevivo | 19 days ago

thanks for sharing. some of the highlights we found interesting:

* Growth rate of new repos doubled in 2025 (driven by AI?) * Microsoft leads Big Tech in repo creation, contrary to narrative the company is closed * a16z captured nearly as much OSS value as all other early-stage VCs combined

Also, AI repos since 2023 have seen an outsized share of attention relative to other categories of repo (as measured by GitHub stars). This is not surprising, but interesting to see it playing out in the data.

patrickdevivo | 11 months ago | on: Launched my first Stripe app to help founders understand their customers

I just developed and launched my first Stripe "dashboard app" (https://docs.stripe.com/stripe-apps) - which is a way Stripe allows developers to embed custom UIs in the Stripe dashboard and distribute through an app marketplace. I thought this was pretty cool, so I wanted to give it a shot.

The app helps you understand your customers by automatically researching firmographic information and recent news about the companies buying your product - if the customer uses a work email. It uses the new OpenAI Responses API to do the research - so results are not always correct, but working on it! This is especially true for smaller companies that may not have much public information available.

It's basic for now - but it allows you to answer simple questions about who's buying your product, and gives you a starting point to find out more about them.

The app is free, and I have more features planned, including aggregate reporting over all customers, to answer deeper questions like:

* What industries do our best customers come from? * Do we sell more to large companies or small companies? * What's our ICP? * What's the geographic breakdown of our customers this month?

etc...

I'd love to know what people think - I'm open to feedback and would love to tailor the next set of features based on specific requests. So please let me know if there are workflows or insights you'd like to be able to see using this information. Thanks!

patrickdevivo | 3 years ago | on: Ask HN: What are you using to manage in your team the projects/features?

I've been using GitHub Issues (and their new Projects feature) more and more. It's far from perfect, but I really value the colocation of code + task management it allows. I like being able to reference issues/PRs by # in markdown comments - it feels more natural to leave "breadcrumbs" this way so that others can follow the chain of events when trying to piece something together.

One thing we've done internally, for all tasks that aren't tied to a repo (because GitHub issues must belong to a repo), we created an "internal" repo that's a catchall for tasks not necessarily tied to a codebase.

The Projects view then let's us plan work across multiple codebases and this "non-codebase" repo

patrickdevivo | 3 years ago

a very cool project they also maintain is a MySQL server framework for arbitrary backends (in Go): https://github.com/dolthub/go-mysql-server

You can define a "virtual" table (schema, how to retrieve rows/columns) and then a MySQL client can connect and execute arbitrary queries on your table (which could just be an API or other source)

patrickdevivo | 4 years ago

Seconded for Hasura - really great tool that's make it easy to setup an API on your database. Also makes it easy to manage your data models and permissions. You can use it to build REST API endpoints as well as GraphQL ones.

patrickdevivo | 4 years ago

Thanks for this write up! I've been really interested in postgres compatibility in the context of a tool I maintain (https://github.com/mergestat/mergestat) that uses SQLite. I've been looking for a way to expose the SQLite capabilities over a more commonly used wire-protocol like postgres (or mysql) so that existing BI and visualization tools can access the data.

This project is an interesting one: https://github.com/dolthub/go-mysql-server that provides a MySQL interface (wire and SQL) to arbitrary "backends" implemented in go.

It's really interesting how compatibility with existing protocols has become an important feature of new databases - there's so much existing tooling that already speaks postgres (or mysql), being able to leverage that is a huge advantage IMO

page 1