My attempt to explain was squashed by this comment

It’s the second time I see it on a programmer humor community. I get you want to advertise, but we already told you that this isn’t the place for that

I do push often as I’m often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with

I often do the same for my memes. I like them high quality

NGL I 'm a bit like that. I often do “work” commits so that my working tree is a bit more clean/I can go from working state to working state easily.

But before a PR, I always squash it, and most times it’s just a single commit

Could you explain your choices better? Like what makes the top tier so good, and why the bottom tier is so bad?

I’ve started to become 2) for some stupid reason.

I use btrfs snapshots to backup my system, and it has the side cost of needing a bit extra space. This is absolutely fine.

What is not fine however is free desktop/Nvidia flatpaks update. I get 10gb every week, and it keeps filling my disk with this stupid crap.

Not only that I am both a rust programmer and blender artist, and it’s the trinity of non deduped disk space filler

We got the dank Linux syndrome.

Instead of brain there’s a tux doing shitposts.

It’s terminal

Let’s just hope that they won’t use it as a justification to put ads in your browser, or go the brave route.

Thank you. I thought it was an egirl equivalent for boy pussy… It does make a lot more sense now

What’s an ebussy?

Well until you are deep into trait/future/generic territory. Because then you’ll go in big fuck (full type being in a separate file) not being correct somewhere in this shit.

Don’t get me wrong, I love rust. But those area really need some love

They created it. The compiler says the jump function is in src/main.rs

Would be cool to be AI horde compatible and just ditch the GPU requirements entirely.

I don’t think everyone got a GPU that could run stable diffusion easily, even more for laptops

It’s not that bad. It definitely helps in long functions.

I’m an advocate for code commenting itself, but sometimes it’s just better to comment on what you’re doing, and in those cases it helps to over commentate.

Instead of letting the reader interweave code reading and comment reading, I think it’s better to do either. Either you go full self describing code, letting the reader parse it as code,m, or you abstract everything, making it more of an explanation of your reasoning, and abstract lines that may look too complicated.

Not every comment needs to be useful, but I still write them to not have this switch between reasoning and thinking in code. It can also double as rubber duck debugging too!

No one diss the gaming demon summoning circle! Sacrifice him!

What those two commands do?

Bobby’s son

Oh I’m not talking that it can’t be trained well. That’s not my point.

Of course dogs can be trained to sniff drugs or find people, the gist of it is that they were trained for this behaviour, and might not understand it like we do.

A good exemple is a study that research on cancer sniffing dogs had problems with false positives.

proud Rust developer

Joke aside, everytime people gush over AI, I always have to remind them that AI is just a puppy that learnt how to maximise treats, and not actually understand shit. And this is a perfectly good example.