Comment

Comment on Honey, I Shrunk The Vids [Mr. Universe Edition] v1.0.5

Again, get off your high horse.

They just came out swinging, for no reason.

You already know how most self-hosted folks feel about vibe coding, or you wouldn’t have taken immediate offence to the initial comment (which ia valid, btw. You did not mark the project as vibe-coded or ai-assisted.) MARK YOUR PROJECT AS AI-ASSISTED.

Explain where you expect inefficiency and how I can fix it, and I will.

I’m looking to replace my cron-timed ffmpeg bash and ash scripts for encoding. Three of the four projects I looked at have double- and triple-work loops for work that should be done once.

And incidentally, the fact that this is a personal project I shared in case someone might find it useful is another reason that coming in here and throwing shade is a shitty thing to do.

Once again, I’m interested in the project, but I have my own thresholds of quality and security. If you can’t handle questions about your project, personal or not, then maybe don’t share it.

But why try to make me feel bad about it, because you don’t like the way I built it?

Sir/Madam, your feeling are your responsibility, not mine. I did not utter any pejoratives your way. Grow up.

source

Sort:hotnew top

obelisk_complex@piefed.ca ⁨1⁩ ⁨day⁩ ago
Hey, replying again so you get a separate reply message. So like I said, I went looking for redundant loops and I found quite a few, just like you described. There was also a minor performance issue with the logic that built the FFMPEG argument; it used a lot of unnecessary flags, each of which required fresh memory allocation. That would only be an issue in specific circumstances, like if you were encoding thousands of videos in quick succession… but that’s exactly the kind of issue you were talking about, so I asked for and implemented the fix.

It does seem snappier. I’m pushing 1.0.9, which has the fixes beyond what I found from your comments (like the argument construction issue), included. If there’s anything else you’d recommend I look at, I’m all ears.

source
- non_burglar@lemmy.world ⁨21⁩ ⁨hours⁩ ago
  Nice.
  
  The issues to look for are unnecessary logic (evaluating variables and conditions for no reason), and double sets of variables.
  
  One of the seasoned devs I work with said she encourages coders to transpose work at major inflection points, and this helps all devs gain an understanding of their own code. The technique is simply to rewrite/refactor the code in a new project manually, changing the names of the variables and arrays. The process forces one to identify where variables and actions are being used and how. It’s not very practical for very big projects, but anything under 1000 lines would benefit from it.
  
  Good luck.
  
  source
  - obelisk_complex@piefed.ca ⁨21⁩ ⁨hours⁩ ago
    That’s very similar to what I’ve been doing 😊 This project I think is on the cusp, a few of the files are over a thousand lines but it’s still kinda manageable. Comparatively, the PowerShell script I started with was far simpler. That one I actually did write most of it because I know how to get stuff done in PowerShell - just needed Claude’s help with the GUI.
    
    Also, I was thinking about your comment on performance when you’re looking at tens of thousands of runs - definitely not my original intent for this, I figured anyone doing that would just use CLI, but it’s totally possible with HISTV. I added an option to put files in /outputs, path relative to the input file, so you totally could just drag a top level folder info the queue, it’ll enumerate the media in all the subdirectories, and hit start. You’d get the transcoded files right next to the originals in your folder structure so they’re easy to find. Useful, I hope, when doing that many jobs.
    
    And thanks to your advice, it’ll do so a lot more efficiently. Like 5-6x lower resource usage, now. I really do appreciate the feedback, it’s exactly the kind of pointers I was hoping for when I posted this. I wish you’d come in to the comments outside my emotional response to someone else :P
    
    source
    non_burglar@lemmy.world ⁨20⁩ ⁨hours⁩ ago
    
    I wish you’d come in to the comments outside my emotional response to someone else :P
    
    I’m 50 yrs old now, but I used to react almost the same way you did, I understand where you’re coming from.
    
    I personally believe LLMs (and AI in general) can be great tools to help along with coding and similar tasks, we just don’t have a very good culture of their use yet.
    
    source
    -> View More Comments
obelisk_complex@piefed.ca ⁨1⁩ ⁨day⁩ ago

Again, get off your high horse

I’m on a high horse? You’re the one riding in here yelling at me for not conforming to your arbitrary rules I didn’t know about, and defending someone who did nothing but insult me.

You already know how most self-hosted folks feel about vibe coding, or you wouldn’t have taken immediate offence to the initial comment (which ia valid, btw. You did not mark the project as vibe-coded or ai-assisted.) MARK YOUR PROJECT AS AI-ASSISTED.

No, I don’t know any such thing, I took offense to the implication that there was no effort put into this, and the absolute absence of any constructive criticism whatsoever. And again, I didn’t agree to your rules, and I don’t owe you anything, so take you imperious commands somewhere else, thank you very much.

I’m looking to replace my cron-timed ffmpeg bash and ash scripts for encoding. Three of the four projects I looked at have double- and triple-work loops for work that should be done once. This seems to be a theme in vibe-coded projects.

See, this is something I can actually work with. I’m looking for places that unnecessary probes get spawned for example - there are some that are necessary for the way I want this thing to work, but there’s one just for audio data when previous probes already get that. A useful observation that resulted in an improvement. Thank you.

Once again, I’m interested in the project, but I have my own thresholds of quality and security. If you can’t handle questions about your project, personal or not, then maybe don’t share it.

First of all, I’m going to say this very clearly so maybe it gets through: I am not mad about questions. I am mad about insults and a lack of questions. Thank you for your attention to this matter 🤦 Next: Your thresholds are your responsibility, I didn’t know about them when I built this and I didn’t build it for you, I’m sharing it and you happened to stop by. I appreciate your observations on issues to watch out for when I’m using genAI code, I will be keeping an eye out for duplicated loops and other issues in future projects.

Sir/Madam, your feeling are your responsibility, not mine. I did not utter any pejoratives your way. Grow up.

You have a few things to learn about living in a civil society, based on how you treat strangers who are trying to learn. Grow up.

source
- hietsu@sopuli.xyz ⁨1⁩ ⁨day⁩ ago
  O-kay…so you chose this route. Not going to read any of these walls, but to answer your initial point, I was merely alluding that it would be nice to declare the use of LLM tools these days.
  
  And I too am a leet-full-stack-vibecoder but I rarely publish any of those tools other than for internal company use, always, ALWAYS, declare that the code is likely not fully verified/tested and never just say I did it. The tools work in my environment and test scenarios but might not in yours. I have seen how fragile the code/logic can sometimes be, perhaps not in this case, but who knows. And while things are getting better and better by each LLM release, it does not remove the importance of declaring the tools so people know what to expect.
  
  But of course people tend to publish these with the usual ”look what I made” for some reason… Guess it makes people feel special?
  
  source
  - obelisk_complex@piefed.ca ⁨21⁩ ⁨hours⁩ ago
    Hey, my ask if simple: if you find a problem, let me know so I can fix it. I already have implemented fixes based on other suggestions, even though the commenter was kind of a dick, and my application is better for it. You’re the one who swung in here with nothing to add except a snide remark trying to antagonise me. Again, I’m not expecting approbation (except for the name, that was mine and I like it), I just shared it in case it was useful to anyone else.
    
    If it doesn’t work on someone’s system, I want to know so I can fix it. If someone finds a bug I couldn’t, I want to fix it. I’m trying to learn - to read code better, but also technical project management. It sounds like you might be in or around technical projects yourself, so you know shipping something that works is actually quite a challenge. It’s an area I want to get some practical experience in.
    
    If there’s a discourse that everyone is supposed to label everything that involves genAI, then I haven’t been part of it. There was no memo, there are no rules in the sidebar, so you can’t expect everyone to just know to follow those guidelines.
    
    Finally, I don’t care if you read my other replies to other people. I was having an emotion about people piling on me, because I get enough of that shit at work, but here at least I get to speak in my defense, so I did. Do me a favour though and quit assuming things about my personality or how I think of my own skill set (I don’t think I’m any kind of coder, for one thing. I’m at best a warlock who read some wizard books but couldn’t even light a candle without his patron). So do you intend to engage with me in good faith, or were you just looking for a temporary punching bag?
    
    source