
Head of Developer Growth at @ActianCorp. Prev @Massive_Com @Box. I make developer content with a focus on AI. Views are my own.
Austin, TX
Joined January 2021
- Tweets243
- Following150
- Followers131
- Likes272
Alex Novotny retweeted
We grew a Pi 5 agent's memory 100x, to 100,000 vectors. Median recall moved from 1.90 ms to 4.17 ms. A 2.2x cost for 100x the data, all on the board 🫡
Alex Novotny retweeted
Is this the best way to build self-evolving agents with GPT-6 Astra?
Astra has a 1.05 million-token context window that resets with every new session.
We gave it an external memory. It stores every verified fix, and Astra checks that memory before touching new code.
Watch this before building an agent workflow with GPT-6 Astra! bki.sh/QwKTRsI
Alex Novotny retweeted
5 things that happened in AI infrastructure last week that'll affect how you build.
1️⃣ The agent loop is becoming its own infrastructure layer. What you build on top of it matters more than which model sits inside it.
2️⃣ Vector search alone can't handle production agent workloads. An agent that gets an exact lookup wrong loses the user. Hybrid retrieval fixes that.
3️⃣ Several vendors shipped disk-based indexes this week. If cost and memory weren't in your infrastructure decision before, they should be now.
4️⃣ Agents that place calls and touch codebases are surfacing a question teams haven't answered yet: who owns the data trail those agents leave behind?
5️⃣ Air-gapped facilities, regulated networks, and disconnected environments can't run cloud-hosted agents. If that's your deployment environment, your infrastructure shortlist just got shorter.
What are you watching out for this week?
I'm 35.
Developer Advocate from a place called Oklahoma. Currently based in Austin.
Looking to connect with more software developers, developer advocates & people building with AI. 🤠
+1 if you play boards too. ♟️
I can barely get my Tesla to miss a pothole on the road, and IMHO thats the closest thing to real world AGI we have right now. I think we are fine. Everyone needs to chill out.
Alex Novotny retweeted
Thanks @andre_z.
We respect what the @qdrant_engine team has built. Their API is clean and deliberate. We made our API compatible because it’s a standard developers already know. Low friction, easy migration, better for the whole space.
But under the hood, VectorAI DB is fundamentally different. We’re running on Actian edge database technology, a battle-tested database engine with decades of maturity, paired with our own indexing orchestration. The performance gains we quoted are from standard benchmarks like VectorDBBench.
We’re here for the engineering conversation.
Replying to @ActianCorp
@ActianCorp launched a vector DB. Their comparison post says it's 22x faster than Qdrant.
I was curious what they'd built, so I opened the docs...
Core concepts: Collections, points, vectors, payload... Wait. I know it from somewhere. 🤔
Alex Novotny retweeted
A write up of some recent work we did @massive_com to tag 8-K filings using an LLM pipeline. Probably the most interesting learning was that asking LLMs for a quality score of their own tag was terribly calibrated, but using a fresh context call did much better!
Why does he look like cottage cheese as a person? 😂
Introducing Aidan, your newest AI employee
Aidan is the first computer-using AI built for realtime conversation
We’ve raised $45M from @sequoia and @8VC to bring Aidan to the world
@NotionHQ and @DecagonAI already use Aidan to run customer interactions. This is how @sablehq works:
Alex Novotny retweeted
Earnings aren't coin flips.
@earnings_watch built a platform to prove it, on Massive data and 1,000+ options traders use it daily.
Here are the Massive products they use:
→ Options Contracts + snapshots power the earnings simulator and VolScanner
→ Fair Market Value cleans up the rankings
→ Stocks Aggregates drive post-earnings drift analysis
One API pattern across every tool. No mismatched data between screening, simulating, and analyzing.
Read more in the case study.
massive.com/blog/case-study-…
Anyone else try making a pet 🦉 in ChatGPT? Here's mine. I think he's pretty cute? What do you think? I'm such a sucker for adorable little guys like this, even if I used up all my Codex usage to make him. 🫠
GPT 5.6 Sol ☀️ did really well here too. 👏
😲🤯Another day another model release.
Just tested GPT-5.6 Sol on the new @massive_com Remote MCP Server with this monster query…
Using the massive (pun intended) Massive data, it analyzed the latest FOMC rate decision’s impact on QQQ + options:
- 1-min QQQ bars from 30 min before the statement to 90 min after the press conference
- One liquid 25-45 DTE expiration
- ATM call/put + ~5% OTM call/put
- Price & volume reaction, bid-ask spreads, IV changes, downside skew, gamma exposure
- Statement vs press conference: which one actually moved the market more?
- Plus the exact graphs requested
No code. No manual data pulls. Just one prompt → full professional-grade event study in seconds complete with a graph. 📈📊
Woah 🤯 I connected @spacexai's Grok 4.5 to @massive_com using their new remote MCP server - asked it to analyze @Tesla performance and create a powerpoint with the results. Did it all in under two minutes. Pretty blown away by this. This is just the tip of iceberg too. I haven't even tried my hard queries yet.
Alex Novotny retweeted
Without accurate stock market data, Claude guesses or makes data up.
That is where Massive comes in.
Here Claude Sonnet 5 is querying major memory stocks over the last year. It correctly uses the Massive Market Data connector, builds a chart and provides an easy to read overview of everything related to the historic run up.
All it took was a quick install and simple prompt.
Connect Claude to the market now.
It was a short trading week due to the holiday tomorrow, but it was a roller coaster of a ride? Anyone buy $SPCX?
Alex Novotny retweeted
Checkout this LULD monitor if you need real-time awareness of volatility guardrails across U.S. equities.
This example connects to Massive's stock WebSocket feed and subscribes to LULD events. It shows upper and lower price bands, indicator codes, tape, timestamps, and sequence numbers, then turns the raw feed into a monitor that is easier to read under market pressure.
The practical pattern is selective and high signal: show routine band updates for a watchlist, while surfacing halt and resumption indicators across the market. Indicators 17 and 18 are available for Nasdaq-listed securities, so the copy and example keep that scope explicit.
massive.com/blog/luld-massiv…
Thanks @RobinhoodApp for my entire one whole $SPCX share. History has been made. ✔️ 😂
It is wild what you can see when actually start looking at the data. 👀
The $25,000 day-trading minimum is gone.
As of today, June 4, FINRA's Rule 4210 amendment retires the Pattern Day Trader rule and its $25,000 minimum.
So we measured what that barrier actually cost. Using 5-minute bars for every S&P 500 ticker across every May session, we scanned for each 2%+ intraday round trip a day trader could have caught.
Our analysis flagged 4,679 potential trade opportunities. Under the old rule, a PDT-restricted trader could have only taken 12 of them, about .3% of the total.
Now that the limit is gone, we may see much broader market participation.
Dig into the relevant OHLCV data using our aggregates endpoint: massive.com/docs/rest/stocks…























