Don't you want to live in a world where people make decisions based on observable things, rather than blind faith in arbitrary nonsense?
You can't reason with a religious person. Their axioms can be completely incompatible if, for example, they believe the afterlife is more important than actual life.
"Wants to work with" doesn't apply here. This is what the phone does by default, so it's not a conscious choice of the user. Also, if the college had written the `accepts` field on their form correctly it would have been converted to JPG automatically when they uploaded it.
Huh. So, according to the other comments, if they'd set the `accepts` on their form to MIME types instead of extensions, the browser would have converted the file to a JPG automatically.
Definitely right. Sometimes I look at notes I made for myself, telling myself what to do, and then ultimately rebel against my past self because I don't want to do what I'm telling myself to do.
Systems are better when they're an augmentation of your memory that you can appreciate. For example, I always put events in my google calendar so I can remember when they are and catch overlaps early.
I've had a bad relationship with todo lists. They get stale really quickly. If I look at a todo list that's a few days old, I might think, "Why should I do that now? Why should I factor the work in this way? Just so I can say I'm done with this item?" In practice, the way I factor a task changes constantly. So now the way I do todo lists is more like an aid to my memory. When I have time to do stuff (which is rare) I'll write down the things that are most important at that exact moment. Sometimes I'll skim through todo lists from previous days to jog my memory, but I won't copy over everything. I'll arrange the things into an itinerary for the day and see how many of them I can get done. Usually it's not all of them. And that's OK.
The additive/subtractive colors thing is has a really neat sort of symmetry to it. That's how I knew it was the correct explanation. There was no such beautiful internal logic to the Red Blue Yellow system and I couldn't figure out how people came up with it.
I never believed my teachers. As early as 4th grade they were treating me like a troublemaker for not following rules like their three-paragraph essay format.
I don't like the idea of having authorities on knowledge. I much prefer Montessori or Socratic teaching methods, or explorations. They're harder to do, but they produce a better understanding of the material and they allow the student to teach the teacher as well.
I remember this one distinctly because in school they just gave me a handout and asked me to come up with the explanation myself. I thought about it. I didn't know. It seemed like if you had an angle of attack then the air would hit against the bottom -- like a knife would want to continue to travel straight through a fluid. I didn't know what the significance of the curve over the top of the wing was. They tried to guide me toward the equal-transit-time explanation and I was like, uh, ok, is that really true? I remained suspicious of this for a long time.
My high school art teacher made us make color wheels using red, yellow, and blue paint. She showed us books that use these "primary colors" and said that this makes them more pleasing to children.
I thought about it for a moment. If these are the primary colors, why aren't they what printers use? Printers use cyan, magenta, and yellow. And there's a great symmetry there, since those are all the secondary colors to light's primary red, green, and blue, which are the colors used in computer monitors. And the only thing that makes these colors primary to us is that they're the colors that the cones in our eyes perceive.
So I decided to experiment. When I made my color wheel, I substituted blue for cyan and red for magenta. The color wheel I produced was much more vibrant and beautiful.
There are a lot of things my school teachers tried to teach me that show up on wikipedia's common misconceptions list. For example, the "equal-transit-time explanation of aerofoil lift". I got pretty jaded about this stuff. Now I don't trust anyone's explanations unless I can understand them on a deeper level.
I've used HOCs to share behavior between React components in the past. You can also accomplish similar things with the Render Props pattern, depending on how you want to organize code. Using hooks is new to me. Anyway, my point is there has always been ways to factor out the behavior from React components. I'm pretty sure the reason they don't encourage factoring it out completely is so that DOM events are still handled in the domain of the UI, since they don't deal with types in your model.