• 143 Posts
  • 631 Comments
Joined 1 year ago
cake
Cake day: April 4th, 2025

help-circle




  • They’ll keep doing that, over and over. And it usually ends up with them insisting on a meeting to “discuss” where they essentially get in a loop of “it’ll work, just do it”

    And it’s like pulling fucking teeth to get them to admit the only thing they’re basing that on, is a chatbot told them it would work.

    Strange. I am experiencing the same. In one case, I had to make, after six months of discussing an interface, an end-to-end test to show it didn’t work and their, ahem, unit tests failed to show that. That was for a stepper motor interface and driver with three essential methods.

    This guy is senior software architect at my workplace.

    Boss insisting that I get to an agreement with him on ai usage.








  • I don’t know if the last part “What do these software developers actually do all day? ;->” is ironique or not.

    It is actually a mix of two things:

    1. Ironic about the idea of what AI companies promote - and many managers in tech believe - that you can speed up the work of developers by speeding up code generation. The fact that typing in code costs way less than 0.1% of developers work time shows that the time to type in code is /not/ the bottleneck.

    2. Interested in what it is actually that costs time. I think most time I work on larger projects is reading code and trying to understand how different parts are related, what invariants it has, etc. It is actually a form of /learning/ because it uses material to build a useful long-term collection of related concepts in my brain.

    Anything that’d help us to do and understand the second part better would be extremely useful for this work. I think that literate programming, also tools that can transparently put code into a form of interconnected hypertext (like the LEO editor), inline doc tests and so on, are helpful for that.

    Personally, I also think that wikis like gollum are powerful tools for that kind of learning, but not many people seem to agree with this (except the fossil and forejo authors).







  • Two ways:

    1. Say you want to rename the files Sevilla_big{number}.jpg to Sevilla_small{number}.jpg:

    in bash, using the extglob option:

     shopt -s extglob
    for f in pics/**/Sevilla_big*.jpg
    do 
         mv "${f}" "${f/big/small/}"
    done
    

    (If you want to type it in a single line, you need to add semicolons as separators.)

    The ‘"’ are only needed if file names contain whitespaces.

    1. Using find:

      find . -name ‘Sevilla.*big.jpg’ > t

      now, you edit the file named “t” with Emacs or vim so that you duplicate the file names, modify them as you want, and copy them using the copy-rectangle command right to the collumn with the original names. (Vim also offers this functionality, it is super useful to learn!) Delete any names of files you don’t want to change. save the result to t.

    Then, in bash:

     <t while read a b; do mv $a $b; done
    

    Alternatively, you could also insert the mv command as a first collumn in t, save t and do:

    source t
    

    This variant wouldn’t work with spaces in filenames.

    1. Bonus option:

    Use the mmv command