kettro

Almost all North American sports have a player entry draft, where the weighting is based on your success. The best teams (eg the Detroit Red Wings of the 90’s and 00’s) are given garbage draft picks, while the bottom-feeders (eg the Edmonton Oilers of the late 00’s-early 10’s) are given (the opportunity for) superstars. This is clearly a punishment for doing well, and a reward for being terrible.

It is exactly the correct approach — especially with the dataset potentially changing at each iteration, treating it as a contiguous sequence of executions is wrong anyways. Plus, you should always strive to reduce state as much as possible.

The issue with null pointers is that they are, as you said, a stand-in for an invalid state. However, most null pointers don’t prevent you from trying to use the underlying data, which can, among other things, cause crashes (think not checking the return value of malloc). Additionally, it doesn’t make formal the litany of possible forms that a value can take — if you codify possible states, then you don’t always need to check everything. I’m currently working to port security firmware from C to Rust, and I’ve found I make fewer state checks, because the data I’m working with has bounded state — the data given cannot be in an invalid state.

They ask you to set a primary care doctor, but I have had more success with seeing a small group of their more available non-MD physicians.

That, or another piece of jewelry is an obvious place to start. Essentially, anything that has utility, and you use it for that task.

It’s not like Vancouver or SF decided first to have safe injection sites, and then suddenly had huge heroin problems.

Waiting helps you ignore the impulse responses, and double check if you heard the question correctly, whence you can just ask for clarification.

No one complains about a sorta slow speaker, but a frenetic one is hard to follow and will blurt things out.

We have unicode for Sumerian, so I don't think that will ever happen.

https://en.wikipedia.org/wiki/Sumerian_language

/s/Azov Battalion/Ukrainian National Guard/

Later on, you may want to branch out to More complicated Distros, but Ubuntu (or Debian) is the easy choice.

Thankfully, we don’t need to be beholden to history.

Another: someone with anxiety is prescribed Valium. Over time, it starts to work less well. They go to a doctor, who ups the dose a bit. Repeat, again and again. At no point was the patient ever not prescribed the dose, but addiction happened nonetheless. And when their insurance stops (say, after losing their job), then they need to keep up, and get Valium any way they can.

These are not uncommon. At all. Addiction from other means is typically a result of mental health: someone is desperately trying to fix something, which leads to drinking, which leads… The same is true for any other drug. If you actually interact with addicts, it is very very obvious. There is a reason that AA is the way it is. I really recommend going to a meeting, just to visit. It will absolutely change your mind, if you are open to it.

The patch workflow is smooth and just a great experience. It is vastly improved by some git aliases (which you can set up in your gitconfig), but is, in general, very smooth. It allows for local branches to a single upstream, topic tagging, and a reasonable learning curve. Much better than GH.

It would be very well served to have a web-based offering (like GitHub/Lab).

I’m on Linux, and use mosh as a more reliable ssh client.

C is not “low level”, in the assembly sense. It is absolutely a high level language. But it is the simplest, and the one with the most fine control.

Scots is absolutely a different language from English, despite it being intelligible. I can't produce that speech, even with an accent. It has different rules and formations that My English just doesn't have.

Having both is important, though: you need to be able to preserve the things that matter, that you may need later on.