Show HN: Superglue – OSS integration tool that understands your legacy systems https://ift.tt/W0gEUSY

Show HN: Superglue – OSS integration tool that understands your legacy systems If you've ever worked in a large company, you've probably encountered "shadow infrastructure": scripts nobody understands or custom connectors written once and never touched again. This glue layer isn't documented, isn't owned by anyone, and tends to break when systems are upgraded or someone leaves. It's also the part everybody dreads working on, because it's hard to understand, painful to work with, and full of unknown unknowns. We built superglue so that engineers stop wasting time on deciphering legacy APIs and documentation. superglue ingests existing glue code, SQL, configs, docs, OpenAPI specs and reverse-engineers what the system is actually doing. It then maps dependencies and regenerates everything as clean javascript code that can run directly or be exposed via MCP or SDK. It also monitors API changes and schema drift, and automatically repairs integrations when upstream systems change. In short: It turns legacy integrations into code you can easily understand, test, and update. So that engineers can do more exciting feature work, and companies can migrate and upgrade systems faster. Think of it as: a context engine + code generator + integration runtime for legacy glue. What we'd love feedback on - How do you deal with "nobody knows what this script does" situations? - What would you want to know about your legacy systems? OSS/community version: https://ift.tt/SulCXoR More info: https://superglue.ai Happy to go deeper on the technical details. https://superglue.ai November 25, 2025 at 09:58PM

Show HN: I built an interactive HN Simulator https://ift.tt/0shvW83

Show HN: I built an interactive HN Simulator Hey HN! Just for fun, I built an interactive Hacker News Simulator. You can submit text posts and links, just like the real HN. But on HN Simulator, all of the comments are generated by LLMs + generate instantly. The best way to use it (IMHO) is to submit a text post or a curl-able URL here: https://news.ysimulator.run/submit . You don't need an account to post. When you do that, various prompts will be built from a library of commenter archetypes, moods, and shapes. The AI commenters will actually respond to your text post and/or submitted link. I really wanted it to feel real, and I think the project mostly delivers on that. When I was developing it, I kept getting confused between which tab was the "real" HN and which was the simulator, and accidentally submitted some junk to HN. (Sorry dang and team – I did clean up after myself). The app itself is built with Node + Express + Postgres, and all of the inference runs on Replicate. Speaking of Replicate, they generously loaded me up with some free credits for the inference – so shoutout to the team there. The most technically interesting part of the app is how the comments work. You can read more about it here, as well as explore all of the available archetypes, moods, and shapes that get combined into prompts: https://news.ysimulator.run/comments.html I hope you all have as much fun playing with it as I did making it! https://news.ysimulator.run/news November 24, 2025 at 11:22PM

Show HN: Runbooks – Shareable Claude Code Sessions https://ift.tt/81GBrUg

Show HN: Runbooks – Shareable Claude Code Sessions When we asked developers from large engineering teams, almost everyone is using Claude Code, Cursor, or Copilot. But adoption is still inconsistent. Some of us would have 15 agents running in Claude Code at the same time; some would still refuse to use any of them and write code manually. There's a fragmented AI development problem: - Five developers building similar features, and all of them start from scratch - No way to share "here's how we prompt AI to follow our architecture" - No trail of how the AI changes were generated - People leave the company, so does the their knowledge Aviator is a developer productivity platform with tools like MergeQueue, Stacked PRs, Releases ( https://ift.tt/Ozf9xGQ ). Runbooks came from watching our own team and our customers struggle with fragmented AI adoption. With Runbooks 1. Create executable specs - Plan (with AI) that captures intent, constraints, and steps before AI touches code 2. Version control everything - Specs, AI conversations, and generated changes are all versioned. Fork, improve, roll back 3. Make it multiplayer - Multiple engineers collaborate in the same AI coding session. 4. Build a template library - Migrate one test from Enzyme to React Testing library → use that Runbook to batch migrate the entire test suite. We're not replacing Claude Code or Cursor. Runbooks is powered by Claude Code. We’re just making it work at team scale. -- Explore our prebuilt template from our open-source library: https://ift.tt/S03nh9N Templates cover migrations, refactoring, and modernization. They're code-agnostic starting points that generate Runbooks using your code context. Docs and quickstart: https://ift.tt/Mv5eHDE -- About the name: Yes, we know "runbooks" makes you think incident management. But technically a runbook is just a documented, step-by-step procedure—which is exactly what these are for AI agents. We're keeping it! Happy to get feedback, answer questions about architecture, context management, sandboxes. https://ift.tt/8yRl4PJ November 25, 2025 at 12:09AM

Show HN: I built an interactive map of jobs at top AI companies https://ift.tt/xBIrzgi

Show HN: I built an interactive map of jobs at top AI companies I built a live interactive map that shows where top AI companies hire around the world. I collected this data for a hackathon project. Many ATS providers have a public API that you can hit with the slug of the companies to get open jobs. The hardest part was finding the companies. I tried Firecrawl but it returned around 200 companies per provider which wasn’t enough for me. Then, I tried SERPAPI but it was expensive. I ended up using SearXNG to discover companies by ATS type and fetch their job postings. This produced a large dataset of 200k+ jobs (I only use a subset as it would have taken too much time processing). A few days ago, I decided to build a visualization of the data as I didn’t know what to do with it and wanted people to benefit. I kept catching myself wanting to ask simple questions like “show only research roles in Europe” or “filter for remote SWE positions” (and had plenty of free ai credits) so I added a small LLM interface that translates natural language into filters on the map. The map is built with Vite + React + Mapbox. Live demo: https://map.stapply.ai GitHub (data): https://ift.tt/EQhyitR Would love feedback, ideas for improvement, or contributions. https://map.stapply.ai November 24, 2025 at 11:38PM

Show HN: Search tool for "Ask HN: What Are You Working On?" https://ift.tt/wKXjZD4

Show HN: Search tool for "Ask HN: What Are You Working On?" Hi all, I created a public dashboard for searching / chatting with "What are you working on?" posts. I'd love to hear any feedback that you have. https://ift.tt/tvCBfyU November 23, 2025 at 10:52PM

Show HN: Makefiles, Metalanguages, Matrioshka Automata https://ift.tt/xjbZ2qS

Show HN: Makefiles, Metalanguages, Matrioshka Automata Immediately buried last time, so reposting for your lazy Sunday. This project is a strange labor of love, practically guaranteed to inspire horror and delight. It's also tough to summarize. Partly it's very practical and involves familiar tools, but part of it is also a new programming language with esolang roots. I'll start with the practical and move towards the peculiar. The one-sentence summary: compose.mk brings docker-fluency, polyglots, and a capable standard library to Makefiles. A more in-depth elevator pitch from the main landing page is below, and some related links at the end in footnotes 1-5. > Meet compose.mk, a tool / library / framework for Makefile-based automation, scripting, and lightweight orchestration. Native support for docker, docker-compose, workflow primitives, JSON IO, TUI elements, and more, all provided by a single file with no dependencies beyond what's already in your development environment. Typical use-cases include general project automation, especially decoupling your CI/CD from different kinds of platform lock-in. Other superpowers include the ability to quickly incorporate foreign tools and foreign code as first-class objects, which provides unique and powerful capabilities for quickly assembling console applications, systems prototyping, and component-oriented design experiments in general. Definitely not the Makefiles of your ancestors. Here's where it starts to get more weird and fun. Building the ideal environment for zero-dependency automation and pesky "glue code" moves in a certain direction. So it happens that compose.mk moonlights as an interpreter / compiler / packaging tool for a new kind of programming language. CMK-lang (or just CMK) is multiparadigm with diverse influences, from functional to concatenative, ultimately specializing in things like extensibility, interoperability, DAGs, and dispatch. CMK is a superset of Makefile that can be transpiled to vanilla Makefile. And it is what is known as a matrioshka language. Paraphrasing the definition from esolangs-wiki: > A matrioshka language is formed by bundling one or more meta-languages with one or more language descriptions. They can be identified by their program forms, which have multiple, distinct 'phases' with different syntactic and semantic rules. There are often two phases; the first gives a set of rules, and the second provides objects on which those rules are to be applied. In CMK-lang, matrioshka "objects" are things like container-runtimes or foreign interpreters, and "rules" are DAGs in the form of tasks, task-groups, or foreign code. For those interested in matrioshkas and topics in PLT, I suggest the alternate landing pages at footnotes 6-9. Love it or hate it, I think you'll agree that compose.mk is easily the biggest, baddest, most highly powered mutant Makefile the world has ever seen. If it helps you can think of CMK-lang as a PoC that's waiting for another back-end implementation ;) Playing around with it has convinced me though that the gap is real, and the world really needs containers-first matrioshka languages that work locally, and aren't tightly coupled to bulky remote platforms or infrastructure. It also needs languages that are capable of aggressively reusing and recombining existing code and existing tools. [1]: https://robot-wranglers.github.io/compose.mk/standard-lib [2]: https://robot-wranglers.github.io/compose.mk/bridge [3]: https://robot-wranglers.github.io/compose.mk/container-dispa... [4]: https://robot-wranglers.github.io/compose.mk/demos/polyglots [5]: https://robot-wranglers.github.io/compose.mk/json [6]: https://robot-wranglers.github.io/compose.mk/matrioshka [7]: https://robot-wranglers.github.io/compose.mk/language [8]: https://robot-wranglers.github.io/compose.mk/compiler [9]: https://robot-wranglers.github.io/compose.mk/demos/packaging https://robot-wranglers.github.io/compose.mk/ November 23, 2025 at 09:55PM

Show HN: RealDeed – Tokenize Real Estate into Digital Assets https://ift.tt/xXinsAz

Show HN: RealDeed – Tokenize Real Estate into Digital Assets RealDeed is MENA’s advanced real estate tokenization platform, licensed under the Dubai International Financial Centre (DIFC). Our mission is simple: Make real estate “digitally alive” without forcing property owners or developers into securities, fundraising, or STO regulations on day one. Real estate globally is still stuck in PDFs, local land offices, and offline processes. Tokenization exists, but almost all solutions jump straight into securities, fractionalization, investor pooling, and STOs, which triggers regulation and makes experimentation nearly impossible. We built RealDeed because property owners kept asking us the same question: “Can I put my real estate on blockchain as a digital twin without selling ownership or offering securities?” So that’s exactly what we built. Today, we’re launching the RealDeed — a platform that turns physical real estate into digital assets or twins, represented as utility tokens pegged to land area. What RealDeed Actually Does :. RealDeed allows property owners and developers to: 1. Upload property documents Title deed, floor plan, DLD or RERA documents, etc. 2. Verify ownership KYC + property verification. 3. Define a tokenization model Example: 32 sqm → 320,000 utility tokens 120 sqm → 1,200,000 tokens Tokens represent digital land, not ownership. 4. Mint the digital twin on-chain We generate tokens on XRP Ledger & EVM networks. 5. Deliver tokens to the owner’s Web3 wallet 6. Optional integrations Where legally allowed, owners can connect their digital twins to: Broker-dealer platforms DeFi platforms Fintech apps Metaverse/spatial systems Partner proptech tools RealDeed creates the first interoperable property layer on blockchain where: A Dubai villa A Mumbai apartment A London flat …can all exist as standardized digital twins—usable across APIs, developer tools, and digital ecosystems. This enables: Global property mapping Unified digital registries Digital twin trading like gift deed and selling tokens(not property trading) Cross-border developer collaboration Blockchains finally have a way to “understand” property. Regulatory Positioning RealDeed is:Licensed under DIFC Innovation Licence (PropTech/DLT & Tokenization) (we don’t do financial services) Not a securities platform Not selling tokens Not accepting public funds Not fractional ownership Think of us as “Stripe for property tokenization.” Founded by Malhar Jajoo & Pratz (Prathmesh) Try It / Join the Waitlist realdeed.co https://ift.tt/J3dyYDL November 23, 2025 at 02:16AM