Clojurians Log v2

was this meant to be posted in a thread or something?

Just a lesson for myself and others.

You probably won't find a many lot of people who stopped using Clojure on the Clojure-specific slack server.

This is an off-topic channel so I consider it fair to discuss other topics, including other languages, so long as they are in good faith and follow community guidelines. If any particular post is spam then a concern can be raised in the #spam-reports channel

The moderators could establish #rust-is-marvelous, #cobol-is-marvelous, etc., and move offending posts into those sinkholes.

Even short, fat, ugly guys deserve a chance at happiness, do they not?

I've learned about a variety of interesting things that I otherwise never would have discovered or given a chance thanks to passionate people evangelizing. I don't think that's inherently bad

The problem is disrespecting personal boundaries.... It's not like using Rust is going to change my life for ever. Being repetitively told how Rust is better than clojure after telling him to not bother me with Rust is annoying. I personally think Rust is a shitty language, but I don't repetitively tell Rust programmers how shitty Rust is.... even after being told not to bother them. I think all low-level languages kind of suck. I basically don't ever bother Rust programmers with how shitty Rust is. Developers who don't respect my personal boundaries have no place in my network. Network is net worth. Perhaps, once or twice, it's okay to mention something, but don't repetitively bother people with other languages after being told to leave them alone.

I've learned over time, when devs make large sweeping statements (e.g. "Rust is better"), to just filter that commentary out, and try to assist in building more empirical arguments backing up the sentiment. I might follow up with "why is it better?" but only if I feel like engaging at that particular moment.

For example, while I believe Clojure is a superior language in many ways, I won't just state that. I'll just ask someone using Java/Spring "how would you like to reduce your total maintainable code footprint by 50%?" That sometimes gets their attention.

@amano.kenji Is someone directly messaging you non-stop about Rust? If so, reach out to an admin. Otherwise, if it's in the appropriate channel, I think it's fair game.

Okay, as an Admin, I'm getting tired of the arguments you are causing @amano.kenji Your comments often cross the community etiquette line and this particular post goes way over the Code of Conduct guidelines for this community, so I'm going to delete it. If I see you start any more of these personal "language wars", your account will be deactivated. Criticizing any language -- Rust included -- is specifically against the tone of a community that Rich and Stu have encouraged.

If you don't like people talking about the pros and cons of other languages here, perhaps you should go find a different community, okay?

Fine. Okay.

improve docs!

I'd suggest not worrying about appearing like something. You aren't going around fixing hundreds of typos in unrelated repos all day long.

I personally always appreciate people who find and fix my typos! Go for it!

same here

There is a project for which I made a PR fixing the spelling of my own name! Ultimate vanity PR.

If a project has contribution guidelines and they were followed for a PR, then a PR should always be welcomed.

what @p-himik says. Don't worry how it might look like. They probably aren't going to judge you from a single interaction. And if they do, they aren't worth your time to begin with. Furthermore, that just might be the first commit in a long line of future code improving commits. You can get an idea how the project responds to newcomers from such small and low effort PR and judge from there if you want to get involved more or not.

Disclaimer: this is just a suggestion, I'm not advocating that you should or should not do something. Alternatively, you can spend 15 extra minutes to improve the docs around the typo or in that file – maybe reformat something to make things clearer, expand a bit, add a better example. Something that you would do if you were the maintainer. That way: • You don't feel guilty for padding the github. • The maintainers get happy that somebody gives a crap about their project. • It might become the beginning of something beautiful – like ten years of unpaid open-source labor for you.

Agreed. A typo is often a sign that something was rushed and therefore the author didn't have time to fully explain or it was a bit of a brain dump that could be explained more clearly Of course it could also be just a typo

I should have been clearer! I wasn't concerned about the repo owners themselves thinking I was just padding my github, but future potential employers. Do employers go through someones github deep enough to think that any potential pull requests are just too trivial and that being a bad look ?

No. And if someone does and just a single typo fix among other contributions is enough to change their minds, it's their loss.

It could even look good to potential future employers showing details matter to you

You could "test the waters" by offering typo corrections on GitLab projects.

In my experience employers rarely look at a CV in detail, never mind anything else.

Do employers go through someones github deep enough to think that any potential pull requests are just too trivial and that being a bad look ?I prefer to see in a different way.. How many people use the OS project, read that doc, saw the typo, just complained about it out loud, and NEVER thought about open a PR to fix it? You are helping the maintainer with that fix, improving docs is a good contribution.

As an OSS maintainer of 30+ years, I always appreciate PRs that fix typos in documentation. As Arthur says, it shows you care enough to do the work to help fix/improve the docs. So many folks who submit PRs focus only on code (and their PRs often don't include the relevant doc changes -- and sometimes don't include test changes either).

How else are the typos going to get fixed?! 😁

Is adding the 'hacktoberfest' topic toba repository topic really the only thing? I thought a project had to be posted in the hacktoberfest-projects channel on their discord server too? I also don't see a specific way to discover projects, even after registering an account on tue hacktober website 🤷 Other than searching github or scrolling through discord

Ah, this link shows the Clojure projects: https://github.com/topics/hacktoberfest?l=clojure

Yeah, to make a repository part of the event, you just need to add the topic

Nice! Didnt thought about using github search.. My bad 😅

https://finder.usmans.me/repos?l=clojure also gives a nice view of Clojure projects that are part of Hacktoberfest