Martin

South of Sweden

I’ve been using Linux professionally for 15 years. It’s been Debian or Ubuntu almost everywhere I have been. Although that might be regional.

Comments should explain “why”, the code already explains “what”.

I try to follow Bash strict mode. It can protect you from some foot shooting.

No thanks

Yes, unstable Debian is still hella stable. But you probably don’t want to suggest it as the first Linux dust since you need some extra carefulness when updating.

Try Rdx, it’s great for read access to Reddit.

More info in the GitHub repo.

We have well established ways to deal with secrets. Also, everyone is responsible enough to not self approve changes where they do things they are uncertain of.

We very seldom resort to self approvals. Everyone in the team see code reviews as important. But also that progress trumps code review.

Who said anything about only requiring 1 reviewer? And no, I did not drop an /s. You should try working for a healthy team where everyone takes collective responsibility and where the teams progress is more important than any one person’s progress.

We decided that everyone in the team is allowed to approve changes. If no one has reviewed your change within 24 hours you are allowed to approve it yourself. It will usually come up in the daily sync that a self approval is imminent, which usually leads to someone taking a look.

Yes, the top most directory, /, is the root directory.

Each directory is a branch in one giant tree structure. For example, if you have a directory containing two other directories, that is a branch that is splitting into two branches. All directories are descendants of the same root.

“Can open” and 'can open without the layout being broken" are different things.

“Compatible” with Microsoft Office, just don’t expect for your colleagues to be able to open the document in Microsoft Office after you edited it in LibreOffice.

Edit: Don’t expect your colleagues to be able to open it without the layout being broken.

Gnome with the gTile extension is quite nice.

I see, sorry for the noise.

It’s enough that you have read the code before implementing an alternative to get into legal trouble.

If it works and you are still figuring things out, I suggest not taking specific action right now. Use your package manager to keep your system up to date and it will deal with this in due time.

It was a way for apps to run without risk of being killed while letting the user easily see that the app was running.

If the foreground apps need the resources (RAM, CPU) the OS will kill apps that are in the background. There used to be various things apps could do to reduce the risk of being killed, but these options have gradually been reduced in recent years.