we do ourselves a huge disservice by thinking of things like the AT Protocol as a “developer ecosystem” — dev rel, technical docs, dev grants…
what about the creators, the artists, the community organizers, the activists, the “non-technical” people?
can we plz not repeat the mistakes of the past?
what about the creators, the artists, the community organizers, the activists, the “non-technical” people?
can we plz not repeat the mistakes of the past?
Comments
the future is intersectional.
funnily enough got me to the point though where i dont want to learn to code, i want to write about this stuff as a non-tech person, and i refuse to have to become a techie in order to write about atproto
We make software for people and any human centered approach involves folks from the humanities in its development.
- All info would be public
- since its forum posts prob cut down on chit chat and just be sharing technical info
- everything old is new again?
Someone steal my idea plz
which is like the catchy term to say - if you want people to do something, make it easy. Stop fetishizing “doing hard things,” it’s not human nature.
to incentivize behavior, build a system that makes it easy.
to disincentivize behavior, build a system that makes it hard.
i’m advocating for “developers” to merely not have as extreme of a disproportionate influence on the tech that is going to serve us all
i think that systemic issue is part of what got us in this mess to begin with
Tools like @graze.social are a good step in the right direction. Some @glitch.com templates would be awesome too, wdyt @anildash.com?
@dame.is, I couldn't follow this convo as much as I'd have wanted to this weekend, but I saw a lot we should talk about! Let's connect and go from there?
Couldn't agree more.
We need to make things as easy as possible to non-technical people see and engage.