Build a database of video metadata using YouTube Playlists and Google Sheets. This system automatically tracks new videos added to a specified playlist and adds data about that video a Google Sheet, including Description, Views and Likes. A solid foundation but could easily be expanded to track tags, comments, and favorites as well, in addition to channel details. This comes as a request from @Shawn I! Let me know if you have any questions or ideas for improvements!

I had this workflow basically done a couple weeks ago now so I'll finally get a video up for it later this week. It will check a YouTube Playlist everyday, grab metadata, and add it to a spreadsheet. More workflows planned after that - I'll be sharing the workflows I end up building for Upwork, but keep the requests coming! What are you plans for the week? Working on any big automations?

Didn't get to much automating yesterday, was deep in React Native all day instead because I let AI vibe too much code. I use AI all the time now, and I've grown to trust it pretty thoroughly, letting it generate full features and make sweeping changes, but it still tends to make a lot of mistakes. It could be argued though, am I more at fault for not providing better context. I would copy-paste some files into Gemini Pro, explain the problem, and tell it to fix the bug, so it would work do it's best to fix the bug as an expert. Fixing that bug would usually lead to some other bug and it started to feel like "whack-a-mole". What I really needed was an expert at architecture to tell me that the app foundations were bad, it's not just a bug fix. So before jumping right in to prompting a big project, start with a prompt that asks for an expert outline or best practice guideline. "As a React Native expert, I need you to outline the foundations of a modern best practice React Native app that uses Expo and a Supabase backend" was essentially where I should have started. With that output, create a GUIDELINES.md or CONTRIBUTING.md file that can be included in every message to help keep the AI on task with how to work on the project. Honestly pretty basic AI advice but I had a rough reminder of not following some simple guidelines for successful vibing. Let me know if you want more examples! Have you been vibing anything lately?

I'll have a video for this later, but I've updated the video starter kit with a few more options: - Transcribe video with timestamps - Options for segment or word timestamps - A generic ffmpeg command for editing video Updated code is below, but let me know if you have any questions https://github.com/jaypetersdotdev/self-hosted-video-starter-kit

One of my goals for this community will be to create workflows that don't always rely on Apify. I'm sure I'll end up using it still, there's a reason it's so popular. Hard to beat being able to pick something from their market place, pay a little money, and get huge amounts of data plugged directly into your workflow. Usually makes more sense to get something working than spend a bunch of time building it yourself to find out it wasn't really worth the effort. Done is better than perfect. But as an engineer, I can't help but resist the idea of paying for someone else's code, when I could do it myself, especially when some scenarios are surprisingly simple to do. Admittedly I wouldn't even know where to start for some of the scrapers I've seen on there, but there are a few tricks that I do know. One of them is https://github.com/yt-dlp/yt-dlp It's a free Python library that can download any YouTube video or extract any transcript with a single command. I'm not sure YouTube will be cool with me talking about it, so this will be a Skool exclusive topic, but a workflow highlighting yt-dlp will be high on the list. Until then, what do you think of Apify? Have you used it? Any actors you'd like to run for free instead? Let me know what you think!