Awesome! Love these previews tools! Super useful.

I am creating a free tool to preview the whole social post.

I love CLI tools, plus it is open source!

Directories are getting more and more popular and people are making money from them. Have you created one or thought about it.

What is stopping you? I wrote a blog on why you should create one with your knowledge and resources.

"The idea behind the algorithm is to give high-quality content more exposure. But it's not about quality anymore. It's about what gets the most likes and shares. We end up pushing a few types of content that get engagement instead of quality. Most of the time, it's broad inspirational messages because they appeal to everyone."

I don’t like the phrase “algorithm” because an “algorithm” could be just about anything.

For instance you might choose to emphasize titles that start with “B” and are between 40 and 50 characters long. In the AI age you can train a model to identify more complex characteristics as “angry”, “political”, “written by somebody depressed”, …

Then the are the fairly “organic” feeds that I think are toxic without a lot of work behind the scenes. Consider something like Mastodon or Twitter where you follow people and see their retweets/boosts, some people think that “chronological feed” is a Garden of Eden but it is really a chain reaction or clickbait and if you don’t believe me look at the “explore” feed that shows what is most boosted.

You can make an algorithm that privileges anything but ‘quality’ is probably the hardest recognize as you can at most detect signs of quality.

thanks for the reply Paul and elaborating

> they are automatically distributed everywhere where they are needed

for you and your tools, but what about everyone else?

Look at using dotfiles to sync your computer's config to multiple computers, it is a great tool

Other people working on the project add their ignored files to the same .gitignore. No problem.

I don't understand why people make an issue of that. Just add everything that needs to be ignored to the .gitignore, as long as it makes sense to someone. If I use XYZ-Obscure-Unknown-Editor, just let me add `.xyz-obscure-unknown-editor/` to the .gitignore. It literally has no negative impact on anyone.

There's no reason to gatekeep what goes to the .gitignore

Great point! Thank you for adding that, yes it works for sub folders also, which makes sense especially for mono repos

I really appreciate you adding value to the conversation, thank you!

good point, comments are super important

I don't like to rant, I like to have professional discussions.

Than you for reading the article and for sharing the FB link with a git ignore example - the contents of the example file is not long because it doesn't have every dev tool possible, so I think you proved my point - so thank you :)

Can you answer the questions?

>> Everyone uses different operating systems, IDEs and dev tools. > How is this related to .gitignore?

Exactly! I explained in the article (and video) people fill the repo git ignore with all their personal tools that generate files, for example .DS_Store, .Idea etc. This should go in their personal global git ignore

>> This list will only keep growing, it will never end > Where's the problem? A random Facebook's repo has its gitignore file weigh 2KB[0]. Is this a problem?

Have a look at some other projects. I explained in the article (and video) the file can be pages long with every possible combination and will only keep growing as new dev tools come out

>> Is the “.gitignore” file competing with the “README.md” for the most updated file in the git repo? I hope not > Again, why is this a bad thing?

As I explained in the article, it becomes a lot of work for the maintainers, to review, check for duplicate entries etc

I don't think you read the article, there is a video at the end if you prefer.

Yes we should use git ignore for the repo specific items, so if the repo has terraform it should ignore generated files - but not desktop tools people use as we all use different dev tools

> Examples of folders included in the git ignore file are generated files like “.next” from NextJS or “test-results” from Playwright. These will be generated for every developer on the project regardless of their OS, IDE etc.

> Yes I am saying this is wrong… (let me know if you agree/disagree below)

I didn't realize that the first paragraph is saying "This is good"; I thought the second paragraph was saying that the first paragraph is bad.

oh sorry for the confusion! I do think we need both git ignores, but to be used appropriately.

System global .gitignore solves a problem specific to that developer

Repo .gitignore solves a problem for the project (and every developer)