• 11 Posts
  • 405 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

    Three things I can imagine:

    • Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
    • Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
    • It’s a bug in that Whoogle version.


  • What I don’t like about the genre, is that I’m bad at it. 🙃

    More seriously, I do find it kind of frustrating at times. Restarting ten times in a roguelike, no problem, because it’s always a new challenge.
    But if I miss the same jump ten times, or have to retry the same platforming passage ten times, you’ll see me getting impatient, which means I’ll fail the next ten attempts, too…


  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlDesigners cry quietly
    link
    fedilink
    arrow-up
    45
    arrow-down
    3
    ·
    5 days ago

    I, unfortunately, have to use GitHub at $DAYJOB and this is me. I navigate most of the webpage via the URL bar now.

    Basically, let’s say I’m working on a repo github.com/tomato/sauce/ and want to navigate to the Releases page.

    Via the webpage:

    1. Type github.com into the URL bar.
    2. Don’t find tomato/sauce/ in the list of recent repos, even though it’s the only repo I work on.
    3. Click on some other repo that’s at least in the tomato/ org.
    4. Navigate up to the tomato/ org.
    5. Find the sauce/ repo in the list.
    6. Traverse half the fucking screen to hit the “Releases” heading in the middle of the About-section.

    Via the Firefox URL bar:

    1. Type gi→t→s→r→.
    2. Hit Enter.

    I admit, it’s hard to compete with the latter, but I wouldn’t know how to navigate that way, if the former wasn’t so terrible.




  • Personally, I’ve found Poetry somewhat painful for developing medium-sized or larger applications (which I guess Python really isn’t made for to begin with, but yeah).

    Big problem is that its dependency resolution is probably a magnitude slower than it should be. Anytime we changed something about the dependencies, you’d wait for more than a minute on its verdict. Which is particularly painful, when you have to resolve version conflicts.

    Other big pain point is that it doesn’t support workspaces or multi-project builds or whatever you want to call them, so where you can have multiple related applications or libraries in the same repo and directly depending on each other, without needing to publish a version of the libraries each time you make a change.

    When we started our last big Python project, none of the Python tooling supported workspaces out of the box. Now, there’s Rye, which does so. But yeah, I don’t have experience yet, with how well it works.



  • Well, for reasons, I happen to know that this person is a student, who has effectively no experience dealing with real-world codebases.

    It’s possible that the LLM produced good results for the small codebases and well-known exercises that they had to deal with so far.

    I’m also guessing, they’re learning what a PR is for the first time just now. And then being taught by Microsoft that you can just fire off PRs without a care in the world, like, yeah, how should they know any better?



  • Tangentially related rant: We had a new contributor open up a pull request today and I gave their changes an initial look to make sure no malicious code is included.
    I couldn’t see anything wrong with it. The PR was certainly a bit short, but the task they tackled was pretty much a matter of either it works or it doesn’t. And I figured, if they open a PR, they’ll have a working solution.

    …well, I tell the CI/CD runner to get going and it immediately runs into a compile error. Not an exotic compile error, the person who submitted the PR had never even tried to compile it.

    Then it dawned on me. They had included a link to a GitHub Copilot workspace, supposedly just for context.
    In reality, they had asked the dumbass LLM to do the change described in the ticket and figured, it would produce a working PR right off the bat. No need to even check it, just let the maintainer do the validation.

    In an attempt to give them constructive feedback, I tried to figure out, if this GitHub Copilot workspace thingamabob had a Compile-button that they just forgot to click, so I actually watched Microsoft’s ad video for it.
    And sure enough, I saw right then and there, who really was at fault for this abomination of a PR.

    The ad showed exactly that. Just chat a bit with the LLM and then directly create a PR. Which, yes, there is a theoretical chance of this possibly making sense, like when rewording the documentation. But for any actual code changes? Fuck no.

    So, most sincerely: Fuck you, Microsoft.





  • I’d say, I’m primarily a very low volume gamer, so I don’t play a lot of games, and if I do, I don’t play them for long. And that certainly makes it easy to look at the news of a game releasing and to think, yeah, that’s probably neat, but if I’m buying another game then it’d be Undertale or Baba Is You or such, and it definitely doesn’t look as neat as those…


  • I find that difficult. Aside from code reviews, often times your job as a maintainer is:

    • getting a refactor or code cleanup in while everyone’s asleep
    • shuffling commits around between branches
    • fixing the CI toolchain
    • rolling back or repairing a broken change
    • unfucking the repo
    • fixing a security vulnerability

    A required review slows all of these tasks to a crawl. I do agree that the kernel is important enough that it might be worth the trade-off.
    But at the same, I do not feel like I could do my (non-kernel) maintainer job without direct commit access…




  • That is a very good question. It all started as a dainty test setup, and I guess, we had lost the routine of always scripting hardware setups, because our previous project hadn’t required it.

    Obviously, the second-best time to start doing it is now, but I’d need to properly learn one of these first to be able to lead the way on that.
    Which collides with me not really wanting to use any of the ones I’ve experienced so far (Ansible, Puppet) in my freetime. 🫠