If you want to get into doing it, I found searching through a lot of note taking applications until I found something I really liked helped me remember to go do it regularly.
For FOSS stuff a lot of people like Joplin, and I could certainly recommend it. Personally though, I really like Obsidian for its backlinking and graph view features, but it's not open source.
Furthermore, just carrying around a notebook and a pen everywhere you go as a habit helps a lot. I got into the habit of doing this by maintaining a personal journal for some time. For writing effective notation on paper which can easily be digitized, I would recommend looking into "bullet journaling" methods, and again, finding a notebook and pen that you really quite like, helps a lot to make the experience enjoyable and develop it as a skill.
I learned this lesson pretty quick when working in IT.
It's not always feasible to document everything as it happens, but I definitely learned to do so if I had the time and means to while I was doing the thing.
Just started at a new company with 0 documentation, they're super psyched that I've actually been writing down all their processes/procedures/configurations etc. as they explain them to me/as I work with them.
I see, thanks!
Thanks Dessalines!
Fascinating, didn't know moderators could investigate such things effectively (I was unaware of any mod tool that made that easy to do).
Its early so I only had time to take a cursory glance and the vote counts were still looking the same to me - which one had the votes removed after your report?
Good to hear nonetheless, definitely felt something was up, thanks!
To make it clear what I am talking about - I would expect any voting distribution for 16 votes to be at least semi-random on a controversial comment, in example such as this:
However, the distribution as it occurred looked like this on the first 16 votes:
A controversial comment will have such a ratio, but any comment controversial or not will almost never have this kind of distribution unless there are multiple accounts waiting for vote up events to occur so that they can send a vote down.
I can believe this happening 2, 3, even 4 times by chance, but not 8 times.
I'm entirely aware, I'm specifically referencing my top level comment which at the time had no replies.
Additionally, what you are describing does not explain both a vote up and vote down, occurring at the same time 8 times consecutively, so I'm not quite sure I understand what your point is as what actions occurred prior to hitting the button doesn't enter into what I'm describing as far as I can determine.
Even if people read a thread before scrolling back up and hitting the up or down button, them hitting that button at the same time as someone else hitting the opposing button 8 times in a row within a few moments of each other is still a statistical anomaly.
See my other comment in which I graphed what I am talking about in order to better explain myself.
As I said, certainly possible, I was just surprised by the distribution over time, not the distribution of vote type.
Yes, it's true that some good things have been added, I suppose my concern is just that I feel the negative things in the case of firefox hold greater weights when compared to the positive things they have done.
As a euphemism; a cruise ship adding a bowling alley, better seating, and fine art to its interior is neat and might make it look better and more convenient but it doesn't mean much to me if they also added an engine which spews 50% more pollution into the atmosphere and poisons me.
Certainly possible but I'm sure the odds are astronomically low. After I saw this happen 3 times I started refreshing every minute and each time there was a change, both counts had increased, and this happened 8 times in a row. I could see a distribution happening of something like a vote up at minute 2, vote down at minute 3 vote up at minute 12, vote down at minute 20, etc, but this was - vote up and vote down at minute 5, same thing at minute 11, same thing at minute 16, etc, 8 times concurrently (the minutes listed here are an example, I wasn't tracking exact time between events).