[–] 11 points 5 months ago (1 child)

And directional radio towers ( https://en.wikipedia.org/wiki/AT%26T_Communications_(1984%E2%80%932010)#AT=&T_Long_Lines= ) and satellites. Both of which are wireless.

So yeh, wires have been used in establishing the internet. But wires are not a requirement for internet.

It's like rain can make things wet. But something being wet does not require rain.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (1 child)

    Yeh, fair question.
    Recently I built a Non Linear Editor for Vimeo VODs.
    The server downloads the VOD, extracts key frames using FFMPEG, allows the user to create a bunch of sections and where they get uploaded to, then FFMPEG does a stream copy to extract those sections, and then upload them.

    I knew all of that was possible. I had never done HTML5 video players, I had never spawned FFMPEG from typescript, there was a lot of html/CSS that I didn't have experience with.
    Previously, I would have passed on this work.

    But after defining a plugin system for source/destination (so it can be used with YouTube or whatever), and splitting each stage into workers, the code itself is fairly easy to evaluate.
    I didn't need to know how to get to the result, I just knew what shape the result should look like so I could drive the LLM, and then I just had to read the result and google anything I didn't understand.
    And ultimately, I don't really care "if it's good or not". The definition of "good" is that it works and is robust. Other than that, it's looking for code smells.

    I guess I am lucky that most of my work is "one and done" instead of long-term support.

  • source
  • parent
  • context
  • [–] 4 points 5 months ago (5 children)

    As a solo dev, Claude has moved me from a "code writing developer" to a "system making developer".

    Someone would come to me with a problem, I'd chew it over come up with a plan and execute it to the best of my ability. And I loved writing the code, solving the problems, learning new stuff, and ultimately seeing something I built get used and make other people's lives/jobs/whatever better.
    But many times I would come to the conclusion that it's beyond my skillset (or I could do it, but the sheer quantity of learning would mean I don't hit the deadline or that I wouldn't be confident in the result) and not take on the work - despite understanding the problem they want to solve.

    Now, someone comes to me with a problem and I either say "yeh, I can solve that. But let me dig into it a little first", or I say "I don't understand that enough to be able to design a solution for that".
    It's no longer beyond my skillset. I have to understand the problem presented, I have to understand what the users want, and I have to understand what the result is. From this, I can know what the code/architecture/frameworks/stack will probably look like.
    That's the first step of solving a programming problem.
    I don't necessarily have to know/learn exactly how to achieve it.
    It feels like I've gone from solo-dev to manager.
    Thankfully, I guess, I've done full-stack, k8s, native app development. So I have experience.

    Which brings me to my point:

    I spent a few minutes reading through the documentation to better understand how the Astro configuration worked.

    I've had this exact scenario.
    Then I point Claude to the docs, and then it "knows" how to solve the problem.
    I point Claude at the docs because I know the specific software can solve a part of my problem, because I have evaluated previously that it can.
    I don't necessarily know exactly what I'm looking for, or what exactly the answer is. I don't necessarily know the keywords to be able to find it on DDG.
    But Claude could probably suggest something, and I'll know what I'm looking for when I see it.
    I've even had Claude build it's own docs from a GitHub repo of docs because the actual API docs are trash (looking at you Vimeo).

    LLMs aren't smart. They are expensive to run. And they take a LOT of the fun and knowledge out of programming & development.
    But they are a tool.

  • source
  • [–] 0 points 5 months ago* (last edited 5 months ago)

    This is the kinda small script I use Claude for. So yeh, it's LLM generated. Downvote away.
    But I am terrible at writing bash scripts!

    #!/usr/bin/env bash
    # rename-episodes.sh — run inside the folder, or pass a directory as $1
    
    shopt -s nullglob
    cd "${1:-.}" || exit 1
    
    for f in *.mkv; do
        # Match: ... Season N ... Episode N - Title.mkv
        if [[ $f =~ Season\ ([0-9]+)\ Episode\ ([0-9]+)\ -\ (.+)\.mkv$ ]]; then
            season="${BASH_REMATCH[1]}"
            episode="${BASH_REMATCH[2]}"
            title="${BASH_REMATCH[3]}"
    
            # Zero-pad to two digits
            new=$(printf "S%02dE%02d - %s.mkv" "$season" "$episode" "$title")
    
            if [[ "$f" != "$new" ]]; then
                echo "mv: $f  ->  $new"
                # uncomment the next line to actually move the file
                # mv -n -- "$f" "$new"
            fi
        else
            echo "skip (no match): $f"
        fi
    done
    

    I've commented out the mv command so you can test/fiddle/play around with it without clobbering your files.

    Some notes from Claude:

    Two practical notes:
    If your files aren't all .mkv, change the glob (*.mkv) and the regex anchor accordingly, or loop over *.{mkv,mp4,avi}.
    This assumes the literal words "Season" and "Episode" appear. If your real filenames vary (e.g. "S1", "1x01", "Ep 1"), the regex needs adjusting


    Edit: I just realised that specifically file-rename is mentioned, and looks like you are getting appropriate help in other threads.

  • source
  • view more: ‹ prev next ›