doing the right thing isn’t gendered. I assume you mean “or will you take responsibility and act like an adult”, but the way you phrased it leaves too much room to be interpreted as “don’t be like a woman who can’t take responsibility for their actions”

even if you didn’t mean it that way, this is how sexism perpetuates.

A few often overlooked ways to contribute:

• artistic contributions: logos, banners
• user interface design (I wish more UX folks participated in OSS, many projects could use the love)
• improving documentation: as a new and/or novice user, you’re probably more sensitive to jargon that developers overlook and can help make documentation more useful to others like you
• accessibility testing: testing software using accessibility settings like high contrast color schemes and screen readers. these use cases are often overlooked
• project management: participate in the issues, see if the team wants help triaging or managing a discussion/chat platform

Even if not code, some of these are quite specialized. Just be realistic about where you can add something useful.

For all of these, it is critical that you first contact the maintainers and ask what they would find useful. Be mindful that it’s also work for the maintainers to manage your help. The only “wrong” way to participate in open source is to drop a bunch of work on someone unprompted.

Generally, if a project already has a clear call for contributions or a contribution guide, that is a good indicator that the maintainers are willing to do a bit of community management to bring in help. I would only suggest investing energy in those projects if you have the choice.

It’s not striped. Those are alternating regions of UTC+12 and UTC+13.

Yes, it’s excruciatingly annoying to try to get an accurate ETA when traveling through there. The research labs in that area regularly have to throw out samples because they walk them across the lab and all of the sudden they’re an hour too old.

I use a 60% for literally everything. It’s my only keyboard. If I had more keys, 99.9% of what I’m doing would be on these keys anyways.

I’m often using vim-style navigation in editors, which is designed to minimize the need to move your hands off the home row in the first place.

When I do need arrow keys, I hold a modifier key and my hjku keys become arrow keys. For gaming I can toggle the arrow keys on so I don’t need to hold another key the whole time.

I wouldn’t say I have a wildly complex setup. There are very few custom keybinds that I use regularly and need.

Okay everyone calm down. We can’t see the other side. Everyone knows that you tie one side at the top of the wheel and the other at the bottom of the wheel. When driving, the two wheels rotate at the same speed and keep the line taut.

(please don’t ever do this)

why do the kids have full body shadows but the father only has a shadow under the newspaper!?

i guess the shadow gene was from mom?

I fell victim to this one on authentic “retro” N64 hardware, which has a hard plastic analog stick. Got an enormous blister right on the palm of my hand trying to win this tug of war. Of course, my young brain was able to hyperfocus on the game and completely tuned out any sense of pain in my hand. It was quite gruesome when I finally beat it and realized my hand was torn to shreds. I was at my neighbors place and I remember how shocked their mom was. She applied some cream that I think was meant for severe burns.

Nintendo would later run a campaign where they’d send you fingerless gloves for free to try to do some damage control on all the negative press when reports started popping up.

I don’t want to detract anything from this tram photo, but I also know that with all the content floating around in the internet these days it’s easy to build unrealistic tram expectations.

I think this is two trams, each on their own line. Notice how the roof line steps down and the window reflections seem to change halfway through. I think they’re just very conveniently aligned for the photo to make it look like one double length tram.

I’ve been there, but over the years I’ve gotten better at avoiding being in this situation.

If you are implementing something for yourself, and merging it back upstream is just a bonus, then by all means jump straight to implementing.

However, it’s emotionally draining to implement something and arrive at something you’re proud of only to have it ignored. So do that legwork upfront. File a feature request, open a discussion, join their dev chat - whatever it is, make sure what you want to do is valued and will be welcomed into the project before you start on it. They might even nudge you in a direction that you hadn’t considered before you started.

Be a responsible dev and communicate before you do the work.