2023.12.24.

2023.12.17.

Cool iCal tips from 43folders

https://web.archive.org/web/20060819234608/http://www.43folders.com/2006/06/29/ical-tips/#comment-8784

Planning out my time with iCal calendars and groups, and being able to click back and forth between that planning view and David Allen’s “hard landscape,” is very appealing. I’d forgotten your earlier post on this topic, but I’ll be returning to it for ideas.

The printed calendar I carry with me doesn’t have the kind of detail yours does, but it does have the advantage of giving me four months of schedule in my back pocket. Do you print your calendars to any special size—e.g., for pasting into a Moleskine—or just to letter-sized?

The daily agenda for a trip sounds like a great idea for many (salesmen, in particular), but my trips are almost always focused on a single project. I’m more likely to be juggling appointments on the days I am in front of my computer.

https://web.archive.org/web/20060819234608/http://www.43folders.com/2006/06/29/ical-tips/#comment-8841

Thanks for mentioning iCal. I have ditched eveything else and find that iCal has everything I need for GTD.

It’s a calendar, to-do (to-do’s can be sorted by calendar, too, by the way) list, tickler file (just put “See File under “file name” in the notes field) and, well, everything else that GTD requires.

Here’s the reason I forced iCal to work for me: I don’t carry a PDA, just a sony ericsson phone, and everything that is in iCal, including tasks and alarms, are synced with my phone quickly via iSync. I even have a script to open iSync, sync them, them quit iSync, all by hitting Shift-F8. So I just tap the hotkey when I get to my mac and leave it, and all my stuff is current all the time and very portable, always in my pocket.

Another great thing, it doesn’t just import from iCal to the phone, it syncs them, so when I’m out and I need to add a task, I can do it shorthand on the phone and it will sync to a calendar called “Inbox” in iCal when I sync up.

I would love to use fother fun GTD software, but alas, I don’t need to. If you carry a syncable phone with you everywhere, I highly recommend tweaking iCal to work as your GTD system.

Did I mention there’s tons of little apps and even widgets that let you see your iCal stuff at a glance without bringing up iCal? Very nice.

2023.12.10.

Exploring the database format of Things

I was think about switching from #Things to #TaskPaper. Task-management is the last piece where I still don’t use plain text, albeit using Markdown in Things notes (see 2023-12-09_12-09 Things to-do journaling template).

  • Why I like Things
    • Nice UI
    • #Markdown support in notes
    • Really good #Shortcuts integration
    • iOS and iPadOS versions, which are at the same level of excellence
    • There is a link to everything
    • No attachments
      • People tend to dislike this. Having no attachments support forces me to have better attachment management in dedicated apps like DEVONthink
  • Why I don’t like Things
    • Uses a database
    • Sync is not end-to-end encrypted
    • No Spotlight integration
      • On the Mac, I periodically run a script which creates .hook files linking back to projects as way to have a fake Spotlight index.

Knowing that the database is fairly easy to understand, I’m a bit more confident that I can export my to-dos out of Things. I can even use the SQLite database directly as an archival format too.

The non-existence of end-to-end encryption is still bugs me though.

2023.12.09.

When we keep a journal we automatically keep bookmarks for ourselves

Programmers complain about distractions all the time. But when we journal and document our actions, we can drop them in the moment and pick them up later from where we left off. It’s like bookmarks for our lives (see next actions 2.7).

We will also have a history of our actions in the journal, which can be used as a reference when we have to go back in time.

#Journaling #NextActions

I can keep automation scripts in Git repositories

Automations should be exported into Git repositories. They have to be installed since most automation tool expects a script, a shortcut, or a macro to be imported into a library, or installed in a special place, but we can still export and assemble files from our tools into a repositories.

Keeping these repositories up-to-date can be a burden, since we have to manually export files. But it’s still beneficial to keep these under version control, since sync problems can happen, so we can go back to a previous version more easily.

Keeping an issue thread ensures we have background information about code changes

  • Timestamped documentation
    • #TBD…
  • A timeline of changes
    • As the idea develops, we can see a timeline of changes in the issue.
    • The timeline of changes is similar to how Zettelkasten threads work. The only difference is that we can’t have indentation with timelines.
  • An issue thread is like background information on what decisions we made about our code at a point of time.

Documentation should live in the same repo as the code

  • Documentation review should be part of the code review.
    • By forcing us to store the documentation in the same repository, we can keep it up-to-date with the code directly.
    • We can catch missing documentation updates in PRs while doing code reviews.
  • The documentation is versioned in a way in Git that ensures it aligns with the same version of the code, thus automatically synchronizing its history with older versions of the app.
  • Question: how we can migrate existing documentation from an external wiki into the repository?

#Linking

We don't need to create a PR if the commit is atomic

When committing atomic changes of a “thing”, it has to have the following items included:

  • Actual code changes
  • Tests/specs
  • Documentation
  • Reference to an issue number (or a link to an external issue tracking software)

If the commit includes these, we can directly commit it into the main branch.

However, this wouldn’t work in a team setting since it requires too much discipline from other people. Also committing directly to the main branch can be dangerous.

#Development #Linking

Things to-do journaling template

This is my standard notes template for journaling about a #Things to-do in its notes.

# 2023-12-09_12-07

Notes about what happened with the to-do…

# 2023-12-09_12-09

Yet more notes about what happened with the to-do…

#Journaling

Displaying Hookmark icon on the Dock

Source: Hook: getting out of the Dock - Discussion & Help - Hookmark Forum

To display the icon on the Dock:

defaults write com.cogsciapps.hook background.app.mode 0
  • #BugsQuestions
    • The problem with the Dock mode is that the Hookmark app still kept active after copying the link.
    • It doesn’t switch back to the original app.
      • LaunchBar has a Dock mode, but it doesn’t steal the focus when it’s activated.

To revert it to be a background only app:

defaults write com.cogsciapps.hook background.app.mode 0

I’m going to keep my interstitial journal separate from my Zettelkasten. My journal doesn’t need Git and all the bells and whistles of my Zettelkasten. I just want to have a simple place to quickly draft ideas.

Some notes may move over to my Zettelkasten, which I can automate, but it’s very private, so I don’t want to accidentally publish something.

#Journaling #TaskPaper #Zettelkasten

The Arc style tab and bookmark management

People seemingly like Arc because of its tab management. I think it can be replicated with Safari as well using tab groups.

Arc doesn’t even have bookmarks, but Safari does.

  1. A bookmark can live in the temporary tab space
  2. It can be moved into more specific tab groups
  3. From here it can be even bookmarked into my Inbox tab group
  4. I can organize the bookmark in my Safari bookmarks, or move it into other apps for long term storage.

I should manage my Pull Requests like this, since they are very important.

2023.12.08.

I can quickly search today’s notes by typing fdate into The Archive’s omni bar. Typinator will expand today’s date.

I also modified my Open Current Note in Zettelkasten shortcut to give me an option to open the note in The Archive too. I just figured out that it searches for the note and gives me backlinks.

#Shortcuts #Workflow #Journaling

Simon Willison

Simon Willison is the creator of Datasette, an open source tool for exploring and publishing data. He currently works full-time building open source tools for data journalism, built around Datasette and SQLite.

Prior to becoming an independent open source developer, Simon was an engineering director at Eventbrite. Simon joined Eventbrite through their acquisition of Lanyrd, a Y Combinator funded company he co-founded in 2010.

He is a co-creator of the Django Web Framework, and has been blogging about web development and programming since 2002 at simonwillison.net

#Person #Development #Web

Refactor Things journaling

  • Create a repository for the original shortcuts
    • automation-things-journal
  • Journal About Things To-Do
    • Save the Things URL of the selected item
    • Create a new Drafts document with the date, published, things_url, title attributes in the frontmatter
    • I could also create a new text file directly using iA Writer URL schemes, and the Shortcut
      • Get the Things URL
      • Format the frontmatter
        • title → name of the selected Things item
        • date → the current date
        • publishedfalse
        • things_url → URL of the selected Things item
      • Create the Markdown file with a timestamp and a slugged version of the selected Things item
  • Open Things To-Do Journal

#Journaling #Things

Refactor checklist journaling

Automation repository creation

I created the new repository for my first automation script. https://github.com/zsbenke/automation-taskpaper-checklists

It would serve as a demo.

  1. Include all files that are needed for the automation.
  2. Create a README.md file which describes what it does.
    • I could include the keyboard shortcut which triggers it.
  3. Record a demo.mov file
  4. Upload the demo.mov file to Vimeo with the name of the automation
    • Automation – Automation Name
  5. Link the demo.mov from Vimeo in the README.md

#Automation #Reference

Plans for TaskPaper journal changes

Since I want to use TaskPaper as just another editor app, I should move my interstitial journal file out of it.

I cancelled some parts of this project. → 2023-12-09_10-04

#Thread #Shortcuts #TaskPaper #Journaling #TheArchive

Switching to my Zettelkasten as a journal

I think I’m going to give up my TaskPaper journal. I just think The Archive app makes so much sense as a journal and Zettelkasten.

I can develop notes and journal about stuff here. It’s even have images integration, and I can use the old style Notational Velocity app.

Increase your productivity on personal projects with comprehensive docs and automated tests

  • Author: 2023-12-08_20-16-simon-willison
  • Increase your productivity on personal projects with comprehensive docs and automated tests - DCUSDEVONthink Archive
    • The Perfect CommitDEVONthink Archive
    • Using PRs and squashing commits is similar
    • GitHub issues can be archived → https://github.com/dogsheep/github-to-sqlite
    • Using GitHub as Zettelkasten
    • 2:58
      • Perfect commit
    • 4:00
      • Commit changes of one thing
    • 5:30
      • Incrementally building tests
    • 7:32
      • Documentation should live in the same repo as the code 2023-12-09_13-27
      • Catch missing updates in PRs
    • 8:55
      • Documentation tests
    • 10:10
      • Issue threads
    • 12:10
      • It’s like Bike planning
    • 13:40
      • Timestamped documentation
      • A timeline of changes
      • Keeping an issue thread ensures we have a background information on a code change → 2023-12-09_13-35
    • 14:08
      • Issue driven development
    • 14:55
      • Have this for Shortcuts
      • I can commit and export a shortcut
      • Keep them in one repository
      • I can keep automation scripts in Git repositories 2023-12-09_16-05
    • 15:20
      • Get back to something when you have notes
      • Programmers complain about distractions
      • When we keep a journal we automatically keep bookmarks for ourselves 2023-12-09_16-10
    • 16:40
      • Issues for everything, even life stuff
      • At this state, this is a project management app, like Things
      • I keep stuff like this privately, not in GitHub issues
      • I link it using Hookmark
    • 16:56
    • 18:14
      • Publish Markdown files to GitHub issues
      • I can create a new comment to have a way to I document my stuff
      • It will make my work more transparent
    • 19:30
      • Have an output about what did you done
      • Journal about what you did
      • Twitter threads
        • Or small status blog posts
      • PR description
      • Get a blog

#Thread #Literature

2023.12.06.

Using my Zettelkasten in DEVONthink

I indexed my #Zettelkasten notes in DEVONthink and also turned on syncing without uploading indexed items. On other devices, I also want to have this database synced, but I should also set it up the same way as on the original laptop.

I want to use DEVONthink to browse my Zettelkasten locally. It can even get and parse hashtags. But I can’t use hypens in the name of the hashtag for the Hungarian suffixes.

2023.12.01.

2023.11.03.

Leave permanent note linking to the Mac

  • Writing notes requires a different environment than linking notes.
    • Linking is about finding the connections between notes, while writing is about getting out our ideas from our fleeting notes in a focused manner.
  • When I do linking, I need to have a bigger display with multiple notes open so I can easily review them. An iPad screen size it’s just too small for this activity, so I like to do linking on a Mac.
    • Can linking be done on an external display on iPad using Stage Manager? 2023-11-17_21-44

The capture log is an append only system

This note connects “2.16 Appending information is way to keep a history of changes” to “2.14.12 The capture log is an automatic journal”.

So I can see the capture log in the descendants of “Appending information is way to keep a history of changes 2.16”.

2023.11.02.

Git can be used for keeping the history of non-code based source files

  • I can set a Git repository for almost any source material which I’m working on, and I’ll have a nice history for these files.
  • Keeping a Git repository only works for file-based apps. It doesn’t work for database based apps like Ulysses, or Bear.
  • On top of Git, it’s still worth to keep manual versions for writings around, especially after reaching a milestone like the first draft, the first edit, or the version before spell checking. Manual versions usually work in database based applications too.
    • 2.16.3 Keeping manual versions in Ulysses.

The capture log is an automatic journal

A capture log is a journal-based version of the inbox, where ideas are getting captured. This was an idea mentioned by Merlin Mann 2024-10-23_08-21-merlin-mann for the first time, where he wants to yell into the void and let Siri capture his ideas, with automatic metadata like creation date, a location, and optionally the weather.

A capture log is kind of a journal about our ideas. It’s like a tail for our life.

There is a difference between the Inbox and Storage

The Inbox is a medium which contains items that change frequently. It is a temporary place that holds new information in the short term. It’s like a tail for our life as Merlin Mann said it 2024-10-23_08-21-merlin-mann. → 2.14.12

The Storage is a place which holds processed information on the long term, optimally organized in some form of fashion (2.8.2.4.5 The file system is a backend for our projects). Organization categories should have clean edges, so we know what to store where.

By using these two information holders, we can separate the processing and organization part of #GTD.

2023.10.30.

There similarities between naming things in programming and naming things in a Zettelkasten

  • When we have to name something we’re forced to think about its meaning.
  • Naming a #Zettelkasten note is similar to naming a class in programming.
    • In programming a class describes a set of related behaviors.
    • A name have to describe these behaviors in a way that makes sense for us (and other developers).
  • Phrasing a title for a note will force us to came up a simple clarification on the content of it. This requires understanding.
    • 2.6.11.5 A jegyzetcímekre API-ként kell gondolnunk

2023.10.29.

Thinking with a digital Zettelkasten

  • My idea of having a flexible thinking space means that I should be able to expand an idea everywhere in my #Zettelkasten.
  • Using iA Writer as the thinking space, I can automate new note creation using my “New Zettel” shortcut, which creates a new empty note and copies its wikilink to the clipboard.
  • After creating the new zettel, it displays the quick open bar in iA Writer, so I can choose to open the new note, or dismiss the search pane and paste the wikilink into the current one.
  • The workflow with this approach is that I can quickly create new notes, but keep them in the drafting phase, so I continue developing them later.
  • When a note is properly expanded, I can add it to the outline with the final zettel ID, and link to other notes.

Things is my Finder

I don’t browse my stuff by category or by area. I browse it by project.

Since I use #Hookmark to link related support material to my projects, I use the Things quick-find panel, to quickly jump to a project, then click on a link or invoke Hookmark to open a related asset.

Things is a taxonomy for my ideas

Since Things provides taxonomy for our life 2.10.4, by keeping ideas there, this taxonomy will be true for ideas instead of tasks. Things is my Finder 2.8.2.4.3.

Ideas need to be developed: the idea manager workflow 2.8.2.4 will make sure that I have a complete overview of all of my ideas organized into projects and areas.

Things to-dos can be a source of Reminders and Calendar based next actions

Follow-up on 2.8.2.4:

Next to Reminders, I also have to create Calendar events for Things to-dos. Having the next action creation automated, makes using Things as an idea manager easier.

When I run the New Next Action shortcut on the selected to-do, Shortcuts ask me if I want to create a new reminder or a new event. Events are created for the next day, then revealed in the Calendar, so I can continue to edit them.

Things can be used as an idea-manager

When I’m working with projects in a #GTD system, I need to have a way to plan projects. Previously I used external apps for this, but having a different view on my task manager app – combining it with Reminders for next steps – I can create an interesting use case for Things, where the app is used as an idea manager and not a task manager.

#Things allows me to create todos and attach long-formatted Markdown notes to them. In addition to that, having the date and checklist-related functionality let me add details on how a task should be performed.

In essence, a to-do for me in Things doesn’t mean a next action. It is closer to the analogy of Trello and cards.

The basic system is built on this foundation:

  • Each idea is represented as a todo.
  • An idea contains detailed planning.
  • The phases of the execution of an idea are tracked with tags, which can be Scoping, Ready, and Blocked.
  • Each idea belongs to a project (or area) and can be scheduled in the time constraints of Things (upcoming, anytime, someday).

An idea is something that is getting worked on as I get more information on the project. These todos are represented by a todo tagged with Scoping. If I have everything collected about the idea, then it gets the Ready tag. These todos no longer contain unknown details or questions, they are well-researched and ready for implementation.

When a todo is completed and needs review or it’s blocked, then it turns into a Blocked idea. I add a new item to the checklist about why it’s blocked, and I use notes to log the history of events. This is a remixed version of the “@Waiting for” list in #GTD integrated into the #Kanban like status tags.

I don’t work from Things though since I need to have concrete next actions stored somewhere. Since I don’t want to mix plans with next actions, I integrate Reminders with Things (2.8.2.4.1 Things to-dos can be a source of Reminders and Calendar based next actions). Using Shortcuts automation, I can create a linked reminder for any selected Things item, and move it to the appropriate context list in Reminders. Having this separation makes it possible to use Reminders to store bookmarks where I can quickly jump into plans stored in Things. Since Things no longer contains next actions, it can be treated as a #Zettelkasten like #PKM app which is about ideas working towards a clear goal (projects).

Git is an append-only information storage system

  • The workflow of appending new information can be used in the software #Development context.
  • Adding or removing code in a project will change its state, so when we store a snapshot in Git, we essentially keeping an append-only history of the codebase.
  • We shouldn’t worry about how changes are looking at one state, since code can be always formed. Actual state stored in Git will show changes, mistakes, refactorings, removals, which is the natural part of everyday work.

2023.10.28.

Csak úgy tudunk javítani a helyzetünkön ha elfogadjuk azt

Csak úgy tudunk javítani a helyzetünkön ha elfogadjuk azt. Ez az első lépése annak, hogy az irányításunk alá vegyük a dolgokat. Amikor ellenállunk, és/vagy nem vagyunk képesek elfogadni a dolgokat, akkor nem fogjuk megtalálni a kormányt.

A saját helyzetünk és végzetünk a közvetlen irányításunkon kívülre esik

  • A helyzetünk egy olyan állapot, amit nem tudunk közvetlenül irányítani, csupán hatással lehetünk rá.
  • A sztoicizmus két dolgot is említ egy helyzet irányításával kapcsolatban.
    • Egy helyzet a közvetlen irányítási körünkön kívül esik, viszont hatásunk lehet rá, amivel tudunk rajta változtatni.
    • Ha beleegyezzünk a végzetünkbe, akkor vezetni fog, ha nem, akkor korlátozni.
      • A végzetünk elfogadása segít bennünket előrevinni.

A vastagbélgyullasás állapotát befolyásolja az időjárás

  • Tapasztalataim alapján a vastagbélgyulladás állapota függ az időjárástól.
  • Az állapot javulása és romlása megfigyelhető egy ismétlődő hullámban: ahogy jön az ősz, úgy romlik az állapot, majd amikor beköszönt a tavasz és a meleg, az állapot újra jobb lesz.
    • Konkrétan a javulás és a romlás valahol 15-20 fok körül triggerelődik.
    • Felmerül a kérdés, hogy az állapotromlást az időjárás okozza közvetlenül vagy az időjárás által okozott testi/pszichés változás? Esetleg ez a változás kivédhető-e?
  • Az állapot romlása és javulása közötti fellángolás időszakot a gyógyszerek csak színten tartják, de nem javítják meg.
  • Tapasztalataim alapján a fenti állítás kb. 70%-ban igaz, mivel voltak olyan esetek, amikor nyáron volt begyulladva a bél.

Az állandó testellenőrzés és a fájdalomérzet kapcsolata

Az állandó testellenőrzés növeli a tényleges fájdalom szubjektív érzését azzal, hogy a figyelmünk lézerfókuszáltan egy érzésre összpontosul, ami bekapcsolja az agy harc vagy menekülés reakcióját. Az elme okozza a szenvedést önmagának. Ebben az állapotban egy megerősítő folyamat indul el, ami végül további gondolatokat szülve egy gondolat és félelemspirálba tereli az embert a fájdalom feltételezett növelésével. Ez azért van, mert meg akarunk szabadulni a fájdalomtól, pedig A fájdalommal szembeni ellenállás csak több feszültséget szül.

A fájdalommal szembeni ellenállás csak több feszültséget szül

A fájdalommal szembeni ellenállás csak több feszültséget szül. Amikor fájdalmat érzünk és megpróbáljuk azt eltolni magunktól – A fájdalommal szembeni ellenállás a múltban lévő állapottal való összehasonlításból származik –, akkor csak feszültséget generálunk, ami növeli a fájdalmat. Ezzel szemben, amikor elmerülünk benne, őszinte kiváncsisággal közelebb kerülünk hozzá, akkor az elménk nyugodtabbá válik. A fájdalom egy érzés, amire az elme teszi rá a szenvedést. Csak úgy tudunk javítani a helyzetünkön ha elfogadjuk azt.

Az anticipatorikus szorongás okozhatja az ellenállást a fájdalommal szemben

Az anticipatorikus szorongás okozhatja az elme ellenállását a fájdalommal szemben. A szorongásnak hatása van a dolgok kimenetelére. A fájdalomra az elme reakciójaként adott ellenállás oka az, hogy félünk a fájdalomtól, meg akarunk tőle szabadulni, mert az a múltban nem létezett. Ennek hatására az elme automatikusan sztorikat kreál a fájdalomról.

Az egészségnapló vezetésével jobban odafigyelünk az egészségünkre?

A naplózással könnyebben átlátjuk mi van irányításunk alatt és mi nem?

A naplózás segítséget adhat abban, hogy letisztázzuk, hogy mi van irányításunk alatt és mi nem.

Napi naplót vezetve tisztábban láthatjuk a különbségeket a múlt és a jelen között, így kirajzolódhatnak azok a korlátok, amik elválasztják az irányításunk és nem irányításunk alatt lévő dolgokat.

Amennyiben tisztában vagyunk ezekkel a határokkal, előnyünk van abban, hogy a jövőben tudjuk, hogy mely csatákat érdemes megvívni. A naplót backward tickler file-ként használva a múltból tisztábban reflektálhatunk a jövőre.

Napi naplót vezetve tisztábban láthatjuk a különbségeket a múlt és a jelen között

  • A naponta írt napló tisztább képet ad, közelebb hoz minket a múltban lévő állapothoz, mint egy sima emlék.
    • Az emlékeink fals képet adnak, mert csak a jóra tudunk emlékezni. Ez eltorzítja a múltat és felül értékeljük azokat a dolgokat, amik nem voltak olyan jók, mint ahogy emlékszünk rá.
    • Az emlékeinkben nem lehet bízni, de egy naponta vezetett naplóban igen. Ez a legjobb könyvjelző a jövőben arról, hogy mi történt az életünkkel a múltban.
  • A napi napló úgy tud működni, mint egy backward tickler file. A naplózás egy backward tickler file, ami a múltból hoz elő nekünk dolgokat. Ez az előhozott információ segítséget ad ahhoz, hogy a jövőben jobban meg tudjuk magunkat ismerni. Tisztán látjuk a különbséget a múltban leírt szöveg segítségével az akkori is jelen állapotunk között. Ez új perspektívát adhat abban, hogy hogyan kezelünk egy helyzetet, mennyire tartjuk azt fontosnak.
  • A naplózással lehetőségünk van arra, hogy összehasonlítsuk a jelen énünket a múltban lévő énünkkel és levonjuk a következtetéseket.
  • Hasonlóan ahhoz ahogy a GTD külső rendszerbe rendezi az gondolkodás végeredményét, úgy a napló is külső rendszerben állít tükröt két pont közé.

A fájdalommal szembeni ellenállás a múltban lévő állapottal való összehasonlításból származik

A fájdalommal szembeni ellenállás a múltban lévő állapottal való összehasonlításból származik. Az az állapot, amikor még nem volt fájdalom. Ez az összehasonlítás viszont nem valóságos, csak egy ötlet, Az elme automatikusan sztorikat kreál a fájdalomról.

A fájdalom elfogadásához nem jó hogyha összehasonlítjuk a múltat a jelennel?

A fájdalom elfogadásához nem jó hogyha összehasonlítjuk a múltat a jelennel?

  • A naplózás egy eszköz arra, hogy Napi naplót vezetve tisztábban láthatjuk a különbségeket a múlt és a jelen között.
  • Egy nehezebb helyzetben, amihez még nem volt szerencsénk, a napi naplóvezetés által adott különbség negatív érzelmeket szülhet, mert a helyzetünk rosszabb lett ahhoz képest, amikor még nem volt fájdalmunk.
    • A katasztrofizálás kezelése helyett van-e esély arra, hogy a naplózás elősegíti a spriálba kerülés esélyét azzal, hogy összehasonlítási alapot ad a múlt és a jelen között?
    • A múlt és a jelen összehasonlítása nosztalgikus élményeket szülhet, ami a fájdalom elfogadásában nem segít. Nyomorultabbul érezzük magunkat, ha látjuk, hogy a múltban mennyivel könnyebb helyzetben voltunk.