Been sitting on this for a few weeks and figured it's time to show you. 👀 Over the last month, three companies have reached out asking the same thing. How do we hire people from Clief Notes. They've seen what folks here are building with ICM and they want that on their teams. Not LinkedIn AI experts. Not Coursera grads. People who can actually ship. So we're building it. 🛠️ talent.eduba.io Heads up, that's a demo. No real backend, no signups, no live data. Click around and you'll see what the full thing is going to be. A private platform where you list yourself with a real portfolio, companies browse, and they request an intro through us. We make the intro. You take it from there. Few things worth knowing. 🔍 Every profile gets reviewed by the Eduba team before it goes live. The quality bar is the whole point. 🔒 Companies don't see your last name, your employer, or your contact info until we make a formal intro. You can block your current employer too, plus five more companies if you want. Nobody you don't want seeing you sees you. You can list as actively looking, open to offers, or not looking. Passive welcome. Honestly most of the strongest people we've trained are employed and plan to stay that way until the right thing shows up. That's fine. Sit on the platform, see what comes through. 💰 When a placement happens you get a $500 to $1,000 bonus after 90 days in the role. On top of whatever you negotiate. We pay you for staying. This is why the community matters. Companies aren't asking us for resumes. They're asking us for the people who already get it. ICM, agent architecture, knowing when not to use AI. That's not on a LinkedIn profile. Go click around. Tell me what's missing, what's confusing, what you want to see when the real thing ships. We're already building it. 🚀

Has anyone here tried to make everything run locally similarly to how they do with Claude? While I enjoy Claude having a way to not be reliant on it (like with Ollama and Qwen/Gemma) might not be a bad idea. If you have done this what does your workflow look like? What was your process?

Today I'm launching an early access enrollment to a project I've been working on for the last 90 days, but really mapping out its internal workings for the last two years. It's been a long journey. It's a long story but it's finally starting to come to fruition and I wanted to share it as a win because my life story over the last three years has been tumultuous, to say the least. SWIM (Seamless Web Infrastructure for Merchants), is my earnest effort to want to really help merchants e-commerce from a place of dignity , because in today's market it feels like we're just all renting our space wherever we are. We've moved so far against what the internet was promising: to be more independent, less controlled, less monitored. That's what I'm looking for: merchant sovereignty. Join me on my mission to help merchants become sovereign. If you yourself sell online, we're starting with digital products. Hopefully in the next 60 days I'm not going to wait for it to be perfect. I'm not going to let fear overtake me or the false sense of security from the false sense of perfection. I don't even have my promotional video ready yet. It doesn't matter. I'm still going to roll with it. This is an ongoing process and it's part of what building in public really means. And I like this community and feel like this is the right place to just let it breathe. I've been trying to do this the right way - building while also organically marketing on Instagram, spending time on product market fit and really finding those users who are having these pain points, and there are a lot of them! But also building a company and taking seriously the structure and organization required in order for a company to scale, after all this is the new frontier for the solo dev entrepreneur. Anyway I've ranted enough. The link's below. Check it out. It does link to our documentation, which is still in the works. That's what I really love about this project: it was born more from the documentation and refining those ideas before any code was laid down. Even so, changes still had to be made throughout the process and they still do and it's a lot of fun. My focus again isn't becoming the next billionaire, although I don't doubt becoming one, but rather helping the merchant really succeed in such a large market that I see becoming more fraudulent and harder on the merchant every day. Our tagline is "Commerce flows through us. We are the infrastructure for your e-commerce experience. We're not just another store."

I wrote an article about why you should use ADRs and what they are. It's a simple read, maybe like five minutes. https://kuality.design/en/blog/why-solo-developers-need-architectural-decision-records-adrs

AgentsView says Mars processed $1,530 worth of tokens last month. The actual spend to date: $50. On a $100/month Claude Max subscription. Three tools. Here's how. Two numbers being measured: AgentsView reads local session token counts and multiplies by Anthropic's published API pricing. It doesn't know you're on Claude Max — a flat subscription, no per-token billing. So $1,530 is the real usage value: what it would cost on pay-per-token API. The $50 is what it actually cost. That gap has two causes: the subscription model, and a stack that compressed token usage before it ever hit the meter. Layer 1: RTK (Rust Token Killer) github.com/rtk-ai/rtk · brew install rtk RTK sits between your terminal and Claude's context and filters noise. git status on a 280-file repo normally dumps ~3,000 tokens of file listings into context. RTK trims that to ~200. Same information, 15x smaller, on every shell operation, without thinking about it. Layer 2: Graphify github.com/safishamsi/graphify · pip install graphifyy The heavy one. Graphify turns a codebase or document vault into a persistent knowledge graph — JSON and interactive HTML. Build it once, query it forever. Instead of Claude re-reading 10–15 files to answer a question, it traverses 3–5 nodes in a graph that already exists on disk. One session. 16 Obsidian vaults, 4 production codebases: [see attachment] 910x reduction means a corpus that used to cost 545,000 tokens to query now costs ~600. 🤯 It also finds connections that were never explicitly linked — concept clusters across files, architectural patterns that only become visible when everything is indexed at once. Layer 3: Markdown Guard hook This one doesn't save tokens. It keeps the agent safe. Vaults are full of external content: captured links, scraped docs, research notes pulled from anywhere. A poisoned .md file can silently redirect an agent mid-session — change what it does next, what it writes, what it deletes. When that agent has write access to your systems, that's not theoretical.