sukhmel

joined 3 years ago
[–] sukhmel@programming.dev 5 points 1 week ago* (last edited 1 week ago)

I'm not a 100% sure it does, the choice of symbols looks a bit suspicious but it could be independently invented from ColorAdd idea like the one you linked. Symbolism is hard to standardise, maybe a chevron for blue has another meaning for the author

Edit: or more realistically, they had this problem and decided to solve it with AI and publish their solution for everyone without checking if the solution already existed and was partially copied by AI. That's the feeling I get from the repository at least

[–] sukhmel@programming.dev 15 points 1 week ago

To be fair, this is what bothers me more than the supposedly non-existent benefits, because I've seen LLMs being useful as tools, but the impact on environment is not clearly communicated (I'd wager it's because no one wants to admit that it's enormous). For that reason I'm trying to use local LLM instead, and it is more limited in usefulness but that's fine by me as it's not the only tool I have

[–] sukhmel@programming.dev 2 points 1 week ago

Charging you would create real revenue, which would violate our principles.

Great, also payment plans are very affordable

[–] sukhmel@programming.dev 2 points 2 weeks ago

Isn't it already how things are run if you have the right rights unlike the rest of the populace

[–] sukhmel@programming.dev 6 points 2 weeks ago

Oh, but that's different, you see

[–] sukhmel@programming.dev 6 points 2 weeks ago

I think it's because the article is trying to paint a picture that may not exactly fit the reality. But I didn't read it anyway, this comment thread looks more interesting

[–] sukhmel@programming.dev 1 points 2 weeks ago

Yeah, some commit messages are very not good either

[–] sukhmel@programming.dev 2 points 2 weeks ago (2 children)

Largely yes, but also having it squashed requires better commit messages and comments to show what was done for what reason. But yes, bisect is the only reason I'm fine with squashing

[–] sukhmel@programming.dev 1 points 2 weeks ago

Because less merge conflicts (we also rebase on top of master each time we commit)

[–] sukhmel@programming.dev 1 points 2 weeks ago (2 children)

If you mean to ask what that means, it's that for development you start a branch and either do everything in one commit, or do everything in several, but each time you git commit --amend so that a history is overwritten and in the end it is only one commit still

[–] sukhmel@programming.dev 3 points 2 weeks ago (1 children)

I mean, who cares, really, it's your desktop, after all

[–] sukhmel@programming.dev 1 points 2 weeks ago

With rules like that I would expect people to split onto two groups: ones that learn one pattern and repeat it because it's a guaranteed result, and one that tries to find a counterexample to the rule they thought of at first. The fact that pigeons try different patterns kind of makes them more clever in my eyes.

But it's known that pigeons perform better than humans in Monty Hall problem, so they are really pretty smart when it comes to statistics, it seems

view more: ‹ prev next ›