The problem is that they both are contextual and can mean any position in a list/array. The starting index or starting offset is generally zero, but could be one, depending on the language used.

Crazy. https://www.cbsnews.com/news/australia-ghost-appencrypted-messaging-for-criminal-underworld-arrests/

Amen. Now, where’s that Wine?

This should be its own sub to be honest. I bet this would get popular fast.

I appreciate both your and @[email protected]’s responses. I certainly was not aware of the expanded set of results that DDG use. Nor was I aware that they anonymized the queries they send to their search partners.

I’ve noticed this too. Not only what you stated, but how the search terms aren’t always respected; ie they do similar terms, even if the term or phrase is in quotes (the quotes should mean exact matches only). They also do a lot of filtering of the results if they feel I shouldn’t be seeing them. I can take my same search query from DDG to Google and most of the time find what I’m looking for.

If I understand DDG correctly, they use Microsoft Bing as their backend for search results. So while they may be branded DDG, the results are in fact out of DDG’a control. It also means we are more subject to Microsoft’s privacy policy than we are to DDG’s.

I’ve been wanting to move away from DDG because of these reasons, but have been unable to find good alternatives. Hopefully someone here can make good suggestions.

What I suggest is not the same as using git rebase. It’s pretty automatic and easily abortable.

In my experience, this amount of conflicts typically occurs because 1) most people mass commit a bunch of (mostly unrelated) changes at once, which leads to 2) inexperienced/impatient devs to clobber incoming merge conflicts without doing proper merges (mostly because they can’t make heads or tails of the diffs).

This is very easily mitigated if all developers would make small, related commits (with descriptive commit messages and not “committing changes”). This makes everybody’s life easier because 1) diffs are smaller and readable for conflicts, 2) the dev can see the progression of code through commit history, 3) broken code is more easily revertable (and traceable) if something goes wrong, and 4) it’s easier to cherry pick specific changes if the whole changes cannot be published all at once.

Also, git pull --rebase is your friend and not scary at all. It applies all incoming changes first, then applies your new commits last. 9 out of 10 times it avoids conflicts.

Lastly, use a GUI. There are plenty out there to suit your tastes, and I feel they are a safer and easier alternative than CLI. Some GUIs are very safe and even allow undo operations on most things.

I know this is a joke, but those errors/warnings/messages screenshot is not from git. That looks more like results from a compiler of some sort.

Sometimes it takes a little unintentional embarrassment to drive a point home. It’ll make them think twice next time.

What I mean by that is that as long as you’re not intentionally or maliciously trying to embarrass them, then you shouldn’t feel bad. You cannot always control how somebody receives information; nor should you. The best you can do is to be clear and polite in your communication. If someone’s feelings get hurt, that’s on them to reconcile, not you.

This is genuinely like parenting a child: they need to develop their critical thinking skills, and to gain their own confidence. So they must be left to make their own mistakes to learn from. Your job is to give show them the tools to use, give advice when necessary, and be there to catch them when they fall; because they will fall.

Doing this will help bolster their self-confidence and make them better mid-/senior-developers later in their career. Coddling them and constantly holding their hand will make them reliant on other people and prevent them from learning anything.

Edit: also remember KISS. 😊

It’s all good. If you’re using bash and readline to read the file, you can use sudo echo ${INPUT@Q} (assuming your variable is named $INPUT) to have bash escape things like the quotes and other characters that could get you into trouble.

sudo echo "# FYI quotes(") must be escaped with \ like \"

👆 that is not a comment. That is a command that says to echo the text “# FYI quotes(” and then to do ) must be escaped like \ \" which is invalid syntax.

I assume that startup script is reading the contents of the file and trying to echo them into another file? i.e., using the original file as a template, but is not escaping the input, hence the error — which you’re lucky that’s the problem you’re encountering and not something actually destructive like sudo echo "# foo" && rm -rf /*.

I merely meant that buying a house at a high interest rate is the irresponsible part. But yes, everything you say is true.

Activate your donkey now for $29.99/month!

My house. I bought when the rates went up, but I’m so much happier than living in an apartment.

Hint: they’re all expensive 😉

It was meant to be a replacement for the now completely defunct app called Our Home. It was a chore management app that allowed us to attach points to completed chores (mostly for the kids).

I started a community with the intention of posting a lot. It was meant to be geared toward an app I was going to build to help me and my family be more organized. Then life happened, and the need for the app waned, and. Now I guess I’m “squatting” on the community.

It’s not something I generally think about very often. I guess if someone wanted the community for whatever reason, I’d hand it over. The genuinely weird thing is, I have a multitude of people who subscribed; like 17 (not including myself).

Java/TypeScript

😒

I use the main feed as a way to broaden my horizons. Of course I block communities and use filters extensively as necessary. So it’s not too bad once it’s dialed in.