I am surprised there was not an affiliate link for a book, "Pattern Matching Investing Guide - Six simple steps to generate generational wealth!" by the author of this post.
This post was one of the most strange I have read on the front page. I clicked the link hoping to read some research about pattern matching in some scientific or technical field.
Of note: This only occurred for fragments taken from an individual of the same genetic makeup(genet: basic meaning is they are a colony). Presumably, it would be difficult to recreate this at scale in the wild. I did not read past the free to read portion of the article that mentions scaling this is possible. I am curious about the methodology of that.
I find it strange that the first observance of this was a year ago, especially given how rapidly it occurs. Coral bleaching has probably been studied since the 80s when major events started being noticed. If Stephen Palumbi is reading this, I would love to read why you think it took so long.
edit: I would wager this is only the first published observance.
The data will be much clearer in the future, once all of our data has been mined. We create so much personal media and collected data that some point in the future when one entity has loaded that, a crazy real autobiography could be created.
I usually agree with this sentiment. I have a general disdain for elaborations and novelization. Get to the point! Give me the necessary facts and make it concise!
In this case for some reason, I disagree. This post is engaging for me. I sometimes elaborate on how I came to a conclusion because that journey is equally as fascinating as the conclusion itself. While reading this authors post I was happy to see what seems like a very thorough thought process.
It was actually refreshing for me to see someone write at such length and find myself engaged.
It worked for me.
Now, putting my self in your shoes, as I have regularly had the same opinion, I have more empathy and understanding for how people consume and enjoy writing.
If you think a bit, you'll notice that it's long but it's not padded for content length. It does not repeat the same thing 100 times with different wording. Every "bug" he talks about is somewhat different.
>I thought this had something to do with how I use computers but, over time, I've realized that it's mostly that people are hitting the same bugs and don't notice.
I suspect I know why they do not notice. See below.
>it works well, etc., but when I open up the thing and try it, it's in a state where the thing only works if you do quite a few non-intuitive workarounds.
I suspect most people are so inept at navigating UI because even a good UI is not intuitive to them. A bad UI is equally not intuitive. They do not know it is a bug because everything is a bug to them.
I can use a novel UI and figure out where to find what I need to do very quickly. In my experience with lay people, they can use the software for a decade longer than me and still not understand some of the capabilities and navigate to utilize them as I can within a few minutes or small amount of research.
>I suspect most people are so inept at navigating UI because even a good UI is not intuitive to them. A bad UI is equally not intuitive. They do not know it is a bug because everything is a bug to them.
This seems a weird thing to believe given that we know there are such things as black UI patterns designed to keep users from doing things they might want to do, but which the company might not want they do yet still are obliged to provide the possibility of doing.
As a general rule I think I am pretty good with finding out things about software, for example in pretty much every company I've worked at I'm one of the only devs who learns Jira's query language, and how to make my own dashboards to organize things, but I do at times experience UIs that I either must believe are malicious or buggy, and I stand by that interpretation no matter how they people who work at the company like to claim it is working as intended.
But I have also experienced some times when I think the way this UI works must be a bug, because otherwise the people who designed it must be incompetent idiots and also, given laws about accessibility requirements, potentially on the hook for some monetary payments in court soon.
My interpretation has been that I am often to quick to think things are bugs and not worthwhile using because I am familiar with how buggy things can be and still "work" somewhat, and also that normal uneducated users will try to soldier through things I just give up on because they don't realize that a thing should not be working the way it does, they think it is them that are wrong - as evidently you do as well. I think it is frankly a strange viewpoint to have in the world of software development, which world I assume you are a part of?
>I just give up on because they don't realize that a thing should not be working the way it does, they think it is them that are wrong - as evidently you do as well. I think it is frankly a strange viewpoint to have in the world of software development, which world I assume you are a part of?
I agree with, "They think it is them that are wrong", essentially. The end users that I deal with at the consumer level usually think they messed up when something does not do what they thought it was going to do.
>as evidently you do as well. I think it is frankly a strange viewpoint to have in the world of software development
Can you elaborate on this statement? I do not know whether you are agreeing with me and implying we are both strange or you are implying that I think that way and that is strange. Either way, I am not a developer, yet. I dabble in things.
I think, knowing that dark ui patterns exist - which I called black ui patterns by mistake earlier, I unfortunately very tired the last few days - and given the assumption I made that you knew something about how often bugs can actually come about, that thinking the users are to blame is very weird.
The users who don't know how often bugs occur and so forth always think that it is them to blame, but people who know about bugs and how things are made should probably think otherwise, but it seemed the way you phrased your initial post that you are in agreement that it is the fault of the users for whom the UI is always nonsensical and who never put in the necessary amount of effort to understand the UI.
It is possible if you consider madaxe_again's theory(comment here). If the debris just started descending without interruption, there would be no receding.
Brilliant analysis! Although china is notoriously bad at reporting earthquake data, I assumed in this case they were open and honest. It made sense that an earthquake would trigger this event. I do not fault anyone for interpreting the data this way. The USGS has been the agency I most trust in the federal government.
USGS is a fact finding organization. They do not regulate. They have been around since 1879. The land surveys they have done made huge impact on society. The reliability of surveys that they have facilitated has made an impact on industrial civilization that few will understand or ever hear about.
Perpendicular is not the scientifically best path. 45 degree angle is the best angle if the threat is moving toward you at the same velocity that you can move. As the velocity of the threat increases, the angle gets closer to perpendicular. The size of the threat and distance of course matter as well. I think about this before tree felling. In chainsaw classes they teach you to move at a 45.
This post was one of the most strange I have read on the front page. I clicked the link hoping to read some research about pattern matching in some scientific or technical field.
reply