"My waking, working life, like my dream life, can sometimes feel like a series of epiphanies that are just beyond my reach — nonsensical symbols that I can't read and invisible objects that I can't see. I still dont know where ideas come from, but I now seem to at least know something about my own methods for finding them, which I keep holding on to even as the realities of my professional and personal life evolve. I read around and talk to colleagues, trying to keep a steady flow of new ideas in my daily work. Honestly, the homework never stops, it just isn't graded."
This is where I scribble on the web.
"Map becomes territory, and as anyone who has kept a journal knows, soon you witness the present as you plan to record it, seeking out events good or bad that are likely to yield something worth recording. As the old try and fail to teach the young, life comes at you past."
"I have learned to not listen to what companies say, because they never really commit to it. Google: “don’t be evil”. Facebook: “WhatsApp will remain independent and free of ads”. Etc. Companies need to be understood not as personalities, but as game theoretic agents following the simple rules of capitalism."
via andre staltz
Cis is treated as the null hypothesis. It doesn’t require any evidence. It’s just the assumed given. All suspects are presumed cisgender until proven guilty of transsexuality in a court of painful self-exploration. But this isn’t a viable, logical, “skeptical” way to approach the situation. In fact it’s not a case of a hypothesis being weighed against a null hypothesis (like “there’s a flying teapot orbiting the Earth” vs. “there is no flying teapot orbiting the Earth”), it is simply two competing hypotheses. Two hypotheses that should be held to equal standards and their likelihood weighed against one another.
to focus on “a discussion about power, and conflicts of interest” and “social capital”…
I’ve said this here before, but if you want to get anything to happen, somebody has to do it. If you want it to last, some people need to be committed to it for as long as you want it to last.
Those people will have more whatever-you-want-to-call-it than people who just came yesterday.
People who did more work will have more of that than people who did less work (usually, but not always, I think unfortunately).
At some stage, a core or inner circle will form. And more hurdles will appear for new people to move inward. This is inevitable, I think. No point in complaining about it. No use decrying power and calling whatever-it-is social capital as if the people who did the work are necessarily capitalists and should be demonized.
It’s like a cell has a nucleus and a membrane.
But a healthy human-organizational cell continues to incorporate more people and help them move toward the nucleus, and when needed, divide into more cells, and expand into an organism. (Sorry for the metaphors, but they seemed apt, and I mean them as more than metaphors…)
When does the inner circle decay and threaten the health of the cell and and the organism? How do the members of the inner circle refresh the organism?
overheard on scuttlebutt
I'm convinced that summarizing books is an underrated skill for learning
Not tweet-sized summaries
Not Cliff's Notes
Not bullet points or "main takeaways"
Not slide decks
Multi-thousand word, in-depth, comprehensive summaries of the book's message are incredibly valuable
via @fortelabs on Twitter
"I like software, and I like making it. It's like writing a story that gets up and walks away, a story that can be printed infinitely and distributed effortlessly."
In my teens I would live vicariously through the media I consumed. In my twenties, I'm living vicariously through the ideas I read about and the online communities I join.
Attaching myself to labels like #solarpunk #surveillancecapitalism #anarchist #metamodern (& previously, #effectivealtruist #singularitarian) is just another way to add meaning to my life without doing anything meaningful.
We internalize the simulation we are presented with, like being read into a character in a book. Our own rigid imagination guides our perception, generating predictable ideas without realizing we never created anything, just dusted something off and called it our own. Given only outmoded expressions that fail to perform even as a bland medium of a culture's desires, we have completed the recipe for empty repetition of the same old stories... Why do you wonder where culture has gone?
This lesson talks about the MVVM (Model View, ViewModel) App architecture pattern. The idea is that you should break up your code into different files/classes that are each responsible for a specific job — basically, create a separation of concerns in your app, instead of doing all the logic for everything in random activities and fragments.
Separation of Concerns
Divide your code into classes, each with separate, well-defined responsibilities.
Our App Architecture
We're going to be working with three (3) different classes:
UI Controller: Includes activities and fragments. Responsible only for user interface and user input related tasks. You should take any decision making logic out of the UI controller. It is not responsible for the calculations or processing that decides what actual text to draw.
ViewModel: The purpose of the ViewModel is to hold the specific data needed to display the fragment or activity it is associated with. ViewModels may also do some simple calculations and transformations on that data so that it is ready to be displayed by the UI Controller.
LiveData: The ViewModel will contain instances of a third class,
LiveData. LiveData classes are crucial for communicating information from the ViewModel to the UI controller that it should update and re-draw the screen.