This reminds me of my intro to Computer Science class. My professor started us off with the Peanut Butter & Jelly Algorithm exercise [1]. I loved it. Nothing destroys your confidence quite like seeing a grown woman smash a peanut butter jar as hard as possible into an unopened loaf of bread.
I actually remember doing this in either grade 5 or 6, as part of a unit on procedural writing or something.
The entire class was divided into groups and tasked with making the teacher make a sandwich that we wanted. She just waited in front of a whole bunch of jams, mayo and cut up veggies and would “run” your paragraph to the letter. Everyone’s laughing while she’s spreading raspberry jam on lettuce but then the group realizes that’s the snack they’re getting.
That seriously still sticks with me almost 2 decades later!
This is not a judgment on you, or what you did, but I don't know if I'd define that as "reading." I did essentially the same thing you did, but I have always called it "skimming." With articles like this, I tend to skim first, to see if it's worth a deeper reading. to answer your parent comment, I could not have deeply read this post in only 3 mins. It likely would have taken 5 or more.
Different Red Hat employee here, that said, this opinion is my own and I have no real authority to say anything beyond my experience. I, in my job, have a lot of contact with IBM folks now for obvious reasons, but I think it's a slow Red washing rather than the other way around. The independence of Red Hat is fiercely defended and is largely respected, even by IBM. I think we all want this to work as it is, rather than make huge changes, especially culturally.
IBM employee here, can confirm (the Red-washing) after having developed a product that HAS to be running on OpenShift and HAS to go through RedHat's horrible scanning and catalog system. Of course this is in addition to IBM's existing horrible scanning and catalog registries. It's a red layer on top of existing blue layers of tape. It's multi-colored bureaucratic tape all the way down.
This is an interesting project for sure, and I see some great potential. I tried out a few phrases, including the one below that include commonly used words in "toxic" comments, but are not actually insulting anyone. This still had a high score (0.74).
> Unfortunately, most Americans are ignorant of the science about climate change. This is not because they are stupid but rather because they do not have all the data, or the data they have is unreliable.
I'm in no way saying this is the best way to communicate that message, and this could prompt a writer to re-phrase, but I don't know if I'd claim that this is toxic. I think that this could be a good tool, but it's clearly highly dependent on "common" understandings of words rather than actual definitions. Maybe that's the correct trade off though.
I fully agree. Even on topics I feel I know well, she's 1) shown me something I didn't know, and 2) shown me how a "newbie" could see the topic, making it easier for me to help teach/mentor someone else.
I tried to find some external tooling to help with this, but was unsuccessful. In the end, I just built a (hidden) feature into the app that intercepts and displays the key presses in that little bar on the bottom before dispatching the events to the actual handlers.
I can't recommend this book enough. As a long-time Vim user, I still learned a few things after reading this book. Drew Neil is a pretty awesome person too.
This is not an original opinion, but I love her style of writing. I can feel the pure unadulterated joy at learning these things. Sometimes I learn along with her, sometimes I am seeing an old subject through new eyes. Always, it's worth the read.
[1]: https://duckduckgo.com/?q=algorithm+for+making+a+peanut+butt...