Let's take a moment to look at how people demanding "technology" be me humane weirdly only focus on programmers and exclude designers--the real party to blame for the attention economy--by looking at the content from:
The site's goal is to "catalyze a more humane future", which is actually a great thing, but by focusing entirely on programmers, managers, and CEOs they exclude designers. This is done because design is categorized as "art" and art is considered a "humanity" in American culture.
Artists are viewed as sort of a religious class, and in American culture criticizing the Church and religious figures is considered wrong. Even if someone isn't Christian, you'll find some religious figure they consider an authority you can't criticize. Art is that authority.
When you look through their on the Attention Economy (humanetech.com/youth/the-atte…) it's actually not saying anything incorrect. Social media companies *do* work this way, it is a problem, people should be educated about it.
The evil lies in how they word who to blame.
You start to see the first "hint" at who to blame in right away. "Artificial Intelligence", "precise, personalized profiles", all of that hints at the technology, the code, backends, with no mention of corrupting user interfaces that allow *access* to them.
The rhetoric then starts to gradually up the idea that programmers are to blame. Question 2 talks about how you apps are motivated to be persuasive to "collect data", with no mention of the use of design to do this very thing, then at the end "Apps feed this to algorithms"...
No mention of dark patterns, user interface designed to feed dopamine, the literal billions spent on optimizing only a single button to increase engagement.
It's only "algorithms"...written by programmers to collect data analyzed by programmers to...change the design.
There are many opportunities where they can mention "user interface", "designers", but they fail. They talk about how ads can be targeted, but fail to mention that targeting only works if a designer makes it work. It's "technology", but only programmers make "technology"?
Then again, they come so close "media apps are in a race for our attention...tend to promote more provocative content..." Yes, that's correct, but how *does* an app do that? Not with its user interface lovingly crafted by a team of designers.
Nope, it's "ALGORITHMS!"
Even in the middle of that they dance around designer's entire work product.
Then they make the final rhetoric twist to equating the algorithm to the design:
"The algorithm doesn't show you everything..."
"The Algorithm" doesn't show you anything.
The Design does.
Then we get the story of Morgan, a 14 year old who's a victim of the Algorithm (not the design), which is followed with the call to action, the call to destroy "our" collective enemy, the system that produces these stories...but...who makes this system? Designers? CEOs?
Nope.
This is masterful propaganda. It starts with a truth--social media IS detrimental to people and designed that way. It creates an identity (the "us) with Morgan's story. It then says the "system has harmed us in countless ways."
We need now a them to hate. Who will it be?
It then stacks the harms against us by "the algorithm", but "the system", which is never touched by a designer. Never managed by a manager. All of these harms are even more impactful because they *are* actual harms.
The lie comes next. The twist is the next line. The enemy is...
It's not designers making the same money.
It's not product managers making more.
It's not the privileged CEOs worth billions.
The enemy is "privileged engineers!" They're racist, sexist, homophobic, ableist evil people who destroy the young with their apps and algorithms.
The sad truth is, most of what this project claims about the harms of social media is valid. The problem is they've clearly crafted a propaganda vehicle that motivates people to attack and vilify programmers while ignoring designers, and I believe designers are *more* guilty.
More importantly, they're hypocritical because their own list of evils mentions propaganda and systemic oppression, and then they quite literally have crafted a masterful piece of propaganda to motivate people to attack only programmers as the cause of the problems.
Within every fascist regime, you'll find designers making the posters. You'll find movie directors crafting the propaganda films. You'll find the art professions involved in every genocide in human history.
According to Humane Tech, it's not designers, it's racist programmers.
The question I would post to people who believe only programmers are complicit is this:
How can you say programmers are the ones causing all the evil, and then also say programmers just "sit around changing the size of buttons"?
Either they're in charge, or they're not.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
People who write in a pompous "King James" style sound pretentious. This article on teaching completely loses the message because the author is trying to sound "official" by sounding "biblical". It then slides downhill from there as expected:
Clearly the author has never been poor, taught or studied in a poor school, never gone hungry, and has probably only taught people who would fit this model of "perfect". Slap all the "therefore" you want, the entire premise is disconnected from reality.
This is not supported by any research, and this is typically used to justify excluding people who don't already know a topic by claiming that a student is forever unteachable because they couldn't "handle" the artificial challenge. You mostly find this attitude in gifted kids who… twitter.com/i/web/status/1…
A thread of weird Youtube searches for when you want some soothing noise to code to. Most of these either have no talking, or if there is talking it's low whispers (because some folks like that). All of these are also Safe for Work in most places.
Here's my favorites:
1. "dugout"
It's almost always a Russian man or woman building a little house in the dirt. They don't talk much, usually there's a dog they talk to but otherwise, woods, rain, fires, cooking, and digging.
Similar to "dugout" but this is all over the world, with the best ones in Korea and Australia. A little more talking but not a lot of digging sounds and mostly just rain and cooking.
Another thought I had recently was that I would _like_ to actually buy a product from many open source projects. No, I don't want to donate, I want to pay you for a real product, so I'm your customer and you try to make me happy.
But they always screw this up in weird ways:
1. No, I don't want to buy you coffee, or "donate" because that's a dodge to avoid the obligation of treating me like a customer. FLOSS projects do this so they can get money, and then force any changes they want on your without your consent crying "ENTITLED" when you complain.
2. On average I pay say $10-$30 for a video game, and those are way more expensive to produce than most open source projects. That's a reasonable price point for a lot of things like gitea, but what do they do?
Target the ENTERPRISE market with "Call us for pricing!"
The comments are amazingly hypocritical given that...
Gitea is written in Go, which is famously run with an iron fist by Google.
The hypocrisy is simply amazing. If all of these people are so against corporate open source then why the hell are they also all using Go or anything by Google?
Because, if you're a Trillionaire then people are grateful for your table scraps and ignore their supposed "morals".
Google has:
1. Unilaterally pushed a packaging system they wanted without any community input. 2. Banned people randomly for criticizing the project. 3. Let a single engineer on Chrome decide the entire fate of gRPC on the internet.
Now I need to process the docs comment and either I support the JSDoc format--which irritates me--or simplify it.
My problem with the JSDoc format is it's just a copy of the JavaDoc format, and it's far too strict, which is a Java thing. I'd rather have it tone down the format's requirements and handle more looseness, which would make documentation easier.
But, the JSDoc/JavaDoc format does make a ton of sense in many ways. Since I'm actually parsing the file it _could_ eventually make guesses at return values, and at least show the value of default asigned parameters, but not much more without big code work.
I found it! It was in a Svelte transitions module that comes with Svelete, but...I think Microsoft is adding this copyright to all source that's compiled with TypeScript? I'm pretty damn sure that's not how copyright works, especially for programming languages.
There's no Copyright notice in that source .ts file, but this is what's in the generated .mjs file:
That confirms it then, Microsoft is plastering their Copyright on _your_ code when you use TypeScript. That's absolutely not correct, both morally and according to the law. Can you imagine if Adobe Premiere inserted a (c) Adobe on all movies you edited?