Amen. Now, where’s that Wine?

FWIW, I’m referring to the local DNS (domain name system) resolver; the mechanism that resolves local domain names into IP addresses so that computers can talk to each other over the LAN.

Here is a good primer on the configuration files and their possible locations: https://www.freedesktop.org/software/systemd/man/latest/resolved.conf.html

Edit: be careful because this is your domain name lookup you’re messing with. 😊

You make mostly good points — I still disagree, but I can at least see your side.

The divorce and kids thing though is not what you think it is. Divorce and child custody agreements are two separate legal things and child custody agreements are thankfully not a matter of public record.

I don’t like the existence of billionaires anymore than the next reasonably-sane pleb does. But someone’s financial/social status should never be a consideration to their constitutional right of privacy. You’ll just have to find some other way to harangue them for their behavior.

Why? To publicly humiliate a person? Not everyone is evil; people fall on hard times. It happens. A lot. Why should they be further harassed by predatory practices of being offered loans after they’ve hit the rock bottom of their financial world? Because the first thing that happened when I filed for bankruptcy was to be offered a mortgage loan.

I believe some things (like DMV records) are fee based. But the fee is nominal and wouldn’t stop any predator from doing bad things if they are so inclined. The only thing adding fees does is to financially incentivize keeping the data online and accessible to anybody who pays.

I’ve never understood why things like this have to be a part of public record. Traffic accidents, traffic citations, bankruptcies, buying a house, and even getting divorced.

All of those are very personal things that should never be a part of public record. And even if they are, the PII should not.

I usually lead with, “That’s out of my control,” or “that’s above my pay grade.” Most of the time people get it.

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

If CrowdStrike has taught us anything, it’s that blindly trusting automation can be equally (if not more) disastrous.

It’s one thing to ask me to update, but give me options; including to not update. There are machines out there in the world that still run Windows 95. They are vital to manufacturing processes, and cannot be updated because they run software that is no longer updated and there is no inexpensive alternative. It happens.

While that may not be the case in this circumstance, the point is that it’s up to the operator to determine when it’s time to update, not Microsoft.

Anecdotally, the only reason Microsoft does this is because people historically do not update their software regularly. Why? Because it’s burdensome and problematic. Whose fault is that? I’ll give you three guesses; the first two don’t count.

Hey thanks. I’ve starred the repo for later reference.

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.

Is there not a registry setting you could use to disable it?

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 /*.

/^\w{6,16}$/

The issue lays not with legality (it’s obviously illegal), but with a person’s (financial) ability to pursue legal recourse.

BUT, finances aside, people should always document everything. In person meeting or phone call? Follow up with an email recapping what was discussed. Make sure to take notes so you’re not relying solely on your memory.

Look for lawyers who would be willing to work on contingency. This is where they get paid when you get paid. If you have some money saved, you might be able to get away with retaining the lawyer.

Obviously a lot of people cannot afford a lawyer, and that’s a damn shame. Companies count on this fact and use it against their employees. But by documenting everything, you at least send a message to the company that you’re willing to fight back and that maybe enough in some cases to deter them (a long shot).

Also check with your state’s labor board to see what, if any, resources are available for workers in these type of cases.