![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.hogru.ch/api/v3/image_proxy?url=https%3A%2F%2Fprogramming.dev%2Fpictrs%2Fimage%2F170721ad-9010-470f-a4a4-ead95f51f13b.png)
You guys have docs?
You guys have docs?
Sadly it doesn’t fix the bad documentation problem. I often don’t care that a field is special and either give a string or number. This is fine.
What is not fine, and which should sentence you to eternal punishment, is to not clearly document it.
Don’t you love when you publish a crate, have tested it on thousands of returned objects, only for the first issue be “field is sometimes null/other type?”. You really start questioning everything about the API, and sometimes you’d rather parse it as serde::Value
and call it a day.
To whoever does that, I hope that there is a special place in hell where they force you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.
Sincerely, a frustrated Rust dev
I would do that… If CI wouldn’t be set to -D warnings
Who even does that? Oh wait, it was me.
Joke aside, it does help to keep the code clean, even more for open source projects where multiple separate people may all have their own codding style, and it helps make it easier to organise.
But I do agree that it can be really, really annoying.
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
Virgin toddler squasher Vs chad adult compressor
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
Thank you. I thought it was an egirl equivalent for boy pussy… It does make a lot more sense now
What’s an ebussy?
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!
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.
If a item can have different type, those label fields are actually quite useful. So I don’t see the problem