note hacdias every update be a post

This commit is contained in:
Wouter Groeneveld 2022-08-16 13:35:11 +02:00
parent 49d9422618
commit b4cd9469b5
2 changed files with 18 additions and 2 deletions

View File

@ -0,0 +1,16 @@
---
date: 2022-08-16T13:30:33+02:00
context: "https://hacdias.com/2022/08/14/should-every-update-be-a-post"
---
This part made me want to reply:
> Listens and watches probably constitute a large part of the posts of this website. Are they useful however? Do they bring anything to you, or to me? Honestly, I dont think so. However, I enjoy seeing the summary about what I have watched and my listening habits.
So they _do_ bring something to you: that summary. However, in my view, many IndieWeb enthusiasts overdo this bit. I also really really love lists and summaries etc, but simply keep track of them elsewhere: in my (analog) journal. Do they need to be put online? Is that the question you want to pose?
I honestly never read that stuff if I see it in my RSS reader. **Except** if there's context added! Same for bookmarks/links: I don't care for a random link collection, but I do care for summarized ones with some context. Which ones do you recommend me as a reader of your blog, and why? If it's just stuff you're gathering, why not keep it private?
> So no, I dont think every update should be a post. It doesnt make sense
Agreed!

View File

@ -34,7 +34,7 @@ If you find new ways to connect facts, fictions, and feelings, you are _learning
For me, the problem with putting perfection on a pedestal is worrisome:
- Perfectionism leads to burnout and depression---societal problems that already get too little attention and is mostly approached from an economic perspective.
- Perfectionism leads to burnout and depression---societal problems that already get too little attention and are mostly approached from an economic perspective.
- The holiness of a craft leads to ignoring the reason why you're doing what you're doing. [Programmers who see coding as a craft](https://dannorth.net/2011/01/11/programming-is-not-a-craft/) tend to overachieve on the clean code and underachieve on delivering a product that the customer wants.
- This harsh and pretentious interpretation of creativity tends to dismiss smaller victories that are easily reachable for everyone;
- Our society is already obsessed with productivity. Is creativity really yet another beating stick?
@ -42,7 +42,7 @@ For me, the problem with putting perfection on a pedestal is worrisome:
In a way, _The Creative Habit_ is filled with contradictions. Demanding perfection requires constant practice in which your LittleC is triggered daily, but those victories are ignored for the greater good. In an early chapter, to help flex those memory muscles and get good ideas going, Tharp suggests to "get busy copying [others' work]", just [like Austin Kleon does](https://austinkleon.com/2018/02/08/copying-is-how-we-learn/): copying is how we learn. Yet, twenty pages later, it states "always be original!". Is copying just seen as an acceptable way to practice, but not as a way to generate output based on your craft? You tell me, I don't know, I was confused.
For me, the book left me with more questions than answers---which for a creativity researcher is excellent, but for a person looking for practical tips isn't. How does craft fit into creativity? How do memory models/types relate to it? To make matters worse, the term "talent" and "genius" is loosely employed as well.
For me, the book left me with more questions than answers---which for a creativity researcher is excellent, but for a person looking for practical tips isn't. How does craft fit into creativity? How do memory models/types relate to it? To make matters worse, the terms "talent" and "genius" are loosely employed as well.
Still, the book provides usable handles on how to get that habit of being more creative going, even though it won't immediately produce perfection. Tips like "scratching for inspiration" by collecting and clipping interesting things, creating daily rituals to "prepare yourself for creativity".