Perl is the only language that looks just as incomprehensible before and after a rot13 transformation.

Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.

And lisp is hard to say if you have one.

Edit: aa -> after a

AI, also known as Assumed Intelligence

For the purpose of?

Venting? Warning? Praise?

Something else?

Reddit support to the rescue…

Bruce Perens is currently working on a new licensing model called Post Open requiring that business with sufficient revenue to pay up.

https://postopen.org/

In my opinion it’s criminal just how often this happens. Big business making obscene profit off the back of volunteer work like yours and many others across the OSS community.

Is it just me who is sceptical about anything new from Intel at the moment?

Mind you, this is not the first time that this feeling has existed, there was a standing joke amongst IT professionals in the mid 1990s that the sticker “Intel Inside” was actually a warning label, referencing the Pentium FDIV bug.

Multiple camera angles are used for two reasons:

1. Added visual interest. People tend to want variety and colour and movement offered by different views can provide that. This is the obvious reason it’s being used.
2. Ability to edit without it being obvious. Often a presenter will require multiple takes to “get it right”. If you edit in the take, the picture “jumps” because humans move around. If you have multiple cameras you can edit and switch cameras without it looking like an edit. If you then also look at a different camera when you make a mistake, you can keep recording and fix it when you edit it together.

All I’ll say is that I’m glad that I’m neither your child, nor a member of your software development team…

And many of them are heading to BlueSky…

My first recommendation is to become familiar with one flavour of Linux. Debian is a solid choice and it will give you a good understanding of how a great many derivatives operate.

The command line is a tool to get things done, it’s not an end to itself. Some things are easier to do with a GUI, many things are easier to do with the command line interface or CLI.

Many Linux tools are tiny things that take an input, process it and produce an output. You can string these commands together to achieve things that are complex with a GUI.

Manipulation of text is a big part of this. Converting things, extracting or filtering data, counting words

For example, how many times do you use the words “just” and “simply” in the articles you write?

grep -oiwE "just|simple" *.txt | sort | uniq -c

That checks all the text files in a directory for the occurrence of either word and shows you how many occurred and what capitalisation they used.

In other words, learning to use the CLI is about solving problems, one by one, until you don’t have to look things up before you understand why or how it works.

Given your “updoot”, I figured that you’d get it, seems that others were not so lucky…

This precious token was gifted to me and I pass it to you…

Thank you for the links, never heard this, much appreciated.

Unfortunately, with that comes no assistance to your query.

Ask your instance administrator.

Sadly not. Form an audio frequency perspective, noise is many different frequencies. The human voice pretty much matches human hearing.

A voice is not one frequency, that’s a tone. We’ve constructed systems that throw away much of the voice frequencies whilst still being understandable. Telephone calls, digital radio communication, etc.

That’s not to reduce noise, it’s to cram more calls across the same link. There’s a side effect that does reduce noise to some extent, but not significant enough to remove construction noise.

I suspect that your success rate will be very low. Bone conduction microphones might be your best bet.

Fundamentally a microphone doesn’t know the difference between “good” sound and “bad” sound.

Most noise cancelling solutions are based around the idea that nearby sound is good and distant sound is bad.

It differentiate between the two by using the fact that it takes time for sound to travel.

If you have two identical microphones, you can set them up so that you talk directly into one, but not the other.

Any environmental sounds are picked up by both and used to cancel it - sometimes in software, other times just by reversing the microphone polarity.

Bone conduction microphones get their signal from physical contact with the audio source, your body.

Source: I’ve done a little bit of audio recording over the years in and outside of studios. My information might be incomplete and out of date. YMMV.

You can do both at the same time.

Start small.

Write a little bash script that fixes something that causes you grief. Put it up on GitHub with a README.md file that explains what it does, why and how.

Rinse and repeat.

Generally laziness helps.

If you host a system, then you have to dedicate resources to maintaining it, which quickly escalates to lack of interest.

If you pay someone to host it, you get to spend your energy on things that you’re interested in.

If you can find people to pay you for things that you’re interested in, but they just want fixed, you have a business.

So, be conservative in what you host and frivolous in what you outsource.

Note that this says nothing about FOSS. since that’s about a related but different concepts.

From a FOSS perspective, be frivolous (as in, do lots) in your bug reports and patches, be conservative in which projects you own.

It’s to encourage you to eat faster and leave, so your table is available for the next victim.