Val

Four months is early. The syntax that sticks is the syntax you have typed a hundred times, and there is no shortcut, only repetitions. If you want it faster, build things that reuse the same constructs deliberately rather than jumping languages.

Worth asking your lecturer how long they expect a sheet to take. Mine said six hours for six problems and half the room visibly relaxed.

Course completion is a metric nobody will ever ask you about. The thing you built is the thing you talk about.

The chicken breast fatigue is a preparation problem more than an ingredient problem. Thighs instead of breast, cooked hard in a pan, are 24g per 100g and taste like actual food. Same with pork loin, turkey mince and whitefish. I rotate four proteins on a fortnightly cycle and the dread went away entirely.

Two separate ideas are colliding here. new = old does not copy anything, it makes a second name pointing at the same list object, which is why the first version surprised you. old.copy() makes a genuinely new list, but the elements inside it are still the same objects as before, so a list of dicts gives you a new list holding the original dicts.

For your case:

import copy
new = copy.deepcopy(old)

That recursively copies the nested structures. Downside is it is slow on big data and it chokes on things like open files or database connections. If your dicts are plain data, deepcopy is the right call and you should stop thinking about it.

That is still a shallow copy, identical behaviour to .copy(), so it does not solve the nested dict problem they described.

Fourteen days with no card is also long enough for the trial to disappear from someone's memory. Most people evaluate on the first day or never. Shorter trial, or trial that starts when they hit the activation action rather than when they sign up, converts noticeably better in my experience.

Almost certainly a missing return inside getUser. If you wrote

async function getUser() {
  fetch(url).then(res => res.json())
}

then the function returns undefined immediately and the fetch chain runs off into the void. Add the return, or better, rewrite it consistently:

async function getUser() {
  const res = await fetch(url)
  return res.json()
}

The other classic cause is calling it without awaiting somewhere further up, for instance in a .map() where each callback returns a promise and you get an array of promises. Promise.all fixes that one.

Worth saying that this is what worked for me rather than a rule. If you have logged carefully for a month, including weekends, and genuinely nothing is moving, that is a reasonable point to talk to a doctor or a registered dietitian rather than cutting further on your own. There are ordinary medical reasons for it and a forum cannot check them.

It usually is not. Most people who fix afternoon hunger do it by rearranging the same food.

Also set the default so git stops asking: git config --global pull.rebase true if your team likes linear history, false if they prefer merges. Ask which one your team uses before you set it, it is a genuine preference and people have opinions.

Also be careful with the implied renewal threat. Sometimes it is real and sometimes it is a negotiating posture. Asking directly, if we cannot get to this by March, does that change your plans, gets you a surprisingly honest answer most of the time.

Noted with alarm. One bar it is.

Starch not counting as sugar is embarrassingly obvious now that you say it. Bread has been confusing me for months.