korthrun

Why do people do this? There is neither a clubhouse sandwich or any fries in this image.

This looks like a great lunch but why is it so common to call things what they aren't? "Fries" isn't a shape. Apple sticks? Slices? Roughly julienned apples?

Put pork flavoured soy on whatever you want, but why the need to call it vegan bacon ya know?

2-3 sprints?! Y'all really flying by the seat of your pants out here huh?

My teammates and I have no trouble planning multiple quarters in advance. If something crops up like some company wide security initiative, or an impactful bug needing fixed, etc then the related work is planned and then gets inserted ahead of some of the previously planned things and that's fine because we're "agile".

I delivered a thing at the end of Q3 when we planned to deliver at the start of Q3? Nobody is surprised because when the interruptions came leadership had to choose which things get pushed back.

I love it. I get clear expectations set in regards to both the "when" and the "what", and every delay/reprioritization that isn't just someone slacking was chosen by management.

Hot metal + arm = Smiley Face

You're absolutely right. For what it's worth, it's just the first part that's important.

When you pick up a new concept from a "resource" such as a tutorial, take a minute to explore the concept and understand the semantics of what you're doing. In the name of illustrating a concept tutorials can often be misleading in subtle ways.

An explanation of my "useless use of cat" example:

The command line has a concept called "piping". This lets one command send output to a second command. It's very handy. There is usually also a "cat" command, which will read a file and send the contents where you tell it. This is often your screen, or through a "pipe" to a second command. There is also a "grep" command that lets you search data for certain words.

Many "linux newbie" tutorials combine these tools to show how "piping" lets you send data from one command to another. "cat" some text file, then "pipe" the output to "grep" to search for your words. It usually looks something like cat ./my_address_book.txt | grep Giles to find lines in "./my_address_book.txt" that contain the word "Giles". The thing is that "grep" can take a file name as an argument. You can just do grep Giles ./my_address_book.txt, and cat is for concatenating files into one. If you want to simply read a file there are more appropriate tools such as "less". This by the way is the "useless use of cat"

When you're a newbie though, it may be the first time you're seeing either "grep" or "cat". The tutorial is just trying to show you "pipes". Along the way you're picking up these "bad habits". I've met professional sysadmins who didn't know grep took a filename as an argument. It was always "cat blah | grep my_search". I will see people type "cat /some/file | less" instead of "less /some/file". It shows a lack of understanding of what these tools actually do, and IMO it just comes down to regurgitating tutorial actions without bothering to understand the semantics of what you're being shown.

Don't follow tutorials, understand them. I'm so tired of seeing useless uses of cat because some asshole writing a tutorial 20 years ago decided to illustrate how pipes work with a good ol cat file | grep string as if grep didn't take a file name as an argument.

The more time I spend being mad about this the more I notice people using horrible practices in tutorials because they're too lazy to setup a legit use case.

A new user sees this and thinks this is how grep works.

Loops are another common one. People going around not knowing you can pass a glob to a shell for loop. Because the tutorial they read was lazily written and they didn't bother to understand the bits of what they were being shown, only how to reproduce/mangle the command until they manage to get close enough to what they want out of it.

This topic is addressed in the first paragraph on the linked page.

I also have a small domain that is relatively low traffic. A lot of the "all in one" software on the list you linked looks pretty cool, I can't deny.

What I found is that I make very few changes. I used to add mailbox aliases fairly often, but the fact is there are only two users and enabling the "+" syntax in addresses put a stop to me needing to make new aliases when I wanted a new address.

I just don't feel like I need a management interface. Because of this I've just sort of frankensteined my own setup together and I love it. It operates how I expect it to, and enforces the standards I care about to the extent that I desire (e.g. which SPF result codes am I ok accepting?).

• Postfix as SMTP/Submission server. I chose to go w/PAM based for outbound SMTP auth.
• Courier for IMAPS
• Dovecot for LDA (sieve is delightful)
• Snappymail for webmail (served by apache httpd)

Bonus tip: Many distros make this info available on the cli by including a "hier" man page that you can read using the command "man hier".

There is literally an image of it happening in the linked article. Followed by more pictures that help make this make sense. That's how.

I have not bothered to give soulseek a shit yet, sorry ;p I will say that what mentioned are more general content than music specific.

If cost isn't too much of an issue check out The Mooltipass or one of its competitors.

you can set the “FROM” address to literally anything.

Hey all, "that guy" chiming in.

You can set the "FROM" address to any string that meets the specifications of the "Address Specification" section of the relevant RFCs (5322 and 6854, maybe others). Which is SUPER FAR from "literally anything".

I know this seems like some neck-beard bullshit, but we're here answering the question for someone who clearly has little understanding of email internals. Hyperbole is bad in this context IMO.