Alice Sionne

I was laid off (redundancy). Instead of freezing, I started building. Shipped my first app: TrustedMetrics, a verified creator performance ID that helps creators prove results, build trust with brands, and get hired faster. Quick peek: trusted-metrics.com Want to shape it? Join the founding user spots to test early + influence the roadmap. Reply FOUNDING (or DM) and I’ll set you up + send the onboarding. Why I built it: creators waste hours proving numbers across platforms. TrustedMetrics makes it fast to share + easy for brands to verify, without spreadsheets, or messy back-and-forth. Watching someone close to me vibecode pushed me to stop overthinking and start shipping 👀 Learning fast + building in public. I’m Alice, a marketing & comms person who builds frameworks + systems. This is my proof-of-work era: ship small, measure, iterate. Founding users get: early access, direct input on features, priority support, + a “Founding User” badge on your profile. If you’re a creator who needs “proof that travels,” reply FOUNDING. Trust should be easy to prove — and easy to verify.

@HaoranTang0907 Nice. Following along 👍🏾

@AliceReveHaut Thank you and I’m going to share the whole process here!

Day 1 building a zero-fluff app for artists. 🎨 Tired of 2-week "polite" emails just to check budgets? Me too. Vibe coding an anti-networking app for artists 🚫 No DMs 👀 Portfolio first 📅 Direct booking Shipped the core style of UI today. 👇 #buildinpublic #vibecoding #indiedev

@lancit96 @aditiitwt Fair but don’t you think vibe coding by nature pushes people into fast mvps and shipping quickly which can also lead to more things being abandoned?

@AliceReveHaut @aditiitwt Too many disasters and failure

AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER AI WONT MAKE YOU A DEVELOPER STILL VIBE CODING?

@Repovault This is honestly a bit scary. As a new builder this is the kind of thing you don’t even realize you might be exposing.

scanned 10+ repos today and every single one had at least one exposed secret or open endpoint most devs don't even know repovault.co — free scan, no account needed #buildinpublic #vibecoding #security #indiedev

@fidasp__ More on the vibe coder side but I’m realizing understanding the logic still matters a lot.

Real talk... which developer are you in 2026? 👇 Traditional Dev → writes every line, owns the logic Vibe Coder → prompts the AI, ships 10x faster No wrong answers. The industry is split 50/50 on this 😅 Which side are you on? #VibeCoding #AI #Developer #CodeLife

@letsflipgold It really does. The tricky part is making sure those “days of work” actually hold up 😅

Vibecoding feels like spell casting... I've just done days worth of work in an hour.

@fidasp__ Feels like it’s less about killing jobs and more about changing what “junior” even means.

#VibeCoding #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering #WebDev #AI #SoftwareEngineering

@leoobai I’ve been seeing this everywhere lately. Curious to understand why.

OpenClaw is blowing up in China 🤯 What is it *really*—and why is everyone talking about it? Here’s the simple version. #VibeCoding #AI #Coding

@RemcoAI This. As a non-dev, frontend is where things feel the most fragile. You fix one thing and something else breaks

This is cool. Untill today front end has been a bottleneck for vibecoding. The models are too inconsistent. They improve one part of the site but screw up another part. Hopefully this wil fix it

@TheDemianRex99 I feel this. Some days it’s just about showing up for even 1–2 hours. Still counts.

Reality hits hard. Vacations are over, worked 9-7 today and I had almost no energy, I was depleted. Still managed to do 2 hrs of "vibecoding" with OpenCode and the new MiMo model. I wish my country had unemployment.

@five_fortress Feels like it’s moving from generate code to orchestrate everything around it. Less about one-shot code, more about connecting systems.

imo the next stage of vibecoding isn’t Claude code one shotting your code but a platform that uses Claude code to one shot your code and connects all the other platforms as well

@pulseon_dev @sama @nytimes This. Writing the code is becoming easier. Deciding what actually matters to build is still the hard part.

@sama thanked developers right as @nytimes declared coding dead. The bottleneck was never writing the code. It was always knowing what to ship. #vibecoding

@keinEntwickler I see what you mean. At the same time, vibe coding is what made building accessible for people with no coding background.

Using AI as a tool is not vibe coding. There is a big difference. I think it is good that Apple pushes back on this. Time to put real craft into apps again. I want to use good software not AI slop. #indiedev #vibecoding #iosdev #buildinpublic

@lancit96 @aditiitwt Why?

@aditiitwt Vibecoding is dead

@michal_ptacnik This is interesting. As someone new to building, this is the part you don’t really think about at the start. You focus on getting something working then realize there’s a whole layer of risk / compliance behind it.

Legal agents belong in your CI/CD. Vibe Coding compliance means automated privacy and licensing checks every deploy. Stop letting legal bottleneck production. Embed guardrails into the dev workflow. Follow for daily clarity. #VibeCoding #LegalOps #DevOps

@AndrewYNg @Oracle @richmondalake This is really interesting. Memory is usually one of the missing pieces for making agents actually useful over time.

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with @Oracle and taught by @richmondalake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time! deeplearning.ai/short-courses/…

@arvidkahl I try to be quite strict with it. Otherwise it takes over everything.

Do you have a healthy relationship with email?

@marclou Love seeing more of this. Looking forward to what people build with it.

Very nice initiative! Creem is opening bounties (scops) for its developers to build on top of its API. Creem X DataFast might come earlier than expected 😇

@thejustinwelsh I’m just starting this shift after leaving my last role. Not chasing $10M just building something that gives me more freedom than a job did. Still early, still messy but I can already see the path.

The most successful solopreneurs aren't scaling to $10M. They're simply making more than they did at their job, minus the boss, meetings, and headaches.

@svpino Still I agree starting with spreadsheets is one of the best ways to understand your business before automating.

I run every one of my businesses off spreadsheets. It's kind of ridiculous at this point, but I'm used to doing this, and it works for me. I have a bunch of Claude Code skills to manage everything, but I'd love to have an agent that 100% specializes in Excel. This is very promising!