Documenting code, one commit at a time.
Making content easily discoverable for AI search engines is crucial for broader reach. Here's how we improved the accessibility of our tenant portfolio content.
Our primary objective was to enable AI search engines to easily discover and consume tenant portfolio content. This involved providing machine-readable endpoints that expose content in a structured and easily parsable manner.
When dealing with multi-tenant applications, handling tenant removal gracefully is crucial for user experience and data integrity. This post discusses a strategy for tenant dissolution with a focus on minimizing disruption and providing users with options.
In a multi-tenant system, deleting a tenant can have significant implications for its users.
When presenting data to users, accuracy and clarity are paramount. This post addresses a recent adjustment made to improve the transparency of data displayed within our application, specifically concerning aggregated statistics.
Initially, our application displayed aggregate counts of items, such as commits and code reviews, with the label
During a recent update, we encountered an issue where partial failures during data synchronization could lead to data loss. This post details the problem and the solution implemented to ensure data integrity.
Our application relies on synchronizing data from an external source. The synchronization process involves fetching and updating various data points.
We've recently refactored and optimized our AI token usage tracking to improve performance and maintainability. This involved extracting duplicated queries and enhancing user filtering.
The primary focus was on improving the efficiency of retrieving daily and monthly tenant AI usage data. This was achieved through two key changes:
In the realm of automated content creation, achieving variety and maintaining engagement are key challenges. This post explores a technique for enhancing the dynamism of auto-generated posts by introducing an element of randomization into the content selection process.
Automatically generating posts can become repetitive if the
This post discusses a recent update to our post generation process, shifting from hardcoded sections to a more adaptable, example-driven approach.
Previously, our post generation system rigidly enforced a predefined structure: Introduction, Development, Examples, and Conclusion. This inflexible format ignored the nuances and varied structures of different example posts,
When integrating multiple payment providers into an application, managing the transition and allowing for flexibility becomes crucial. This post explores how to introduce an abstraction layer combined with feature flags to handle different payment providers, such as Stripe and Paddle.
Directly integrating a payment gateway like Stripe can tightly couple the payment logic within
Recent development efforts have focused on enriching the quoting module within our application. These enhancements streamline the user experience and improve overall functionality by introducing autocomplete capabilities, refined matching algorithms, and integrated conversation features.
The addition of autocomplete significantly
We recently optimized a background job responsible for post-generation in our application, specifically focusing on how it handles premium access checks. Initially, the job was configured to check user-level premium access, which led to inefficiencies. This post outlines the problem, the solution, and the benefits we observed.
