@FullstackT17204
Account based inUnited States!
About this account
- Account based in
- United States
- Connected via
- India App Store
X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
The Software Guy
Bengaluru
Joined January 2024
- Tweets81
- Following530
- Followers5
- Likes71
Parthiban Subramani retweeted
This is about to go crazy for vibe coders
Introducing e2e
The agentic testing framework for any app
~/ npx e2e init
→ Fully Open Source
→ Mix deterministic and agentic APIs
→ Supports web, mobile, and more
→ Bring your own agent and infrastructure
→ Run locally or in CI
tester.army/e2e
Parthiban Subramani retweeted
ChatGPT Sol is remarkable. For 1-2 days I was disappointed, but then I read one of the published prompts of OpenAI, and then we used something similar for our most exciting open problem. And Sol made the same breakthrough that Fable had made earlier! And now it is progressing further. It is now at 11 hour runtime, still working. We hope to finally crack the problem.
Parthiban Subramani retweeted
Just finished reading "Domain Modelling Made Functional" by @ScottWlaschin.
As promised, my full review of the book.
If I can recommend one book about understanding how to model real-world problems with Functional Programming, it'll be this book.
If you want to kill two rabbits with one shot: learn FP and Domain-Driven Design (DDD) - just read this book.
If you want to learn F# - just read this book.
If you want to learn FP architecture - you guessed it right - just read this book.
I love how the book is structured around a single real-world project example and it covers lots of different problems:
1. Communicating tech design to non-tech people
2. Modeling the domain
3. Modelling external dependencies
4. Testing
5. Error handling
6. Evolving the design
7. Talking to 3rd parties
8. Talking to the database
9. Data persistence
10. Serialisation vs Persistence
11. And so much more!
What's even more interesting is how it's all connected to functional programming.
Honestly, if after this book you're not convinced that FP is awesome for writing enterprise software, I'm not sure you've actually read the book.
The book uses F# but it looks almost exactly like OCaml, so I didn't have troubles reading the code at all. Honestly, I don't think anyone would have troubles because the book also gently introduces all F# concepts along the way, so I consider it a very accessible intro.
I'm not a fan of particular approaches introduced in the book. Like the usage of Higher-Order Functions for Inversion of Control to achieve mocking for the easier tests. I hate mocks and prefer another way. But in the context of this book it makes sense, and the way it was introduced, I don't hate it too much.
However, I specifically want to highlight attention to detail and countless examples. When writing real-world software, Software Engineers always consider alternatives and trade-offs. Besides, the system's design is not static, new requirements constantly arrive. So I really like how this book often considers potential changes to the design and addresses corresponding changes to the code.
I want to end at the start of the book. One of the strongest book intros I've seen. Scott immediately starts with hard facts, so you don't have illusions about what Software Engineers actually do.
10/10, I recommend it to everyone.
Today we're releasing a new set of components for building chat interfaces.
We've taken the patterns we build every day, rethought the abstractions behind them, and turned them into components you can compose and customize.
We're starting with the conversation layer: streaming, scrolling, messages, bubbles, attachments, and markers.
What Makes a Great Streaming Chat Experience
Start here: Never move the reader against their intent.
1. Move only when the reader asked to move.
If someone is reading, don’t pull them somewhere else. Auto-scroll should never be the default.
2. Follow only while they’re following.
If they’re at the live edge, keep the stream in view. If they scroll away, leave them there.
3. Every interaction is intent.
Scrolling is not the only signal. Selecting text, using the keyboard, opening a link, searching should all stop the interface from moving.
4. Start a new turn near the top of the viewport.
This gives the new turn somewhere it can be read from the beginning.
5. Then stream in the answer.
The streaming answer can then grow into the available space.
6. Keep part of the previous conversation in context.
Enough of the previous turn should remain visible so the reader knows where they are. Context.
7. Let new content arrive offscreen.
The conversation can keep streaming without changing what the reader is looking at.
8. Show what’s happening out of view.
Make it clear when a response is still streaming or when new messages have arrived.
9. Make it easy to return to the latest reply.
A "Jump to latest" action should bring the reader back and resume following.
10. Let people jump anywhere in the conversation.
Long threads need message links, search, unread markers, and direct navigation.
11. Reopen where the reader left off.
A saved conversation should open at the last meaningful turn. This is usually the last user message. Not the absolute bottom.
12. Keep the reader’s place when layout changes.
Images load. Markdown expands. Code blocks render. Older messages appear above. None of that should make the reader lose their place.
13. Handle interruptions without stealing position.
Stopping, retrying, regenerating, branching, or errors should not unexpectedly move the conversation.
14. Stay responsive in long threads.
Streaming text, markdown, code, images, and long history should still feel responsive.
15. Be accessible without the noise.
Keep the transcript navigable, preserve keyboard focus, and announce important events at a comfortable pace.
It’s all about the scroll. Scroll Engineering.
Parthiban Subramani retweeted
We’re open-sourcing Unlimited OCR — built to read long documents in one pass.
With 3B total parameters and only 500M activated, Unlimited OCR sets new end-to-end SOTA results on OmniDocBench v1.5 and v1.6.
The key innovation is Reference Sliding Window Attention (R-SWA), inspired by how humans transcribe books: keeping the source, recent context, and next words in focus, while softly forgetting what’s no longer needed.
With constant KV Cache size and lower attention cost, Unlimited OCR can transcribe 40+ pages in a single forward pass — without losing context or slowing down.
Explore the model👇:
--GitHub: github.com/baidu/Unlimited-O…
--Hugging Face: huggingface.co/baidu/Unlimit…
Parthiban Subramani retweeted
/goal refactor until you are happy with the architecture. ensure you live test after each significant step and autoreview/commit. track progress in /tmp/refactor-{projectname}.md
Parthiban Subramani retweeted
I love how open the Codex app is, you can run any model you want, even local.
These are the only configs you need to use the app with Gemma 4 via Ollama.
Parthiban Subramani retweeted
Watch me control my computer with just my voice. This is the future of operating systems.
No hands.
GPT-Realtime 2.0 is very, very underrated.
Demo:
Parthiban Subramani retweeted
We've created the world's fastest PDF parser ⚡️
And it's more accurate than any other open-source, model-free PDF parser out there (pymupdf, pypdf, markitdown, pdftotext, opendataloader, pymupdf4llm)
Introducing LiteParse v2 - we rewrote the entire library into Rust and adapted it as native packages for Python and Node.
It supports 50+ different document types, can be triggered directly or installable directly within your favorite AI agent.
Blog: llamaindex.ai/blog/liteparse…
Repo: github.com/run-llama/litepar…
LiteParse v2.0 is out now, and it is blazing fast + runs everywhere!
We rewrote everything from scratch in Rust, and now:
- up to 100x faster parsing
- install natively in Rust, JS/TS, and Python
- a custom WASM package enables browser and edge runtime usage
pip install liteparse
npm i ＠llamaindex/liteparse
npm i ＠llamaindex/liteparse-wasm
cargo install liteparse
Blog: llamaindex.ai/blog/liteparse…
Repo: github.com/run-llama/litepar…
Parthiban Subramani retweeted
Anthropic onboarding day: Michael Scott introducing Karpathy like he just signed Wemby in free agency.
Parthiban Subramani retweeted
Cloudflare's security team spent the last few weeks testing Anthropic's Mythos against fifty of our own repositories. What we learned about offensive AI, why faster patching is the wrong reaction, and what the architecture around vulnerabilities has to look like next. cfl.re/49BRUqW
Parthiban Subramani retweeted
some random ai thoughts:
- for code, i went from 80/20 claude/gpt to 80/20 gpt/claude in <3 months. surprised by this tbh, and interested to see where the split is at in another 3mo.
- claude still mogs gpt for non-coding agent stuff. codex feels like an engineer (which is great for coding!), whereas claude still feels like a general purpose coworker. gpt still lacks that coworker magic
- i’m pretty meh on opus 4.7. my experience hasn’t been *bad*, but it certainly hasn’t been good. sideways if anything.
- anthropic has got to figure out the compute thing. you can feel it as a user. vibes are all out of whack bc of it. my opinions above are all likely downstream of this. it’s an issue.
- anthropic labs continues to be the goat of ai product. claude design is another hit. it’s fantastic. idk why it’s not talked about more? a+
- updated claude code app is great. i finally switched out of the terminal for it. very well done.
- how are people STILL sleeping on the claude agent sdk? i feel like i’m going insane.
- gpt 5.5 is incredible. the level to which i trust it for engineering is amazing. if i could only have one model rn, it would be this one just bc of strong need for the coding use case.
- codex team is killing it. app has been the gold standard since 5.3 release (buuut i credit conductor team for the ui innovation that everyone is using now). though i could do with a little less passive aggressive shots at ant from the codex team. TARS, dial up class by 30%. it’s a long race guys haha
- i uninstalled cursor this month and am now back to vs code for my ide. composer just can’t hang with claude/gpt, and the product feels a bit all over the place. pretty stoked about the xai thing though, because their team is absolutely stacked and i’m excited to see what they might be able to do with that compute. codex and claude code are t1, cursor is t2. i would love if this deal got xai/cursor to t1 for a real trio there.
- gemini…? seems like this is 2-3 models now where the model seems like a great release and then nobody ever uses it? i’m bullish google/deepmind but weird it hasn’t translated to product use in any form. kinda disappointed still
- no open source models have hit the opus 4.5 level. was hopeful the new deepseek would get there, but nope. good oss agents will have to wait a few more months it would seem…
Parthiban Subramani retweeted
introducing Claude Doctor
1. reads your ~/.claude to find where claude keeps messing up
2. writes rules for your CLAUDE.md so it stops.
npx claude-doctor
Parthiban Subramani retweeted
Today we're excited to announce NO_FLICKER mode for Claude Code in the terminal
It uses an experimental new renderer that we're excited about. The renderer is early and has tradeoffs, but already we've found that most internal users prefer it over the old renderer. It also supports mouse events (yes, in a terminal).
Try it: CLAUDE_CODE_NO_FLICKER=1 claude
