This post discusses a recent update to our post generation process, shifting from hardcoded sections to a more adaptable, example-driven approach.

The Old 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,

Introduction

This post addresses an issue where a billing system, specifically when using a service like Cashier, fails to correctly identify active subscriptions beyond the default type. We'll explore the problem and provide a solution to ensure all subscription types are properly recognized.

The Problem: Default Subscription Type Bias

In many billing systems, especially those utilizing

Introduction

Our application relies on the AutoSyncGeneratePostJob to synchronize data. Recently, we encountered issues with exceeding the rate limits imposed by Azure, leading to job failures and data inconsistencies. To address this, we implemented rate-limiting middleware specifically for this job.

The Problem

The AutoSyncGeneratePostJob frequently triggered requests to Azure services.