Github 101 (many of these things pertain to other places, but Github is what I'll focus on)

- Even the best still get their shit closed - PRs, issues, whatever. It's a part of the process; learn from it and move on.

- Not every maintainer is nice. Not every maintainer wants X feature. Not every maintainer will give you the time of day. You will never change this, so don't take it personally.

- Asking questions is okay. The trackers aren't just for bug reports/feature requests/PRs. Some maintainers will point you toward StackOverflow but that's usually code for "I don't have time to help you", not "you did something wrong".

- If you open an issue (or ask a question) and it receives a response and then it's closed, don't be upset - that's just how that works. An open issue means something actionable can still happen. If your question has been answered or issue has been resolved, the issue being closed helps maintainers keep things un-cluttered. It's not a middle finger to the face.

- Further, on especially noisy or popular repositories, locking the issue might happen when it's closed. Again, while it might feel like it, it's not a middle finger. It just prevents certain types of wrongdoing from the less... courteous or common-sense-having users.

- Never assume anything about who you're talking to, ever. Even recently, I made this mistake when correcting someone about calling what I thought was "powerpc" just "power". I told them "hey, it's called powerpc by the way" and they (kindly) let me know it's "power" and why, and also that they're on the Power team. Needless to say, they had the authority in that situation. Some people aren't as nice, but the best way to avoid heated discussion is....

- ... don't assume malice. Often I've come across what I perceived to be a rude or pushy comment. Sometimes, it feels as though the person is demanding something. As a native English speaker, I naturally tried to read between the lines as English speakers love to tuck away hidden meanings and emotions into finely crafted sentences. However, in many cases, it turns out that the other person didn't speak English well enough at all and that the easiest and most accurate way for them to convey something was bluntly and directly in English (since, of course, that's the easiest way). Cultures differ, priorities differ, patience tolerances differ. We're all people after all - so don't assume someone is being mean or is trying to start a fight. Insinuating such might actually make things worse.

- Please, PLEASE, search issues first before you open a new one. Explaining why one of my packages will not be re-written as an ESM module is almost muscle memory at this point.

- If you put in the effort, so will I (as a maintainer). Oftentimes, when you're opening an issue on a repository, the owner hasn't looked at the code in a while. If you give them a lot of hints as to how to solve a problem or answer your question, you're going to make them super, duper happy. Provide stack traces, reproduction cases, links to the source code - even open a PR if you can. I can respond to issues and approve PRs from anywhere, but can't always investigate an issue on a computer as readily. This is especially true when filing bugs - if you don't help me solve it, it simply won't be solved.

- [warning: controversial] Emojis dillute your content. It's not often I see it, but sometimes I see someone use emojis every few words to "accent" the word before it. It's annoying, counterproductive, and makes you look like an idiot. It also makes me want to help you way less.

- Github's code search is awful. If you're really looking for something, clone (--depth=1) the repository into /tmp or something and [rip]grep it yourself. Believe me, it will save you time looking for things that clearly exist but don't show up in the search results (or is buried behind an ocean of test files).

- Thanking a maintainer goes a very long way in making connections, especially when you're interacting somewhat heavily with a repository. It almost never happens and having talked with several very famous OSSers about this in the past it really makes our week when it happens. If you ever feel as though you're being noisy or anxious about interacting with a repository, remember that ending your comment with a quick "btw thanks for a cool repo, it's really helpful" always sets things off on a Good Note.

- If you open an issue or a PR, don't close it if it doesn't receive attention. It's really annoying, causes ambiguity in licensing, and doesn't solve anything. It also makes you look overdramatic. OSS is by and large supported by peoples' free time. Life gets in the way a LOT, especially right now, so it's not unusual for an issue (or even a PR) to go untouched for a few weeks, months, or (in some cases) a year or so. If it's urgent, fork :)

I'll leave it at that. I hear about a lot of people too anxious to contribute or interact on Github, but it really isn't so bad!

Spending 20 minutes on Youtrack and 5 on actual coding......

'i aM A VeRy pRoDuCtIvE InDiViDuAl aNd i hAvE DeDiCaTeD My lIfE To pRoGrAmMiNg'

When you are discussing about a customer issue with a service that you are using for offer your product and to understand the issue you ask a screenshot.

Later you receive the screenshot in Dutch (we are Italians) and is quite impossible to understand.
Few seconds later you remember that Google Translate for Android support the text recognition and save the day.

I appreciated a lot the Google's service quality also if I block all their trackers.

Almost all of the issue trackers

Why can't any of them just decide to be good for one kind of process. Trying to fit in support for all of them just makes the products worse.

If you really want to cater to every style of issue tracking/work queue just make a low code platform from the start instead of the unholy mess that is jira

The biggest distraction in all issue trackers is the hemorrhaging backlog of tickets that will _never_ be done, or aren't important yet.

This is why I just choose not to even bother opening it and let my PM close them out. :-)

After years of using an android wear on a regular basis I've gotten used to it, I use pujie black for a simplistic watch face and love it, I answer calls on it (although it doesn't have a speaker), and reading texts has been a lifesaver at times. I initially had an issue with the battery life but that was probably my fault for creating a really animation heavy watch face on watchmaker. Anyways while I love the thing it's really excessive (i know original argument huh?), I would love a smart band that can do all the simple things ( tell time make calls and display/read notifications ) and some awesome IoT remote functionality. After some research I found the nex band (I had actually seen this band often prior on Amazon but always just skipped over it cause I assumed that it was a fitness tracker, lesson learned again, don't assume). It looked promising, unfortunately it lacked a few key points that are essential to me. It was missing the most obvious thing, a clock, the band is split up into 4-5 rgb displays so there isn't much room for a clock. Second there is a proprietary clip on micro usb adapter (Ughhhhhh). Finally it it looks too niche and bulky. I'm keeping an eye on it cause i would love it if they at least fixed the clock and appearance issue as I don't travel much so the adapter would just sit on my nightstand anyways. Does anyone know of anything similar to the nex, everytime I search anywhere I get nothing but fitness or motion trackers.