• 3 Posts
  • 529 Comments
Joined 3 years ago
cake
Cake day: September 25th, 2023

help-circle


  • crontab, it’s enough to :

    • kill any add during specific period
    • accumulate usage per app
    • check if tabs are opened

    and it’s pretty straighforward to configure, e.g.

    * 8-17 * * 1-5 killall SlayTheSpire && date >> ~/shame
    # prevents from playing during weekday working hours
    

    or for accumulation (which can be reset daily, weekly, etc by simply deleting the minutes file)

    pgrep mpv && >> mpv_minutes; if [ $(wc -l mpv_minutes) -gt 1000 ]; then echo beyond threshold; fi
    

    That works also for turning up/down network interfaces.

    PS: I use this on myself. I’m not a child but I don’t have perfect self control. It works.













  • Yes, I didn’t know the expression “local rewrites” but that seems to capture it well.

    My bet it’s another version of the inverse of Not Invented Here https://en.wikipedia.org/wiki/Not_invented_here where the IT department or a random manager claims that whatever was generated is “theirs” implying agency. They don’t realize that each iteration will get harder and more expensive (bigger context window) while alternatives have accumulated thousands and thousands of “bugs” or even just usage highlighted limits of their implementation. So they are re-inventing their version at great cost and in the end the difference between what they worked on is basically equivalent of open source equivalents but with no community support and instead a dependency on models and infrastructure they don’t own.


  • Maybe but that wasn’t my point. My point is that a lot of people now invest a LOT of resources, being token, money, time, etc to invent the wheel again. Instead of relying on e.g. Drupal they’ll “generate” yet another CMS which will work (for a while, in theory) not because it’s a good idea (IMHO it’s not) but because it’s been marketed as doable and even “better” on some aspects (e.g. customizable).





  • I agree with everything you wrote but I’m not sure how it helps clarify what I said earlier. So… I think we agree?

    On your final point I think the big difference between then (before LLMs) and now is that until recently a very demanding PR, in the sense that the person asking for the merge would have a good idea yet didn’t really get something about the project and thus needed a lot of guidance, it was seen as an investment. It was a risky bet, maybe that person would just leave after a lengthy discussion, maybe they’d move to their own project, etc… but a bit like with a young intern, the person from the project managing that PR was betting that it was worth spending time on it. They were maybe hoping to get some code they themselves didn’t have the expertise on (say some very specific optimization for very specific hardware they didn’t have) or that this new person would one day soon become a more involved contributor. So there was an understanding that yes it would be a challenging process but both parties would benefit from it.

    Now I believe the situation has changed. The code submitted might actually be good, maybe not. It will though always, on the surface, look plausible because that’s exactly what LLM have been trained for, for code or otherwise, to “look” realistic in their context.

    So… I would argue that it’s this dynamic that has change, from the hope of onboarding a new person on a project to a 1-shot gamble.