2,344 karma · joined November 2, 2011
I liken errors and debugs all related to heart beat and breathing rate but without information like "climbing stairs" or "changed medication", it may be hard to understand context or understand why new errors are being seen. The first question I would expect to ask when seeing logged issues, is what has changed recently that could be related to the new errors. Curious to hear thoughts on this?
I actually built software/startup related to the logging of changes (architecture change/software change/server restarts) but just didn't get traction and curious to know why it's not more interesting to people.
If we stole 100 dollars from all black people and then 20 years later decided to give black people their money back, you’d say that repayment program is racist against non-blacks?
Purposely being facetious, but seriously, we will likely see more and more of these type of rules being applied to competitions or groups. It will be harder and harder to define the rules. At some point, it becomes moot. Did I draw it? Did my toddler? Was I on hallucinogens when I drew it? Did I use computer algorithms (filters) on any form of the digital art? If the intent is to preserve the "effort" that goes into art, fine, but that will be a really gray line. I guess it's all fine to have the rules, it's similar to the natural body building competition.
"Fewer than 350 people under the age of 21 have been abducted by strangers in the United States per year between 2010–2017." [1]
[1] https://en.wikipedia.org/wiki/Kidnapping_in_the_United_State...
“When you quit something, maybe you already got what you came for?”
It’s called Refuse to Choose by Barbara Sher. She labels people like this as “scanners”. I’m not in the camp of reducing the dimensionality of humans to a single bucket/category but the description of what she calls a scanner really, really resonated with me.
I’ve found that I do start many many things and finish very few that I don’t need to. This is largely in my extracurricular time. At work and for work, I can finish things that I need to. The one takeaway from the book that helped me is this:
Maybe when you walk away from a project, you already got what you were looking for.
Maybe you already learned the thing that you wanted to learn and finishing the project wouldn’t do much more for you. And in some cases, I really believe this. For example, I always start little tech projects and I wanted to build a little audio modem in python to understand how digital modulation worked for old dial up modems. I got about 30% in and quit because at that time I had already learned quite a bit about how modulation works and finishing the project was really not interesting to me. The interesting part to me was the learning, not the finishing.
I’m always looking for similar people to chat to about this. Feel free to reach out. Email in profile.
Also, it was only a few days ago I finally learned that modem is short for MOdulator DEModulator. My mind was blown.
I definitely don’t remember much of the content in any of my college courses. But I could reimplement those algorithms today without a problem. It’s amazing how “doing” really contributes to good memory retention. It was also one of the projects that sparked a fire in me. It really showed me the possibilities of computers and computer science.
likes / (likes + dislikes)
I used this quite a lot for determining if a video was decent or not.
I’m in a corporate non-tech company and have, on multiple occasions, encountered someone who talks about algorithms as if they are from math class in high school. Pretty sure they are thinking of logarithms.