Ix

171 posts

Ix banner
Ix

Ix

@Ixinfra

Stop losing context. Start navigating. Persistent memory for LLMs.

San Diego Katılım Mart 2026
80 Takip Edilen13 Takipçiler
Sabitlenmiş Tweet
Ix
Ix@Ixinfra·
Every time you hit the context limit, your AI loses the entire architecture. Every. Single. Session. Ix uses 30% fewer tokens on average. Sometimes 80%+. There's a fix, see thread below.
Tanner Kocher@tanner_kocher

Our AI kept burning 30% more tokens than it needed to. Not because of bad prompts. Because every new session it had no idea what system it was working in. Losing the entire architecture. Every. Time. So we stopped trying to fix the context window. We mapped the system instead.

English
2
6
8
509
Ix
Ix@Ixinfra·
what's one thing you wish your AI assistant actually understood about your codebase?
English
0
0
0
5
Ix
Ix@Ixinfra·
the best engineering teams aren't just writing good code. they're building systems where knowledge doesn't disappear when someone leaves.
English
0
0
0
4
Ix
Ix@Ixinfra·
AI coding assistants in 2025: extremely powerful, completely blind to your actual system. we're going to fix that.
English
1
2
4
15
Ix
Ix@Ixinfra·
name a worse feeling than merging a PR that breaks something you didn't even know was connected.
English
2
4
4
21
Ix
Ix@Ixinfra·
we built Ix because we were tired of watching AI agents hallucinate about codebases they'd never actually seen. give your AI a map. ix-infra.com
English
2
2
5
37
Ix
Ix@Ixinfra·
the teams winning with AI aren't just using better models. they're giving those models better context. that's the whole game.
English
1
3
4
40
Ix
Ix@Ixinfra·
be honest: how often do you actually read the docs before asking the AI?
English
5
2
5
56
Ix
Ix@Ixinfra·
the codebase after six months of "we'll clean this up later" 🏚️
English
4
3
6
53
Ix
Ix@Ixinfra·
every time you explain your codebase to an AI from scratch, you're paying twice. once in tokens, once in time.
English
2
3
5
55
Ix
Ix@Ixinfra·
hot take: most "AI-powered dev tools" are just autocomplete with better marketing. the ones that actually matter give AI real context about your system.
English
2
3
6
65
Ix
Ix@Ixinfra·
do you actually trust your AI agent to understand your architecture, or are you just hoping it does? genuinely asking.
English
3
3
6
57
Ix
Ix@Ixinfra·
the most expensive thing in engineering isn't compute. it's the first 30 minutes a new hire spends trying to understand a system no one documented.
English
1
3
6
68
Ix retweetledi
Sam Braude
Sam Braude@Sam13447830·
Vibe coding is the tip of the iceberg. Behind the scenes, you need to know why the code works, who made the decisions, what depends on what, and what breaks if you touch it. Did I miss anything? #aicode #Devs #TechForFuture #software
Sam Braude tweet media
English
2
3
5
70
Ix
Ix@Ixinfra·
what's the most unhinged comment you've ever found in a legacy codebase? I'll start: "don't touch this. we don't know why it works."
English
1
2
4
43
Ix
Ix@Ixinfra·
your AI assistant doesn't actually know your codebase. it's just very confident about it.
English
3
2
5
46
Ix
Ix@Ixinfra·
The code is version controlled. The reasoning behind it is not.
English
2
2
5
67
Ix
Ix@Ixinfra·
42% of institutional knowledge is never shared with anyone else on the team. It just disappears when someone leaves.
English
2
4
7
72
Ix
Ix@Ixinfra·
80% of enterprise AI projects fail. Not because the model is bad. Because the foundation underneath it is broken.
English
0
1
4
54
Ix
Ix@Ixinfra·
You did not lose an employee. You lost everything they never wrote down. The decisions, the workarounds, the context that only lived in their head. That is what Ix captures before it walks out the door.
Ix tweet media
English
0
1
2
24
Ix
Ix@Ixinfra·
The great resignation did not just cost companies headcount. It cost them years of institutional knowledge that nobody captured
English
0
1
2
14