116 karma · joined January 4, 2021
Prediction: an astonishingly large portion of animal utterances will have to do with reducing the amount of carbon dioxide that humans pour into the atmosphere. You heard it here first.
Just to take the most egregious example,
> To iterate over something using the natural features of the language (object references, array indexing), it would need to be an array managed by that same language implementation.
I seriously doubt that's true even in cython, and I know it's not true in rust. In rust, you could either just use raw pointers (but this doesn't meet the spirit of the demand) or you can assert to the compiler that this code isn't being mutably accessed by other code (an assumption even of the C code, or else it is incorrect) and get a slice. At that point there is no difference between that slice and one "managed by the language", whatever the heck that's supposed to mean.
So immunocompromised people? The rest of us have immunity.
does not mean "effectiveness at preventing the spread of the virus", it means "effectiveness at preventing severe illness and death".
The most important thing about zsh you should think of is "no need to quote variable expansion".
I guess you can continue to deny this kind of person exists; but it doesn't really matter what you think.
This is projection. There are multiple modes of approaching communication and not everyone uses the mode where communication is an exercise in one-upmanship.
Lol it really isn't curious. The vaccines do really well at the first metric, and it can be measured in very short trials (which means smaller trials due to less attrition, and means more trials, etc.) The second metric, they don't do so well at and it's more difficult to measure. It'd be curious if things were any other way.
What other reason could there be given the overwhelming evidence that no legitimate voter is stopped by these laws?
Here's why: Everyone (on the ground floor at least) knows that the code is terrible, but the organization is not optimizing for good code. Code quality is simply and literally a non-goal. The goal is to deliver Projects, where a Project is a unit of work which advances someone's career, whether it be an IC, a project/team lead, a project manager, etc. Now, it's okay not to internalize that goal for yourself; but you've exposed yourself as not understanding that this is the goal that everyone else has. Unfortunately, this makes you a liability w/r/t the goal.
There are ways to advance other goals in the organization, and I suspect these organizations only survive as long as sufficient people are doing just that, but they all revolve around making other goals coincide with The Goal described above.
Note that The Goal isn't a secret or taboo; it's explicitly acknowledged in some organizations. Not so long ago at Microsoft, for example, it is known as "impact" and is the explicit top-level metric for performance review. If you can figure out how The Goal it's expressed in your organization, you can attempt to rescue the situation by explaining that what you really meant was you want to advance The Goal (eg. "improve my impact") by delivering improved code quality in future projects which will have such-and-such an impact on visible metrics.
Having a written agreement—I don't think it sounded like "formal contract" to me—is more transparent than the pre-existing situation where they were informally providing water. Your complaints are internally inconsistent and it seems you just want to kvetch.