• 0 Posts
  • 58 Comments
Joined 2 years ago
cake
Cake day: March 3rd, 2024

help-circle
  • someone was asking for a GUI, so not going to be an ffmpeg expert. likely the LLM would recommend ffmpeg anyway. plus you would run YOLO (or maybe CLIP) locally; it has been running on Android phones since 2020 at least. a Jupyter notebook would also give a quick and dirty GUI to visualize and document the solution. plus “motion detection” is probably not the full story, and any video will probably have artifacting that means you’d have to tune the motion detection algorithm or end up with a bunch of garbage artifacts/false positives in the end. also, sounds like the user isn’t looking for something long-running like Frigate. if the user isn’t familiar with Python and wants to do something downstream like sort the outputs or whatever, an LLM would help with that.

    sure, programmatically, it’s not a difficult problem, but like it or not it can be solved by someone without an advanced CS degree with an LLM precisely because the problem is easy. no easily ready solution exists, but that doesn’t mean it can’t be done. “just use ffmpeg” to someone like my dad who might have the know how to install Linux but isn’t a programmer isn’t exactly the simple advice it sounds like.





  • the first issue is familiar to me as my first laptop had this issue, while running Windows XP. the fans were going out and simply couldn’t move enough heat. the solution then that mostly worked was one of those laptop stands with fans built in. it worked most of the time, but a real solution might mean cleaning out the chassis and maybe replacing the fans.

    for the second, i didn’t really have trouble setting up the Nvidia drivers just following the docs. sorry if that isn’t helpful; i’m stuck with Nvidia for my ML/CUDA stuff.



  • honestly, the brag document is a great takeaway. so many times people will subtly or implicitly question documentation or refactors, and when shit hits the fan and the readability refactor or documentation or logging/tracing PR becomes the clincher in quickly resolving the issue i love calling it out. documenting those cases themselves as a way to sell documentation and code quality to others feels like an amazing idea (if not exactly a “brag document”)





  • honestly, where NixOS shines for me is in my homelab. i don’t always have time to fully document what i’m doing, but my NixOS config is code-as-documentation for when work burns all of my memories away and has a git log and conflict management so i can manage multiple systems that share common config.

    and once you find out you can have services run on systemd with syntax like services.jellyfin.enabled = true you’ll never want to go back to containers, although it has ways to manage those as well.

    it’s overall a great OS for tinkering and deploying small services across small networks. not sure how it scales, but for my use case it’s damn near perfect





  • man this brings back memories.

    i was able to install Arch on my 2012 Macbook Pro, but the networking was a huge issue. not only did the driver cause terrible screen tearing for some inexplicable reason, but i had the same problem even getting the dang thing installed. luckily i’m an Android developer and was able to share wifi over USB with an Android device.



  • no one has noticed

    nice. this is a detail that i needed to know that would otherwise be a dealbreaker.

    i am intrigued by the promises of better histories, since i’ve been reviewing and contributing to a bunch of repos at work.

    a lot easier to use

    see this is the issue. i don’t find git hard to use. and i’m not going to be one of those assholes that’s like “i never thought it was hard”; i’ve just genuinely been at this for over a decade now. and i run nushell so i’m not opposed to new niche things as long as it improves my workflow.

    i’ll have to check it out again.


  • i really want to get into jj cuz i like the pitch, but the real struggle isn’t new syntax or learning curve but the fact that my workflows at home and especially at work are built around git and GitOps. i tried briefly to integrate it into my dotfiles, but migrating such a large repository got a little hairy.

    is there a doc about why a seasoned pro (at least don’t tell my manager otherwise) would switch to jj? are people using this in production effectively? is there a world where i can integrate jj into existing git based workflows that interact seemlessly with other contributors using plain ole git?