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
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
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
Let’s just hope that they won’t use it as a justification to put ads in your browser, or go the brave route.
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
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!
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.
I don’t know and that’s the problem :(
I keep asking myself what to choose, only for changing it a day after cursing myself to choose a stupid name.
Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place. But that’s also a detriment when you know what you want. You can start typing without the prefix but you’ll have to go through the better suggestions of intellisense first.
Little endiant is the same thing, but in reverse. Great when needed, but bad for browsing.
Although I do have some fix I’m starting to use. But it’s not applicable everywhere, and not in every language.
What I do is use module as prefix. Instead of dialogue_file_open
, I create a file_open
in the dialogue
module, allowing either directly calling file_open
, or dialogue::file_open
. Using intellisense on the module allow for easy browsing too!
Although in OP’s post I’d rather have file_open_dialogue
as it convey the more significant meaning, being to open a file, first. Then “dialogue” is just the flavour on top
Oh yeah, there it’s a completely different story. But that’s mostly on OP to not provide context.
But if it was installed that way, it’s just MS being shitty again
Apart from the search engines being both shitty, here there’s nothing wrong
If you installed an extension to use bing search, what you want is to use bing search, not Google. So of course the extension has to say “don’t switch”
There’s also a good point on chrome’s side. There’s extensions that will switch your default search engine without your consent, so having the possibility to undo directly is nice.
Another way to see it, would be to switch chrome for firefox, Google search for duck duck go, and bing to qwant. Same story, but no shitty companies clouding judgements
Well it ses that bing is down too, and most independent search engines are a warper arround bing so…
The worse part, you enter the blog, it looks legitimate enough at a glance, go straight to the code, then find out it’s bullshit.
We need ai blog blockers now…
Inb4 normies force us to change well established terminology just to appease their fragile souls
Like git’s main and master
Good meme, bad reasoning. Things like that are why JavaScript is hated. While it looks the same, It should never, and in ANY case be IMPLICITLY turned into another type.
Oh, then you use and_then()
or something similar.
There’s also the possibility to use the guard clauses patern and do let <...> = <...> else {}
.
And finally, you can always split into another function.
It’s not straight rules. It depends on what makes it more readable for your case.
My attempt to explain was squashed by this comment