DontTakeMySky

Sorry I don’t have any suggestions, but I’m very curious about your use case. What led you to needing this?

Are you doing web dev with just a phone? Impressive

True, but I don’t want to scare the carbrains. :P

Honestly though yes. My pretty basic road bike was 1600 and that was one of the lower prices in the shop. I think they averaged at around 5-8k in that shop at least.

Bikes can reasonably get to 1.5k at least without things getting too absurdly overpriced. If there’s a trade in it would at least be for bikes in that range.

And every spell works like goodberry (the food is infused with the magic and anyone can consume it to complete the spell).

And all material components are food ingredients.all somatic components are cooking steps, and all verbal components are Gordon Ramsay insults.

Agreed.

If you want to do a custom class, take the stats of something that already exists and just flavor it as something new with a new name. Maybe a bard but their performances are cooking meals for people or something.

Maybe come up with a few homebrew spells for them that are cooking related (or something functionally identical to a spell, even if it isnt). Pick an existing spell that’s close to what you want and flavor it as food related and give it a new name.

I think it’s the accounts he’s following on Instagram. It’s a screenshot from her phone’s perspective I think.

A small company like that likely won’t have policies and processes to fall back on. This can be good for some things, but when things go bad it can backfire.

Mainly for things like promotions, HR, complaints, etc. In big companies there’s a formal process for how to get promoted and what’s expected at each level, etc. Same for HR complaints. At a small company you’re going to be more subject to the whims of whoever is in charge.

Same for new projects. In a big company you have red tape and processes to blame when something fails, but in a small company it’ll be more likely to be “your fault”.

That’s amazing, I’m glad your coworker was able to find someone and get to be a parent.

I’m sorry if I came across as advocating against surrogacy. I don’t nearly know enough to have that strong of an opinion on it in either direction. All I wanted to get across was that making sure there’s no coercion is hard. Not impossible, but hard. There were some really sweeping statements under this post that felt like they were oversimplifications and I wanted to consider the nuance.

Separate from any discussion about surrogacy, that’s fucked and our adoption system should be way more accepting of gay couples than it is. There’s no reason it should be so hard.

Absolutely! And more to cover other expenses like maternity clothing, any comfort items to manage the pregnancy, additional dietary needs, and probably some more to help account for how traumatic a pregnancy can be and the body changes it causes.

I’m absolutely not advocating that a surrogate shouldn’t get paid. Just that it’s hard to separate payment from coercion in even the best situations.

Im not sure I can be so confident just because the surrogate knows the couple. If anything that would make me more worried about coercion. That could easily add MORE pressure for a surrogate to take on the pregnancy if that surrogate knows how important it is to the couple.

I don’t know how I feel about it overall (surrogacy, not gay people getting to have children, that’s beautiful), but it’s hard to be confident there’s no coercion when money is involved. The money itself can be coercive especially if the surrogate is particularly in need of the money. I’m not sure it can always be “clear” it’s not coerced.

Probably some kind of wallpaper app then? Or maybe a video call app downloading backgrounds?

You could try limiting files permissions on a bunch of apps to see what gets them to stop.

At least in very dramatic extremes, yes there’s at least a correlation between horrific animal abuse and psychopathy.

No idea if that extends to more run of the mill actions.

Them both being dead is both convenient and conveniently suspicious. Since Trump is guarded by secret service, conspiracies would arise saying they (under Bidens order, or a Harris power grab) killed him. It would be completely absurd given the circumstances and no reputable source would support it, but people would believe it anyway and Fox would push the story. Widely broadcast funerals for each of them.

Then nothing… The conspiracies would flow, but nothing much would change.

With a comment on the test detailing why it matters so people don’t just assume the test is out of date when it fails.

And ideally test the underlying result of x before y, not the fact that x is called before y.

And while we’re at it, assert in Y that X has been called, and again comment the reason for the preconditions.

Code comments for "why"s that persist. Commits for why’s that are temporary.

If you need to run X before Y, add a comment. If you added X before why because it was easier, leave it in a commit

Don’t just summarize the content though, summarize the rationale or how things connect. I can read your diff myself to see what changed, I want to know the logical connections, the reason you did X and not Y, etc.

Or just say “stuff” and provide that context in the PR description separately, no need to overdo the commit log on a feature branch if you’re using squash merges from your PR.

“stuff”

Sourcetree is still best by far for history browsing, and I’ll die on that hill.