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."

It’s not perfect, and I appreciate those of you who tried out the original PMM-plugin (would appreciate the feedback from that). TLDR (AI summarised): Shipped the rewritten Poor Man’s Memory harness — now works across both Claude Code and opencode (Kimi K2.5, Gemini Pro/Flash) from the same project. Choose the model that fits the task, keep the memory. Tested in a multi-user Telegram channel holding concurrent 1:1 threaded conversations without cross-contamination. Previously validated switching between codebases mid-session. Link: github.com/NominexHQ/pmm-harness-dist Looking for early feedback and bug reports. Also built an agentic skill-porting suite between Claude Code and opencode as the first serious test of the rewrite. — The original plugin was Claude code only and worked well for me when I needed to switch beteeen code, CLI and Cowork (and between models) while retaining its memory. I tested it in a multi user environment (a telegram channel) and it held up holding multiple 1:1 individual threaded discussions with users a single group without straying. I had already been using it to switch between different codebases in a single session. So I had the suspicion it would hold up in such noisy environments. I just could test it until I implemented the telegram integration. This next one allows me to run my memory in opencode (where I run kimi-k2.5, Gemini pro and Gemini Flash) and Claude code from the same project. I get to choose which models or apps untike suits what I’m working on at any given moment. Would appreciate some early feedback and bug reports. I’ve been occupied rewriting Vera for opencode and realised I needed a plugin that allows me to analyse and port skills and plugins between the two. Writing the agentic suite for doing this was my first serious test of the rewritten PMM implementation.

You just saw how video production turns into code. Vote below, then tell us in the comments: what is one repetitive creative task in your work that could become a pipeline?