21–30 of 378 posts
I'm basically conning myself into liking the task :)
Earlier quoted context omitted.
This idea is captured nicely in the book "Art and Fear" with the following anecdote: "The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroo…
Maybe this works for potters but I don't think it'd work for developers. If a compSci lecturer suggested one group would get an A for writing a perfect, bug free app and the other group would get an A for writing 50,000 lines of code, I wouldn't expect the group writing as much code as they could to make the best app.
That matches "the quantity trumps quality" idea above more closely in our industry.
Anyone tried using a chain calendar? I used an app that tracked how many days in a row I meditated and that's the first time in my life I was able to do a good habit consistently for 15 days straight. I didn't want to break the chain! Later I used the same idea for studying every day, started with a few minutes and worked it up slowly. Eventually, I was able to concentrate for long periods of time. That sense of mome…
Earlier quoted context omitted.
This idea is captured nicely in the book "Art and Fear" with the following anecdote: "The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroo…
Maybe this works for potters but I don't think it'd work for developers. If a compSci lecturer suggested one group would get an A for writing a perfect, bug free app and the other group would get an A for writing 50,000 lines of code, I wouldn't expect the group writing as much code as they could to make the best app.
Funny to read as we are probably procrastinating.
>Start sloppy >Another trick to start sloppy - you might have high expectations of your finished work. >You want to write a great book, not just a good one. Or create a stellar artwork, or start a great business. >All those expectations can put more pressure on you than you can bear, leading you to avoid it by procrastinating. >Instead, you can escape those expectations by starting deliberately badly. I use this one…
This idea is captured nicely in the book "Art and Fear" with the following anecdote: "The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroo…
Earlier quoted context omitted.
This idea is captured nicely in the book "Art and Fear" with the following anecdote: "The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroo…
Maybe this works for potters but I don't think it'd work for developers. If a compSci lecturer suggested one group would get an A for writing a perfect, bug free app and the other group would get an A for writing 50,000 lines of code, I wouldn't expect the group writing as much code as they could to make the best app.
Consider someone with little to no experience with programming trying to build a single app and planning it out and refactoring and refining it continuously, compared to constantly creating and archiving multiple toy prototypes of the same app and then considering the best among those.
(The app's size and complexity should be commensurate to a single clay pot in a ceramics course.)
It requires the students to actually try to make something of quality, sure, but only to the same degree that the students in the original (apocryphal) story did- after all, those students could easily have shown up with a pile of baked misshapen clay instead of proper pots.
Earlier quoted context omitted.
This idea is captured nicely in the book "Art and Fear" with the following anecdote: "The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroo…
Maybe this works for potters but I don't think it'd work for developers. If a compSci lecturer suggested one group would get an A for writing a perfect, bug free app and the other group would get an A for writing 50,000 lines of code, I wouldn't expect the group writing as much code as they could to make the best app.
creating 1 pot using 10 tons of clay = writing 50,000 lines of code for 1 project
vs
writing lots of different projects = creating lots of different pots.
The last two weeks I made it a goal to run 5km every morning. A few times, particularly today, I felt lazy and run down, but I got out of bed anyway and told myself that I'll at least walk. The next thing I know I'm running and feeling amazing and on to set one of my better times.
The point: When you tell yourself "just one more game" or "just one more post", or "just one more video" and end up doing 3-5 hours more, do that with your other tasks too! "just one line of code", "just one tutorial", "just one rep", "just one line of reading/writing".
We all have this amazing mental tool that we've been honing for years, the tool of self deception. Time to use it for good and not evil.
Copied from: [0] - https://www.reddit.com/r/productivity/comments/cdir3g/trick_...