I'm currently building a free, agent-native (Merchant & Affiliate side) Affiliate Management Platform and would love to know what you are looking for, when choosing a Platform.
For one as marketers, running the program.
But also for the marketers - what's important for you, when joining a platform?
Would love to get some input from you guys.
I'm currently building a free, agent-native (Merchant & Affiliate side) Affiliate Management Platform and would love to know what you are looking for, when choosing a Platform.
For one as marketers, running the program.
But also for the marketers - what's important for you, when joining a platform?
Would love to get some input from you guys.
Just came back from napoli and my extension got approved in the store.
Built a free Chrome extension because my YouTube Watch Later and playlists kept turning into messy long list of links.
I watch a lot of educational videos, tutorials, interviews, and longer podcasts. The problem was not saving videos. The problem was finding the useful ideas again later.
Really like the idea of using transcripts for AI Summaries, but what I was always missing is, bundling together 20+ videos and generate a collective summary for all of them together, extracting the most important infos from them.
So I made AI Organizer: a small Chrome extension that lets you save YouTube videos into a separate library in Chrome's side panel, organize them into collections, search them later, and generate summaries when transcripts are available. It can also summarize a whole collection of videos, not just one video at a time.
I am also working on shared collections, so multiple people can build and manage a YouTube video collection together.
I just published it to the Chrome Web Store and would love honest feedback from people who save too many YouTube videos and actually want to use them later.
It's completely free, for all the organizing things. AI summaries are limited for obvious reasons.
Link: https://www.aivideoorganizer.com/
Extension: https://chromewebstore.google.com/detail/ai-organizer-for-youtube/ehhdndglhgchpigapgbljmkidmcnoebi
Curious what you think.
I am currently building a chrome extension for saving Youtube videos in a better way.
There is no reference to any specific youtube content.
And everytime Codex is testing something in playwright or whatever, he is fucking opening this, autoplaying the video lmao.
gg i guess
I finally completely switched over to Codex.
It's so damn freeing, to finally be able to work on many tasks again without the fear of running out of usage.
i've been working on 4 projects in parallel with 5.5 High & xHigh for over 20 minutes and and not a single percentage of my session limit is gone?
Big fucking ups to OpenAI!
I'm building a SaaS on Vercel + Supabase, and I ran into an issues that looks like a small production warning thing first, but turns into a useful architecture review once I actually pulled the thread and did a proper audit session.
The warning was around database connections. (random error when uploading small files)
The upload itself worked most of the time, but I saw a Supabase connection warning and the random errors in production and decided to dig into it.
It was more the usual SaaS stack adding up..
Individually, all of that is normal. Together, it can quietly become connection pressure.
With Vercel serverless + Supabase, you don’t just think in “is this query fast?” You also have to think in:
These are the types of things, probably most of vibe coders will miss completely and will cause the SaaS crashing, once you get actual users.
I am lucky to have some development background, so I managed to realise what's going on or rather where I have to dig.
It’s adding a few boring guardrails:
This was a good reminder that AI helps you create working vertical slices very quickly, and production architecture is about how all those slices behave together.
Caught early, this kind of review is actually a good thing. It means the product is getting past “does it work?” and into “does it keep working cleanly as usage grows?”
So for the love of god, don’t only check if your app works. Check how your app works.
Open the page and count the DB touches..
Look at what fires after hydration.
Look at your polling.
Look at your cron jobs.
Look at your Supabase pooler setup.
Look at whether your indexes match the actual queries.
Keep your system in check!
I'm building a SaaS on Vercel + Supabase, and I ran into an issues that looks like a small production warning thing first, but turns into a useful architecture review once I actually pulled the thread and did a proper audit session.
The warning was around database connections. (random error when uploading small files)
The upload itself worked most of the time, but I saw a Supabase connection warning and the random errors in production and decided to dig into it.
It was more the usual SaaS stack adding up:
Individually, all of that is normal. Together, it can quietly become connection pressure.
With Vercel serverless + Supabase, you don’t just think in “is this query fast?” You also have to think in:
These are the types of things, probably most of vibe coders will miss completely and will cause the SaaS crashing, once you get actual users.
I am lucky to have some development background, so I managed to realise what's going on or rather where I have to dig.
It’s adding a few boring guardrails:
This was a good reminder that AI helps you create working vertical slices very quickly, and production architecture is about how all those slices behave together.
Caught early, this kind of review is actually a good thing. It means the product is getting past “does it work?” and into “does it keep working cleanly as usage grows?”
So for the love of god, don’t only check if your app works. Check how your app works.
Open the page and count the DB touches.
Look at what fires after hydration.
Look at your polling.
Look at your cron jobs.
Look at your Supabase pooler setup.
Look at whether your indexes match the actual queries.
Keep your system in check!
I'm building a SaaS on Vercel + Supabase, and I ran into an issues that looks like a small production warning thing first, but turns into a useful architecture review once I actually pulled the thread and did a proper audit session.
The warning was around database connections. (random error when uploading small files)
The upload itself worked most of the time, but I saw a Supabase connection warning and the random errors in production and decided to dig into it.
It was more the usual SaaS stack adding up:
Individually, all of that is normal. Together, it can quietly become connection pressure.
With Vercel serverless + Supabase, you don’t just think in “is this query fast?” You also have to think in:
These are the types of things, probably most of vibe coders will miss completely and will cause the SaaS crashing, once you get actual users.
I am lucky to have some development background, so I managed to realise what's going on or rather where I have to dig.
It’s adding a few boring guardrails:
This was a good reminder that AI helps you create working vertical slices very quickly, and production architecture is about how all those slices behave together.
Caught early, this kind of review is actually a good thing. It means the product is getting past “does it work?” and into “does it keep working cleanly as usage grows?”
So for the love of god, don’t only check if your app works. Check how your app works.
Open the page and count the DB touches.
Look at what fires after hydration.
Look at your polling.
Look at your cron jobs.
Look at your Supabase pooler setup.
Look at whether your indexes match the actual queries.
Keep your system in check.
I switched to Codex, ever since the limits on Claude got absolutely wrecked and quality has been degrading.
I always kept 1-2 subscriptions with Claude, for counter checking implementation plans, which becomes less and less necessary now.
Nowadays, since I am also a web designer on the side - Claude Design is the only thing, where I want to keep at least a cheap subscription active with Claude.
I really hope OpenAI is working on something similar and generally make UI Design easier. If they release something like that, I don't think Anthropic will be much of a competition, unless they really change their usage policy or Mythos is actually as good as they say.
I'm tired of switching models, so I really hope it happens.
What's your opinion on it?
I am currently trying to build several social media channels.
Main focus is on LinkedIn and X.
My only problem is, that my crowd on LinkedIn and X is for one a different language and two, a different tone.
While LinkedIn is more professional and german, LinkedIn is more casual and all english.
I am wondering, if there is a tool, that allows me to crosspost to different social media channels, but have an AI prompt inbetween, that changes the "master"-post depending on the platform.
So I could write my LinkedIn posts in German and crosspost it to X, while the AI automatically writes it more casually and translates it to english. Maybe even with the option to make 3 different tweets from it
I am currently trying to build several social media channels.
Main focus is on LinkedIn and X.
My only problem is, that my crowd on LinkedIn and X is for one a different language and two, a different tone.
While LinkedIn is more professional and german, LinkedIn is more casual and all english.
I am wondering, if there is a tool, that allows me to crosspost to different social media channels, but have an AI prompt inbetween, that changes the "master"-post depending on the platform.
So I could write my LinkedIn posts in German and crosspost it to X, while the AI automatically writes it more casually and translates it to english. Maybe even with the option to make 3 different tweets from it