What we actually open every day.

Where the automations live. Visual workflows, so you can see the whole path from trigger to result, and it will happily talk to almost anything with an API.

Right answer when a process runs on a schedule or off an event and more than one system is involved. Wrong answer for a one off, which is faster to just do by hand.

How this site was built and deployed. It works in the actual files on the machine rather than in a chat window, which is the difference between getting a snippet and getting a working thing.

Also where we keep skills, saved instructions that make it do a job the same way every time instead of re-explaining it.

An editor with AI built into it. Where we go to see and shape the code directly rather than describe what we want.

Worth learning even if you do not consider yourself a developer. Reading code you did not write is a skill that pays back immediately.

The second brain. Plain text files on your own disk, which matters more than any feature, because it means nothing you write is trapped in someone else's product.

It only starts working when adding things is made harder. Collecting is not thinking, and a vault full of clipped articles is just a nicer looking browser history.