Tharun Josh

@CharlesPattson Unlock code?

The ability to prompt an image model well is a highly sought-after new skill. New tool in the mix 🔥 x.com/krea_ai/status…

@AxisBank is one of the worst banks for NRIs. They don’t care about their customers. Once you open NRO and NRE accounts with them and go abroad, their mobile app won’t recognise the mobile number you are sending SMS from. If you try to log in via net banking, it asks for a mobile app code. At this point, you are in a deadlock. All your funds are stuck in the bank but you can’t access them, and none of their customer support numbers work. Even with multiple people commenting on their videos since one year, they didn’t fix it. This shows they don’t care about their customers.

spent the weekend designing Jordon \u2014 a single home for your docs, memories, contacts, and AI agents. started from "I'm tired of hunting for files across 10 apps" and ended up here. an early peek at the Knowledge view.

Every hero section I've ever built: 1. Write font-size for desktop 2. Add @media query for tablet 3. Add @media query for mobile 4. Change the copy → redo all 3 5. Change the font → redo all 3 6. Client wants Japanese → cry I replaced all of that with 5 lines using @chenglou/pretext. It binary-searches the largest font size that fits your container. Pure math. Zero DOM reflows. Content-aware. Change the text → it just works. Resize → it just works. Any language → it just works. No more breakpoint font-size whack-a-mole.

The people who have this kind of obsession for providing / building great user experience will survive any era. The learnings from this product will eventually become founding stone for people who are building with AI as the expectations for better quality will rise in a few years. I really appreciate for building Mintlify so passionately.

Let me tell you why Mintlify needs 50 people to "host .md files" and why 50 is actually too low. I was the first intern at @mintlify. I sat three feet from Han and Hahnbee every single day. I watched this thing get built. People see docs.stripe. com and think "oh, markdown renderer." That's like looking at Google and saying "oh, a text box." Let me walk you through what's actually under the water. You want search? Not Cmd+K that returns garbage. Search that understands what a user means when they type "how do I authenticate." That's a whole retrieval pipeline. Embeddings. Ranking. Re-ranking. Edge caching so it feels instant in Tokyo and São Paulo. That alone is a team. You want self-updating docs? That means Mintlify is watching your codebase, detecting when your API changes, and flagging docs that are now lying to your users. Surprise! That's not a cron job anymore. That's diffing, parsing, mapping endpoints to prose, and doing it without false positives that destroy trust. That's another team. WYSIWYG editing? Sounds simple until you realize you're building a real-time collaborative editor that outputs clean MDX, not the garbage HTML that every rich text editor loves to produce. You're fighting ProseMirror. You're fighting the browser. You're fighting every edge case where someone pastes from Google Docs and injects 50 nested span tags. Hahnbee taught me everything I know about engineering in those wall, and half of what she taught me was how to wrestle with exactly this kind of problem. The type safety was less about being academic and more about survival. One wrong type and the editor breaks for 10,000 companies. Custom components? That means shipping a component library wuth interactive API playgrounds, code blocks with syntax highlighting for 60+ languages, tabbed containers, callouts, cards. BTW that has to render identically in the editor, in the build, in SSR, in the preview. Four rendering contexts. One source of truth. If you've ever tried to make a React component behave the same in SSR and client-side, you know that's a PhD thesis disguised as a feature. Authentication. Gated docs. Role-based access. SSO? That means Mintlify is now in the auth business, which means they're in the security business, which means SOC 2, pen testing, token rotation, session management. For docs. AI analytics. Not pageview counters. Understanding which docs are confusing users, which searches return nothing, where people rage-quit. That's event pipelines, ML models, and dashboards that have to make sense to a DevRel person who doesn't know what a funnel is. SEO/GEO. Mintlify doesn't just host your docs. They make your docs rank. Structured data. Sitemap generation. OpenGraph images generated on the fly. Meta tag optimization. Performance scores that stay green when you have 4,000 pages. That's infrastructure. MCP servers. CLI tooling. Content checks that lint your docs like ESLint lints your code. CMS for non-technical writers to ship without a deploy. And I'm not even going to get into the other hundred things. Versioning. Multi-language support. Custom domain provisioning with automatic SSL. Git sync that doesn't corrupt on merge conflicts. Preview deployments for every PR. Broken link detection across your entire site graph. Rate limiting on the API playground. WebSocket handling for real-time collaboration. OG image generation that actually respects your brand fonts. Middleware for custom routing logic. MDX compilation that doesn't choke on edge cases. Custom CSS injection without breaking the component tree. Cache invalidation, which, if you know, you know, across a globally distributed CDN. Each one of those is a rabbit hole. Each one has a person at Mintlify who has lost sleep over it. I watched founders of Mintlify obsess over this. @handotdev would be the last person to leave at night and the first person in the office the next morning. He'd find a 200ms latency spike in the build pipeline and lose sleep over it. I watched him rewrite the entire settings page once. He did it not because it was broken, but because a user had to think for two seconds about where a toggle lived. He tore the whole thing apart and rebuilt it so that every section, every label, every grouping made immediate spatial sense. You open it, you know exactly where everything is. No customer filed a ticket for that. The culture of Mintlify is refusing to ship anything that makes a user feel lost, even for a moment, even on a page most people visit once. @hahnbeelee was the same. Not only she taught me everything about Engineering I know today, she also taught me why things were built the way they were. Why this abstraction was chosen over that one. Why we don't take shortcuts even when the deadline is tomorrow. Every PR review was a lesson in caring about things that users would never consciously notice but would absolutely feel. We moved fast. Extremely fast. But we cared. A lot. About things most people would never see. The spacing between elements in the sidebar. The animation curve on the search modal. The way code blocks handle overflow on mobile. The fallback behavior when a component fails to render. They were less about building features and more about the difference between docs that feel like a product and docs that feel like an afterthought. "But why can't you just vibe code it?" You know who decided to use Mintlify instead of vibecoding? @cursor_ai uses Mintlify. @AnthropicAI uses Mintlify. @Lovable used Mintlify @twilio use Mintlify, @perplexity_ai uses Mintlify @Cloudflare use Mintlify These are the most technical, most demanding companies on earth. They could build their own docs. They have the engineers. They chose not to. Ask yourself why. It's because docs infrastructure is a bottomless pit of complexity that has nothing to do with your core product. Every hour your engineers spend fixing a broken sidebar link or debugging why your OpenGraph images aren't generating is an hour they're not shipping features. Mintlify makes that whole problem disappear. Vibe coding gets you a demo. It doesn't get you a system that serves 50 million page views without flinching. It doesn't get you an editor that 10,000 companies trust to not eat their content. It doesn't get you search that actually works. It doesn't get you infra that passes a SOC 2 audit. It doesn't get you the kind of reliability where Anthropic is comfortable pointing their entire developer ecosystem at your platform. Mintlify is the infrastructure that looks invisible when it's working, which is exactly why people underestimate it. "50 people to host .md files." No. 50 people to build the platform that the best companies in the world trust with the first thing their developers see. And honestly? 50 is actually too low.

Seedance 2.0 product review ugc for my wisdomcards.shop one shotted these 2. Not bad at all...

I built Agent Monitor — an open source desktop app that lets you run 20 Claude Code or Codex agents on one screen. The wild part: any agent can spawn, message, and coordinate other agents through MCP. Tell one agent "split this across 3 agents" and it actually does it. New nodes appear. They start working. Browser-style tabs per project. Full markdown chat. Session persistence. Drag-to-reorder grid. Built with Electron + React + Zustand. github.com/tharunkmr3/age…

@GeekyAkshat04 @BacLeodiv @X Let us connect message me, I cannot find message option on your profile

@Tharun1 @BacLeodiv @X Hey I am also into building and Saas Let's connect and grow together 🤝

@samsonA535 Please follow me

@PaulJun_ Can I talk to you please? I do all those I don’t have a portfolio to present but I have lots of projects, I can show. Give me 30 mins and I won’t disappoint you. Thank you.

I'm on the lookout for a builder, a T-shaped person who has deep mastery in brand design, building things (web and products), who has a learner's mindset and feels like their career is just beginning. Someone who is tired of the traditional brand design role in tech, who wants to work closely with various teams driving business outcomes, who wants to live on the frontier of AI. My team is working on things like the future of internal tooling, brand identity and systems, brand experiences (you get to work with my best bud @ItsJonHowell). We've already built multiple internal tools that can automate whitepapers, decks, and other assets. We're building things that don't exist yet. No official job description yet. Just looking to have conversations with people who wants to work with a team that's redefining the DNA and metabolism of a typical brand design team. Here's how I think how brand design is evolving: pauljun.substack.com/p/how-brand-de… Why I believe a point of view is more interesting than people who yap about taste: open.substack.com/pub/pauljun/p/… Why the future is about builders, small teams, that can own product develop, brand design, and the launch end to end: open.substack.com/pub/pauljun/p/…

@eglyman app.casandra.cloud Build this usability testing app

We only hire builders (and we’re on a hiring spree)! Reply with something you've built. I'll read them personally. We’re interviewing the best ones. You’ll be a good fit if you: - work best without permission - default to “how could I automate this” - had weird teenage hobbies - spend your sunday making side projects - have more Claude agents than cousins - shipped something this week - make prototypes, not powerpoints - don’t like hierarchy - are good at games: chess, monopoly, poker - would take dinner with Elon over $100k Good luck, Eric

Most companies think AI training = teaching ChatGPT prompts. The real skill gap? Knowing which business process to automate first. After training 100+ professionals, the #1 mistake is starting with the flashy use case instead of the painful one.

@samsonA535 hi

@katibmoe We need social media and ads campaign management for google, x, tiktok, reddit, meta, pintrest

Introducing One. The simplest way to connect and monitor AI agents to hundreds of apps. And we’re open-sourcing the world’s largest integration database powering it: 47,000 agentic actions across 250+ apps. RT + comment “One” for access & 1M free API requests/month.

Turned all 50 into a printable card deck. Box template included. Print at home in 30 minutes. 6829933558504.gumroad.com/l/wisdomcards

PEOPLE 31. Listen to understand, not respond 32. Show up consistently 33. Assume good intent 34. Apologise fully — not "sorry you felt that" 35. Invest in relationships before you need them 36. Praise publicly, criticise privately 37. People remember feelings, not words 38. Set boundaries kindly but firmly 39. Ask better questions 40. Call — don't text the important things

50 rules that changed my life. I turned them into a card deck. Here's the full list 🧵