31–40 of 258 posts
Do other people react as strongly as I did to the lack of capitalisation at the start of sentences? The post is generally "well" written with good grammar and punctuation so I find it strange - it feels like a style choice. But the style choice just instinctively makes part of my brain feel like it's written by a child.
> new contributors make PRs. they make silly simple mistakes due to lack of experience; you point them out and they get fixed. this can be fun, for a time. what it’s teaching you is that you personally are responsible for catching mistakes. Every team I've worked with that was feeling exhausted about code contributions actually needed to focus on better documenting guidelines but most importantly, improve CI. Catchin…
CI is good. more tests are good. but there's a limit to how much they can catch.
here is an example: there is an internal type checking API called [`resolve_vars_if_possible`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_infer/...). this needs to be called on the output of almost any call to `.normalize()`, or you will get an internal compiler error. the conditions under which you get an ICE are quite complicated; sometimes you need 6 or more items in the crate with `impl Trait` or type_alias_impl_trait or const generics involved. but it's very easy to see there's a bug just by looking at the code and seeing the missing `resolve_vars()` call.
how can we automate this? well, rustc has a mechanism for "internal lints", but they're somewhat annoying to write - you're basically writing a new compiler pass, and it needs to not have false positives. it's much easier to just catch this one instance. so the reviewer, who's already burned out, does this quick manual review instead.
Do other people react as strongly as I did to the lack of capitalisation at the start of sentences? The post is generally "well" written with good grammar and punctuation so I find it strange - it feels like a style choice. But the style choice just instinctively makes part of my brain feel like it's written by a child.
This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about. I am not sure what to do about the burnout problem. The way he described it is very on point though.…
Glad some said it. When things are too organised or categorised it just becomes another business/todo list.
Earlier quoted context omitted.
This generalises to any idealism. You would not think veterinarians to be at elevated risk of suicide, but they are [0], and I think the reasons are similar: a moral dilemma caused by the mismatch between expectation and grim reality which ultimately leads to burnout and desperation. The other extreme is a "bullshit job", work that you don't enjoy and which serves no meaningful purpose. [0] https://www.bbc.com/workli…
I 100% understand why veterinarians are in a crisis. We had to let our pupper go a few weeks ago. The vet had to basically sit there and watch us while we processed the fact that we were about to pay her to kill our best friend. For us, it was the worst day we had experienced in years . For her, it was Tuesday. She had other people waiting in the room next door, and had to go from solemn to bright and cheery over the…
veterinarians are the most realists people in the medical field. While you put cost as the main factor my experience it is not simply a math problem, it is often a quality of life issue. Spending the $10,000 to extended a pets life for a another year is rarely about making the pet better, it is emotional support for the human companion of the pet while the pet will end up suffering for the year and die anyway.
So yes it is often cheaper to humanely put a pet down, it is often also the most ethical thing do to even if money was not a factor.
I call them realists because the face the inevitability of death head on in a way that we do not do in Human Medicine where we believe maximization of chronological age is the singular goal to be achieved at all costs with no regard to cost, pain, suffering or quality of life.
This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about. I am not sure what to do about the burnout problem. The way he described it is very on point though.…
> I am not sure what to do about the burnout problem. Pacing and self-regulation. It’s a marathon not a sprint. Set an hours-per-week budget. Beyond that things just don’t get done. That’s okay. If the community needs faster pace, they can consider supplying hours or dollars to fund more developers to work full-time.
> the best way to help the project is to keep contributing for it for years. to do that, you have to avoid burning out, which means you have to treat yourself well. When I was a schoolteacher, the way I expressed this is that you have to do the job in such a way today that you're capable of doing it again tomorrow. This did not go down well and I am no longer a teacher.
Safety first, people. Take care of yourselves.
This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about. I am not sure what to do about the burnout problem. The way he described it is very on point though.…
I'm not sure whether it's more to do with the way the project is organised, the state of the codebase, or the sort of person that's attracted to working on Rust in the first place.
Just close PRs that don't meet basic quality criteria, and you will go through them in no time. Oh, but I suppose that's not compatible with the "no one left behind"-type rust manifesto.
This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about. I am not sure what to do about the burnout problem. The way he described it is very on point though.…
Get paid for it, and don't do anything more than you are paid to do.
I've done volunteer work, per se. My biggest takeaway has been that humanity overall is not worth giving away my free time to.
When I volunteer my time now, I do so only for individuals who I know will sincerely appreciate it.