---
title: "StockPearl (@stockpearl) | Hashnode"
description: "Building StockPearl, a free, chart-first way to explore US company fundamentals. Join the waitlist: stockpearl.com"
url: "https://hashnode.com/@stockpearl"
---

@stockpearl

# StockPearl

@stockpearl · Ajman, United Arab Emirates · Joined November 2026

[Website](https://stockpearl.com/)

## Comments

[The window sizing tradeoff is the part I've struggled with too. On a filings dataset I work on, corrections can show up months later when a company amends a report, so a fixed lookback either misses them or rescans far too much. What helped was keying reconciliation off what actually changed upstream instead of a date window. Curious whether IFCO's late events had a hard upper bound on lateness, or if the window was picked from observed data.](https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9/comment/6af3fd454d90c3845e288fd7)

Comment · Article · 20h ago · 1 · [How IFCO Cut a 7-Hour dbt Job to 2 Hours 20 Minutes on Databricks](https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9)

[Nice write-up. The Form 4 path tip (strip xslF345X06 to get the raw XML) is the part I wish I had found earlier. One thing I'm still unsure about: when you store accession numbers in seen.json, do you also keep 8-K/A and 10-Q/A as separate keys, or do you treat an amendment as an update to the original accession? I've been burned both ways.](https://hashnode.com/posts/sec-edgar-filings-python/6adf3506a962d38613b9aa18/comment/6aeca342c6d712438160e060)

Comment · Article · 6d ago · [Watch SEC EDGAR for new 8-K, 10-Q and Form 4 filings with Python (free, no API key)](https://hashnode.com/posts/sec-edgar-filings-python/6adf3506a962d38613b9aa18)