A hirtelen felindulást eredményező érzelmek, mint a düh, a félelem, a vágy és az élvezet elnyomják az agy azon részét, amivel józanon mérlegelni tudjuk a helyezetet. Ez olyan döntésekre ösztönözhet, amiket később megbánhatunk. Ilyen lehet például az impluzusvásárlás, szex közben a hevesen felhúzott gumi vagy vita közben mások szidalmazása. Ezeket úgy tudjuk elkerülni, hogyha megpróbálunk figyelni az adott érzelem kialakulására, vágyak esetében buffert hagyni magunknak a döntésekre vagy büdzsé tervet készítünk.

• A véleményformáló blogok hatása a vásárlásainkra
• A tanulás nehezebb, mint a tagadás

• Vannak olyan esetek, amikor az emberek a tagadást választják a megismerés helyett.
  • A tagadás kényelmesebb, mert a tanulásba munkát kell fektetni ahhoz, hogy megváltozzanak dolgok.
• A tanulással könnyen előfordulhat, hogy végül rájövünk arra, hogy nem volt igazunk. Ez lyukat üt az egónkban, így érett személyiség kell ahhoz, hogy bevállaljuk ezt és elismerjük a hibáinkat.
  • A tagadással ezt el tudjuk kerülni, viszont így könnyen lehet, hogy csak hazudni fogunk magunknak.
  • A tudás az elme és az azt támogató külső eszközök eredménye

A hirtelen felindulásból történő vásárlások elkerülésére a büdzsé egy jó eszköz lehet. A büdzsé egy terv arra, hogy egy véges készlet felhasználása hogyan történjen. Amennyiben igazodunk ehhez a tervhez, elkerülhetjük, hogy a hirtelen felindulásból vásároljunk valamit. Opcióként a tervbe foglalhatunk egy megadott összeget magunknak ilyen vásárlásokra.

A véleményformáló termékblogok képesek olyan vásárlási döntésekbe vinni az embereket, amiket csupán a közösséghez tartozás és a FOMO miatt tesznek meg. Ezek a blogok (például az olyan márkák köré tematizálva, mint az Apple) kisebb közösségeket formálnak ki maguk körül. Ezek az emberek diktált termékpreferenciákat követnek, amiket a blogger vezérel. Ezek a termékpreferenciák többször is kommunikálva vannak és mint egy reklám bújik bele az agyunkba, ösztönözve minket a vásárlásra. Sokszor mondvacsinált problémákra próbálunk megoldást keresni ezekkel az eszközökkel, mindössze amiatt, mert a FOMO érzése arra ösztönöz minek, hogy kövessük a tömeget.

Az állandó aggodalom kitalált veszélyeket hordoz magában, ami miatt jelentkezhet a testünk védelmi mechanizmusa stressz formájában. Ennek káros hatásait elkerülve nem stressz menedzsmenttel kell foglalkoznunk – mivel a stressz automatikus reakció – hanem aggodalom menedzsmenttel.

• A GTD segít irányítás alá vonni a zavar utáni zajt

A szorongás típusa befolyásolhatja a szorongásunk tárgyának bekövetkeztét aszerint, hogy félünk attól, vagy nagyon vágyunk rá.

Anticipatorikus szorongásnak hívjuk azt, amikor annyira félünk valamitől, hogy az erre adott reakciónk valószínűbbé teszi a félelmünk bekövetkeztét. Ilyen lehet például az egészségszorongás során a testpásztázás és nyomkodás reakciója, ami csak rosszabbá teheti a vélt tüneteinket, vagy az eleme fájdalommal szembeni ellenállása.

Ezzel ellentétben hipertenciós szorongásnak nevezik azt, amikor túlságosan vágyunk valamire és az emiatt nem következik be. Erre példa lehet a szexualitásban túlságosan vágyott orgazmus. Ilyenkor figyelmünk annyira erre összpontosul, hogy reakcióként a testünk nem tudja magát elengedni, így végül az orgazmus emiatt nem következik be.

• Az agyunk jelzései a tisztázatlan dolgokkal kapcsolatban

Follow-up on 2023-10-23_22-27:

• By appending information, we don’t delete existing information, we just add new information at the end of the stack.
• Having all changes visible in the chain (even the bad ones), makes harder to erase mistakes.
• Analog systems like Antinet #Zettelkasten or #Journaling are forcing us to organize information by appending it at the end of the stack.
• Digital systems can be used like this, but they need the right mindset from us, so we don’t remove mistakes.
  • Keeping mistakes can be beneficial 2023-11-18_21-47
• Appending information gives us a way to see the development of an idea.
  • Keeping a history of changes called versioning in computer software.
  • A Zettelkasten és a GTD hagyja természetesen kialakulni a dolgokat 2.6.5.4
  • Zettelkasten jegyzetsorozatok 2.6.9
    • A Zettelkasten outline megmutatja egy ötlet kialakulásának történetét 2.6.9.6.1
  • A tweetstorm alkalmas egy ötlet publikus tesztelésére 2.6.12.1
  • We can email ourselves in a thread to capture an idea 2.14.10
  • The capture log is an automatic journal 2.14.12

• I like how Aaron Draplin duplicates layers in Illustrator to keep a history of changes and branch out new ideas.
• In the same way I can duplicate groups in Ulysses for writing projects, so I can have a trackable / branchable writing workflow.
  • Ulysses also keeps versions of projects, but the manual version can be tied to milestones in the writing workflow.
• The version workflow can be this.
  • Keep a group where all sections are sheets.
  • Duplicate groups before big edits and assign version numbers for each group.
    • XYZ v1
    • XYZ v2
  • Triggers for duplicating groups can be the following:
    • First draft is ready.
    • Starring a new editing session.
      • Before each session, create a new group.
      • This removes the fears of loosing ideas. I can just go back and copy a previous idea.
    • Checking grammar with Grammarly.
      • Grammar checking is just another form of editing.
    • Before publishing the first version.
      • I can keep a version which was the initial finalized idea. The published version can change, so this group will allow me to compare what type of changes I usually do.

See more at “Az a munkám, hogy gondolkodok”. 1.1

Email replies need to be kept on the same “Waiting for” list just like tracking any other item I’m waiting on. Keeping just one list for “waiting fors” will make reviewing these actions way easier in my #GTD system.

It’s important to BCC myself in an outgoing email, because that’s how I can get a reminder about that I’m waiting for a reply to my email. I can use my email address, but it’s even better if my list manager can receive emails and save them into my Inbox directly (like Things or OmniFocus allows me). Later I can process captures emails and create a “Waiting for” actions out of them.

I usually name my waiting for actions in the following format:

“Person / organization name → subject of what I’m waiting for (optional date in YYYY-mm-dd)”

Journaling about a topic can help us to clarify next actions about it. This habit is one way of using writing for thinking.

The “River of thoughts” concept means that you are writing down everything that comes to your mind and then later you organize it. The goal is to get down every idea, and then see what happens.

Hopefully at the end, you’ll end up with at least one next action that you can store in your GTD system.

We have the Remind Me and Follow-up features in Mail, which could be useful for email follow-ups, but there are problems with them.

1. Remind Me only works for emails in the inbox, so if I archive an email, it just silently moves the email to the top of the Archive.
2. Follow-up is a black box, driven by AI, and there is no way to set it up manually for specific emails that I want to track.
   • It is 3 days by default, but I’m not sure if it works for every email sent.
   • I also use a GTD waiting for list to track items waiting for reply. → 2.7.8

Instead, I can leverage the fact that Mail has excellent conversations view, so the Send Later feature can resurface any thread by just scheduling a message which is forwarded to myself.

I have a separate “Inbox” contact card with the +captured text appended to the email address, so when I want to remind myself about a message, I can just forward it to this address with Schedule Later feature.

It will reappear in my inbox resurfacing the whole conversation. I can also add my own notes to a forwarded message in a thread which acts a bit like the poor men’s version of HEY’s sticky notes.

• The iPad Pro could be improved regarding problems of UI delays and slowness.
• I don’t use Stage Manager in the internal display.
  • The best iPad setup is to have Stage Manager disabled in the internal display and use it on an external display.
  • Disadvantages of using Stage Manager is that…
    • I feel like the Magic Trackpad connected using a USB cable is actually lagging compared to the internal trackpad.
    • iPadOS can’t turn off the external display. It’s just switches to a black screen, so in theory the display still consumes the same amount power as in use.
• It should be the perfect blogging machine.
  • It doesn’t have MarsEdit, which is one of my most useful apps on the Mac to edit posts on a blog.
    • I can start a link post from Reeder or Safari and share it with people.
  • There is a native WordPress app on iPadOS, which lets me manage my posts, but I still like MarsEdit more, because it uses HTML directly.
    • I can switch to HTML in the WordPress app, but I need to do it manually every time.
• Keyboard shortcuts on the iPad Pro are lagging compared to macOS.
  • Using MacOS from the keyboard feels intuitive and fast, because it has years of experience being an OS controlled via keyboard and mouse.
  • Some iPad apps are have great keyboard integration, like Safari, Things, Craft and iVim. In other apps (like Mail) the keyboard feels like some form of remote device.
• The iPad Pro’s screen is too small to do heavy work.
  • There is a limit of what a mobile device can do on its 11-inch screen.
  • The iPad Pro has bigger UI targets than macOS, so it fits smaller amount of content on its display.
    • We can set the iPad Pro UI scaling smaller, but then it is too small compared to a standard MacBook screen.
      • Setting the iPad Pro UI scaling smaller, we end up with a UI scaling that is similar to iPad mini and iPhone.

• The iPad Pro can be a computer which I use as a small laptop
  • There are usability issues present when using the iPad Pro as a small laptop 2.8.6.3
  • I can say that the benefits of having an iPad Pro with the Magic Keyboard is to use it as a mobile device for tasks that need a lot of typing.
• Such typing heavy tasks include
  • Blogging
    • Assembling a draft of a post in Craft, exporting it into Ulysses, then publishing it via the WordPress app.
  • #Zettelkasten writing, where I have my @Staging list which holds all my notes that I’m working on.
  • Replying to emails, not processing them.
    • We can email ourselves in a thread to capture an idea 2.14.10
  • Using it as the secondary display for my MacBook Pro when doing work away from my desk.

• I can leave notes for myself about an email thread by sending a reply to my own address in the same thread.
  • Send Later in Mail can be used as a Tickler File 2.14.9.2
• I’ll see the email as part of the thread, but it will be kept private.
  • I can use it to forward ideas to my Things inbox, but still keep notes in the thread.
• It can be a nice tool for keeping notes in the email thread about…
  • Code review comments.
  • Ideas about a project we’re discussing.
  • Capture an idea on the phone about a thread which can be seen later on the desktop when I’m processing emails.
    • It is a good idea to turn on threads in Apple Mail to see these notes in context.

• The idea of the workflow changelog is to collect workflows that we want to apply when we’re using a tool.
  • We can keep these workflows in a Zettelkasten-like note-taking system.
  • Write about how we plan to use a workflow.
  • As we learn to apply these workflows, we can evolve them like ideas, and connect them with other workflows.
• When we’re ready to use a newly found workflow, we can create a list of workflows that we want to learn.
  • When we see the opportunity to use a new workflow while we work, we can refer to our workflow list on how to do it.
  • The workflow learning list should contain about 3-5 workflows at the one time. Otherwise we won’t remember to use them.
• Over time, some of these workflows will became muscle memory. The rest will be ignored.
• Workflows that have been learned, can be checked on the list. If we want, we can add a new workflow to our list.
• Our own automations can be also tracked on this list.

• I like to keep my #DigitalGarden private.
• Instead of developing ideas in the public, my #DigitalGarden should be used as a private backbone for my blog.
  • I keep #DigitalGarden notes here about the things I’m interested in.
    • Scripts
    • Systems
    • Workflows
• I can develop ideas here, and when they ready, I can release them on my blog.

• Míg a projektek esetében a sorszám felfogható egy egyedi azonosítóként, aminek vannak előnyei (például Safari Tab Group elnevezése, keresés), addig a jegyzetek esetén sokkal fontosabb hogy a jegyzet címe egy állítás legyen és az szövegkörnyezetben is jól olvasható (202109082109 A jegyzetcímekre API-ként kell gondolnunk).
  • A sorszám nem kommunikál jelentést egy digitális Zettelkasten jegyzet esetében.
  • There similarities between naming things in programming and naming things in a Zettelkasten 2.6.11.6
• A sorszám olyan mintha egy örökség lenne az analóg Zettelkastenből, amiben még a technológia hiánya miatt szükség van egy egyedi azonosítóra.

• Az alábbi dolgokat érdemes benne tárolni:
  • egy meetinghez kapcsolódó meghívókat, support és agenda elemeket
  • meeting jegyzeteket, amiket majd capture-ként használunk egy adott eseményhez
    • így vissza tudunk menni a naptárban és visszakövetni a meetinghez kapcsolódó jegyzeteket
    • érdemes lehet automatizálni a meeting jegyzetek létrehozását valamilyen szűrés szerint
      • a “Sync Calendar to Deep Sessions” shortcut jól alapul szolgálhat ezen jegyzetek létrehozására
  • érdekes / hasznos információ az adott naphoz kapcsolódóan
  • dolgok, amik adott napon aktiválódnak, vagy szükségünk van rájuk

• A DEVONthinkből a Tickler File koncepciót használva össze lehet szinkronizálni annak tartalmát az Apple Calendarral.
• A GTD rendszer azt mondja, hogy minden nap először a naptárunkat kell megnézni.
• A naptárra szinkronizált Tickler Fileban tárolhatunk olyan support elemeket amikre:
  • aznap szükségünk lehet,
  • meg kell néznünk,
  • vagy fel kell dolgoznunk.

• A paper is a final output from a scientist which is reviewed by other people. His findings can provide insights into a topic which can extend the human’s knowledge.
• A pull request is also a final output of a developer’s code work which is reviewed by a peer developer. When a PR is merged, it can extend the application’s functionality.
• Usually pull requests reviews are not as strict as scientific paper reviews.
• There is a correlation between the number of pull requests and developer productivity, but it is not a one-to-one mapping.
  • Pull requests can be hard to implement, so some of them take more time than others.
    • 202109082041 Gyorsabb munkával kevesebbet halogatunk
  • The same is true for science papers: some research is harder to do than others.

• It should always be with me. I could even always carry it around like a small a MacBook. For example Stephen Wolfram always has a computer with him.

But I never like to be computerless, and the 13′′ laptop is a heavy thing to lug around. So instead I also have a tiny 2-lb laptop, which I put in a little bag.

• He uses a 12-inch MacBook to lug around.
• A MacBook could be better choice for this instead of an iPad, but I already bought have an M2 iPad Pro which should be able to serve me as a portable laptop instead of an M2 MacBook Air.

• Stephen Wolfram has usecases for different mobile devices in different context.

  I always have my phone in my pocket, and if I have just a few moments that’s what I’ll pull out. It works fine if I’m checking mail, and deleting or forwarding a few messages. If I actually want to write anything serious, though, out will come my little computer, with its full keyboard. Of course, if I’m standing up it’s pretty impractical to try to balance the computer on one hand and type with the other. And sometimes if I know I’m going to be standing for a while, I’ll bring a tablet with me. But other times, I’ll just be stuck with my phone.

• He uses his phone for most of everyday task, but when he have to do serious typing, then he grabs his MacBook and uses that.
• Typing with a tablet is only feasible for him, when he stands, so if he is going to stand a lot, he brings a laptop.

• We can store next actions of a GTD system in Apple Numbers by creating two tables for next actions and projects.
  • The projects list is just a plain list of projects, with a completion checkbox, a title, and an optional due date field.
    • We could add an optional notes or project support field as well, where we can link notes and other assets, or just link them using the title field.
      • It would be nice if we could link to Hook itself, where the link would open the a bunch of assets in the Hook window.
  • The next actions list contains a completion checkbox, a title, a due date, a context, and an optional project field.
    • The context field can be a drop-down listing all of our contexts.
    • The project field can be a linked field using a formula for the projects table title field.
• Category grouping on the next actions table can be used to group next actions by context.
  • Contexts groupings can be folded, depending on where we are and what we want to see.
  • We can create sums for the number of nexf actions in a group.
• Writing AppleScript for syncing with Reminders should be easy.
  • The script can create different Reminders lists for each context.
  • Due date can be assigned as Reminders due date.
  • Next actions can be added to each Reminders list using the following format.
    • Next action title [Project Title]
  • Questions
    • Could it be possible to sync changes from Reminders back to Numbers using AppleScript?
• Questions
  • What pivot tables are?
  • Can we use pivot tables to create multiple views (perspectives) for the next actions table?
  • How would we store task related notes?
    • A new field can be long, but we can’t have fields under another row.
  • What would be the benefit of this system other than just using a proper task management app like OmniFocus?
    • I guess it’s free and comes with every Mac.