← 021 - Canceling a Project 023 - Something Else Than Saas→
In this episode of Debugging Dan, I share my updates from the past two weeks, focusing on my progress with dan cuts, a video enhancement tool I'm developing for social media. I've been dedicating significant time to this project. I discuss various upcoming features for dan cuts, including workflow automation, video trimming, and integrating Sentry for error tracking. Additionally, I touch on my plans for content creation, consistent social media posting, and revitalizing my website to better showcase my projects.
Episode 22 already of the Debugging Dan podcast.
So I changed things around in my recording setup. So I used to be sitting on my chair at my desk with a green screen behind me. I, as you saw last week, I had issues with lighting. It didn't feel right. I wasn't demotivated because of that. And today I thought outside the box. I remembered something. I need more space. I need more depth on my desk. So I figured, why don't I just record from the side of my desk? So I have, I'm standing right now. My, I put my desk in standing position. The green screen is behind me. It's like fully folded. It doesn't need to be wide. It's just a proper height. I have enough space on my desk. It's just that I need to move everything around and rotate it 90 degrees when I'm recording, but that's okay. I feel that I have a lot of more energy because of this, because I'm now more happier about the setup.
Get it done episode six. So short recap, what I do with the get it done themed episodes. I record an episode every two weeks, and then I decide by planning for the next two weeks to keep myself accountable, to share things, to show what I'm working on. And this is episode six. I'm going to normally do, I do a recap towards episode five. So that's what we're doing. Four topics are on the list.
The first is dan-cuts, which is the video editing software that I'm working on. It's not really editing. It's more enhancing for social. I've worked on that a lot, like almost every evening, every weekend. Every morning for the past two weeks, and I made a lot of progress, but the project is big, too big, probably, but I'm enjoying it. I wanted to do more with my socials and building with den cuts relates to that. And when I made this list, I figured, well, dan cuts, it's not that much of work. Once I get that done, I'll be, it will be easier to share clips and other interesting facts and things on social. I did that for last week's episode. So I shared some videos, the introduction, some other stuff.
And the third item is content. So I wanted to create more content and by doing more content creations, I want to do a way of working. So when I've recorded the podcast, I create a blog post out of it. But maybe I can do more. So I wanted to explore that and spoiler alert. I haven't done anything of that because I've been working mostly on den cuts.
And the fourth item is build. I wanted to progress on the first version of the robots, a TST tool. So robots against AI was that. And if you've seen last week's episode, I decided to can that project. So I'm not building on robots against AI anymore, because I figured out the short summary is that it's not solving my own problem. It's an interesting technical idea that I had that solves somebody else's problem. But since it doesn't solve my problem, I don't really have any motivate intrinsic motivation to work on it. So I decided to can it and focus more on things that solve my problems and thereby hopefully solve other people's problems.
That's what I did for the past two weeks. So it's been mostly building on den cuts. It's a technical challenge. I like technical challenges. I've been building mostly on den cuts and I'm enjoying that and I'm getting it to a state where it works. So we're related to den cuts. I'll be doing it.
This is the homepage after you've logged in into den cuts. It's not really that amazing. I still need to figure out what I want to show there. There's a telegram link. I've switched to a demo account to show you what that looks like. So when you need to link to telegram, you can scan that QR code, or you can enter a number manually and that will link your telegram account to your den cut. I've built it. I already had built that for watcher numbers. So it was pretty easy to copy paste. I did need to adapt it to work with Next.js because the watcher numbers thing was on express. So server actions, but it worked pretty well and I'm pretty happy about the flow.
This is the telegram conversation window with the bot that I built. So when you press start here, it shows a W text of this time. It's the watcher numbers platform, but I download a file and when I type a caption with the file, that one is copied over into the application. And it uploads and then you receive a link towards the media processing step. So sending a file via telegram now makes it available here in the media tab. So here I have the introduction and there's output here and I can view the video file. And there's an issue there. Probably need to remove that. Something went wrong there. So as you just saw, parsing the input from telegram didn't work correctly.
I've also encountered that during development and to be able to test more faster, I also created to create new media for my URL. So what I did is I used ng-rock and I started a small web server in the folder where the file is. So now I can tell, thank God to download media from a URL. So now it's here. So now instead of via telegram, I now have it via file download.
Oh, the status, it says is still running. I can view the details here. It's still downloading. That's what it's saying, but it might be that there was an error. It's not that big of a file download. It might be that there was an error. It's not that big of a file, like 20 megabytes, but it's not there. I made a switch from the prediction environment that I created to my local environment because some things weren't working correctly. But now I can at least show you the working stuff. So there's a file uploaded. I can add an action and there I configure the input of a different step as input. And I can, for example, after downloading the video, I can extract the audio. Then I can give a command to transcribe the audio. And I just need to do the configuration and it can run.
And I will be creating different steps, different operations that you can perform on audio or video to manipulate the video. So here I transcribe the audio and I then use that transcription to generate a text overlay over the video. That's nice to look at. So in the example here, the UI isn't that perfect. It's a client interface, but it doesn't always automatically update the data. So it doesn't show the latest status. I'm aware of that. And at the moment, that's okay. The interface is working. It does what it does. And I just press refresh once in a while.
I do want to upgrade the interface at some point to react flow, to have a graphical interface where you can drag and drop and link different tasks to each other. That is what I have until now. So what I'm wanting to do to put a bow in it and say that it's done for now. So then I will be able to dog food it. I'll be focusing more on some other stuff after I finish these four steps. So I want to be able to prepare specific flows. For example, when I upload a clip of the introduction of my podcast, I want to tell it to execute these steps and those steps are fixed. So I want to have that prepared and just say trigger it so that I don't have to build it manually each time. That's an important one.
I want to be able to trim the video because maybe I make a weird face during the recording at the end. That's always useful to have and it's pretty simple to build. I want to add Sentry support and for people that don't know what Sentry is, Sentry is a piece of software that you can use to track errors and performance of your application. They have a generous free tier that I've been using for years for my applications and it helps me get insight in when other people are using it or when I myself are using it that errors are being triggered. I can have a look at that asynchronously. That's a tool that I always enjoy using.
I've installed an open source like version of it. It's called Glitchtip, which does the error tracking and a simple version of performance tracking, but you can host it yourself. I've hosted it on my own server and you can use the Sentry SDK to point to that server and it implements the same API, but it's a very simple version of it. But then you don't get into any free tier issues and other problems. That's what I've installed and I'm trying to see if that would help me because I've been with the number of applications that I have. I've been exceeding the free tier stuff for Sentry. Some projects I might migrate to Glitchtip, maybe all. It depends on how it goes.
The fourth item is I want to be able to crop a video. The video that I've recorded now, for example, is landscape with some social media like Instagram Reels, YouTube Shorts, TikTok. The videos are either square or portrait. This video is pretty simple to make square. I just cut off this part. I've been pointing at my camera, but it's not really that part, but it's the left and the right part of the video because all the interesting stuff is often always at the center. We're able to do it smart, so maybe it can detect the video and outline the perfect square within a still, for example, by detecting a face, something like that. I've been looking into a piece of software or an NPM module that does that. That might also be interesting to see if that works.
Related to Get It Done 6, these are the four items. It's not necessarily four always, but this is what fits for me, I guess, for the next two weeks. I want to finish what I just explained. These items are running the prepared flows, trimming the videos, adding Sentry, and cropping to square. That's what I want to finish to be able to also move on because there's also other interesting stuff that needs to be done. Also, for the last two weeks, I've been burning it pretty hard, so maybe I need to slow down a little.
For socials, what I notice is that if I don't tell myself when I need to do that, I won't easily post on social. I want to create a schedule. For example, I published this on Sunday. On Monday in the afternoon, I published the introduction on social. Then on Wednesday, I create some kind of clip and share that on social, for example. Then on Friday, a recap of the podcast episode and then sending out a tease for Sunday, something like that. That's what I want to create so that I can just remind myself, hey, it's now Wednesday, I need to do this. It's now Thursday, I need to do this.
For content, I'm keeping this one, so I want to define the way of working for how I create content. What I want to share, how to generate it, and how to create it, basically. Also, the fourth item is I want to update my DebuggingDan.com homepage or the entire webpage. Now, it's generated by my Notion blog software, which I'm only using privately, which is pretty okay, but it's really focused on the blog. I want to create a better homepage that also shows tools that I'm building, like the products that I have, but also some free tools that I'm building. I want to be able to highlight that more.
What I'm going to do is I'm going to also extend an API in Notion blog so that I can fetch items from a newly to build Dext.js website for DebuggingDan.com. I can do the blog, but I can also do the other stuff. So, yeah, that's what I want to build so I can make the website more lively and also express the other things that I'm working on.
I'm also doing some open source projects. This weekend, I created a CLI tool to manage Telegram bots. For Telegram bots, you need to set a Webhook URL. You need to sometimes see what the contents of the message is as how it's sent. I've been building that this weekend because I've been using that also for DanCuts because I'm using Telegram there. I also want to highlight that kind of stuff on the webpage.
That's it for the next two weeks. I haven't decided yet what the topic will be for next week. I might be explaining something on problems I ran into with using Telegram for DanCuts in terms of file size and other quirks that I wasn't aware of for Telegram. I might make it more general, like building on third-party platforms and dependencies and risks that aren't there. For example, building on X and Elon Musk removing API access, which happened two years ago. But if you have a specific topic, let me know so you can reach me on social or other platforms. I'd like to hear from listeners or viewers. Have a nice day.