This and the post yesterday about adding latency to websites reaffirms an idea I've been thinking about lately - adding friction back into digital processes helps break some of the addictive power they have.
Imagine if you had to use a printer to print out your facebook feed when you wanted to see it. Then, in order to interact, you had to write on that paper the comments, likes, etc. that you wanted to transmit and scan it back into the system. That mode of interaction seems "primitive" compared to the way we use things on our phones, but I think carries with it a lot of nice advantages like introducing time buffers for your mind to catch up to your impulses.
Additionally, you could rephrase from "downvote" to "rebuttal", which I think makes it more clear that not only is the opinion/post unpopular, but that there is information that contradicts the OP's post. It could make for a more substantive phrasing
I just was recently introduced to this and other discussions on city planning by a couple of great youtube series by donoteat1[1]. "Franklin" and "Power, Politics, and Planning" are some of the best and most humorous examinations of topics like parking minimums, public housing, gentrification, etc. I've come across. The presenter is highly left-leaning, but also knowledgeable and backs up his positions with data. Agree or disagree with his views, it's informative either way!
It's opened my eyes much more to how cities are actually planned and the problems posed by politics over the ages - the conflict between public good and private interest, and how specific policies affect cities and their accessibility to people of various economic statuses. Would recommend if you enjoyed this article and want more related topics to learn about.
Another way to say this could be if you decide to take the route of explicitly not solving an edge case or write throwaway code, that feature becomes a leaf until the branch of immature code can be pruned and a new, stronger one put in place.
It doesn't become a leaf automatically. You have to force it to stay a leaf. If you don't find a way to do this, and if things grow on top of it, then you are in trouble. This is hard to do in most architecture patterns.
I like the presentation a lot, but after looking at the features tab I'm left wishing there were some sort of interactive demo.
This looks like a really cool project! I like the idea of a journaling tool that also helps you reflect at a meta-level after you've entered in your momentary feelings.
