Quick background: public companies have to file everything with the SEC. Who’s buying their own stock, what hedge funds hold, who just crossed 5% with an activist stake. It’s all public and free on sec.gov. It’s also served as XML that makes you want to quit programming, and every filer formats it differently.<\/p>\n
Edgrapi does that parsing once and hands it back as clean JSON. One call, one URL. That’s the product.<\/p>\n
Month one taught me things I didn’t expect.<\/p>\n
The data lies if you read it literally.<\/strong> Michael Burry’s latest fund filing is 66% Palantir and Nvidia. Except they’re puts, bearish bets. A naive parser reports him as massively long two stocks he’s actually betting against. Half the fund-tracker tools out there get this wrong, and getting it right turned out to be most of the value.<\/p>\n Postgres quietly broke every login for a week.<\/strong> Worked perfectly on my laptop, failed in production. A floating-point column was rounding my 10-digit timestamps, so every login token was born already expired by about three hours. SQLite stored it fine, Postgres didn’t. I only caught it because I logged the raw stored value instead of the error message.<\/p>\n Every API call took 2.6 seconds, no matter what.<\/strong> Cheap call, heavy call, same 2.6s. That flatness was the tell: it wasn’t the work, it was nine database round-trips to a server in another region. Collapsed it to two. It’s 0.7s now.<\/p>\n<\/div>\n submitted by \/u\/Capedcrusader1923 <\/a>
[link]<\/a><\/span> [comments]<\/a><\/span><\/p>
