It would be awesome if there was a computer museum where each floor was up a level on the stack (is that the right term?) where the bottom was exhibits and explanations of circuits and it went from there all the way up to apps and software at the top and at the very top was a cafe/library with public computers.
It would probably have to be a bajillion floors but I read awhile a book awhile ago that went from analog circuits up to a very simple chip able to execute basic programs and it was wild
It's time we stop fussing about source code.
It's time to start fussing about the incredible range of humans that have always made it possible.
Shout out to every woman who's had to make a post about "you guys" language. Every ESL speaker who has had to launch their own localization effort. Every disabled person who's had to remind maintainers about a11y. Every Black person who's had to deal with "master/slave" language
Shout out to every meetup and conference organizer. Every collaborator who jumps into issue trackers and constantly answers questions. Every docs writer. Every person crafting and scaling project processes. Every person who QAs (pre-!)releases as they go out.
A friend suggested today that it's time for a manifesto and I agree. Another friend in another conversation mentioned that "free software" and "open source" are not relevant terms for what we need. I also agree.
It's time for something new. A new, community-centered ecosystem.
I'm increasingly of the opinion that the way forward for us is to build a dual-purpose Commons: one where our communities can freely partake and share and collaborate and learn and build each other up, while those who seek to profit on their own terms put cold hard cash down.
Fives stages of ORM usage
1. This will save me so much time!
2. Why are these work-arounds so complicated?!
3. Maybe if I just write a few custom-queries
4. This is hopeless! Why did I do this to myself?!
5. This is my life now. Too much work to replace it.
@mayel thats a fine a approach.
It does have a repercussion on the sys admin level required to operate .
As in, microservice interdendency is harder to manage than say a monolith application or a packaged stack.
Historically that raises the bar of entry of self hosting.
For those capable it makes the going from 2-3 use ap serice to 10 an more easier tho.