Today I Learned

I'm addicted to the choo-choo sound. I’m using Conductor heavily right now and gents now make this sound when they're done. I love that detail more than I should.

The bigger realization, though: context switching might be the hardest challenge we’re facing over the next year. Things move way, way faster now. Agents don't wait. You finish one thing, another is already done, and suddenly you're jumping between five different threads before breakfast. It's a lot.

And yet, I feel genuinely productive. More than I have in a while. I'm not sure those two things should go together, but right now, they do.

I've been nerd-sniped by personal knowledge management for a long time. Probably tried dozens of approaches in the last 10 years, and not a single one really stuck — the maintenance burden always killed it.

Then I stumbled across this concept by Karpathy. The core idea: you never write the wiki yourself. You drop sources in, the LLM reads them, extracts what matters, and integrates everything into a persistent, interlinked set of markdown files — updating pages, flagging contradictions, maintaining cross-references. You're just the reader.

That role reversal is what makes this feel approachable to me. Every PKM system I've tried eventually collapsed under the weight of keeping it current. This one offloads exactly that part. The LLM doesn't get bored, doesn't forget to update a cross-reference, and can touch 15 files in one pass.

I'm really excited to give this a shot and share my learnings here.

Yesterday at Config 2026, there was this tiny little announcement at the end of Skills for the Figma on Canvas agent. I think this is a huge thing since it opens up so many use cases that I know from other workflows. Imagine skills for a visual design critique, a preparation of the design rationale in slides, challenging questions, a hand-off checker that challenges the design from an engineering side of things. I'm really excited to try this out and build some superpowers for the agent!

Ideate → Brainstorm → Plan → Work → Review → Polish → Compound.

This is the workflow of the Compound Engineering Plugin from Every. I set up a small playground for it yesterday, and it has significantly boosted my productivity. I am ideating on things to build, brainstorming possible solutions, bringing them to the canvas, tweaking them, and planning the implementation. It not only feels productive; it truly is. However, the best part for me is the most mundane: the documentation.

I came across this video from Ridd. It showcases his current workflow for designing (or rather building) products using tools like Conductor, Paper, Claude Code, and others. You can clearly see a shift, with much more production work occurring in code rather than on the canvas. I'm currently trying out this type of workflow, and with my engineering background, it feels much more natural to me. I'm very happy that we have tools that support these processes.

Podcasts are one of my favorite types of media. Currently, I’m learning a lot about LLM architectures, model training, and the technology behind them. With NotebookLM, I can easily compile all my sources and generate targeted podcasts to listen to during my commute or while taking a stroll. It feels like I have superpowers nowadays.

I recently worked on a Figma plugin during an internal hackathon. Our goal was to optimize the hand-off process and incorporate AI into the workflow. However, we found it challenging to make a design "understandable" for AI due to the implicit knowledge embedded in it. We discovered that combining different layers was crucial. We serialized Figma layers, added screenshots, and provided some manual context. This approach significantly improved our understanding of gaps in the hand-off process and allowed us to deliver higher quality results

I just stumbled upon some open lectures from Stanford. It’s so crazy good that education like this is publicly available nowadays. One of them was about LLM training and the technology behind it. Transformers are the thing powering basically every modern AI model. You give them text, they break it into chunks, and then figure out how every word relates to every other word all at once. That context-awareness is the whole trick. It's why the model "gets" what you mean, not just what you typed. Stack enough of those layers on top of each other, train on enough text, and you get something that can predict the next word surprisingly well. That's it. That's the magic. At least to some degree.

I just stumbled on Codepen 2.0, which is currently in beta and it's finally a very modern way to build short little prototypes. I just love this way of working and I already picked it up around university time to build front-end focused experiences or little component snippets and make them easily shareable. Still looking for a good way how to combine that with an agentic workflow, but for now Codepen 2.0 feels pretty epic.

I started playing tennis last year in September. I'm playing somewhat regularly right now and had my first ranked match yesterday. I lost it very closely in the champions tiebreak. I'm quite happy with my performance, but when you watch Roland Garros in the evening, this felt like a completely different sport. I love tennis, but I also learned that it takes a long time and a lot of discipline just to be somewhat average. Keep on grinding!

During my vacation in Japan this month, I learned how deeply the Edo (1603–1867) and Meiji (1868–1912) eras still define the nation. This contrast really becomes incredibly present as you travel through different regions. Moving from the preserved samurai districts and quiet temples of Kyoto or Kanazawa (the isolated, traditional Edo era) to the westernized red-brick architecture and bustling port vibes of Yokohama or Kobe (the rapid modernization of the Meiji era) shows how beautifully Japan blends its secluded past with its industrial leap forward.

I cannot write prompts when I’m tired; the output is poor. For my side projects, I have found a different workflow that better suits my needs. I plan throughout the week, refine the plan from Monday to Friday, and then implement it with intent. This approach provides me with greater clarity and, more importantly, time to consider whether the project is truly worth building. Much of this thinking time does not occur at my desk!

I just stumbled over the fact that Command + Shift + 1 is actually a Macintosh shortcut to eject floppy disks. Well, I guess in 2026, nobody's using floppy disks anymore. That's why it's pretty safe to reassign that shortcut. I set it to capture text on my screen with CleanShot because this is one of my most favorite use cases. And hell yeah, this workflow feels good.

I love the convenience of applications like Conductor and the user interface on top of agent orchestration. However, I've recently found myself returning to the files, tweaking CSS, and adjusting pixels with small increments through many iterations. This workflow often disrupts my context in agent windows. I appreciate the new agent window from Cursor, and the transition to the editor window has become a workflow I truly enjoy. I start and plan with the agent, then iterate in the editor. It's the best of both worlds.

Copernicus is a space program from ESA and is focused on Earth explorations. The cool thing is that there is a newsletter that shares an image from Copernicus with you every day and it always has a nice connection to current happenings in the world. And it's a really nice newsletter that I love to enjoy every morning. Copernicus image of the day

I recently heard somebody sharing a very interesting prompt: Let's step back and think really hard: how can we make this simpler and dumber while still achieving our goals? This is such a good addition to my workflow and I'm using it 20 times a day.

In one of the recent "How I AI" podcasts, I came across a slide that intrigued me and sparked my thoughts. Now, I constantly wonder if this is truly worth my attention and whether I will improve tenfold if it genuinely delivers ten times the impact.

I always thought, based on the name, that it was a Japanese creation. However, it was actually developed by an American architect in 1979 and called "Number Place." Japan simply rebranded it and made it popular. Playing it regular recently and it’s such a fun little thing to do!

Figma keeps track of the last typography style you interacted with, which might seem simple but is quite useful. This means that by clicking on an existing text field that uses the desired style, I can speed up my workflow significantly. I just hit T and start writing, rather than writing first and then switching the style afterward. Little things like this add up.

I’m a sucker for keyboard shortcuts. One of my favorite new ones is the hyper key (✦), which basically combines ⌃⌥⌘⇧. Yep, that’s impossible to press. I combined it with Raycast, mapped it to my Caps Lock key, and assigned it to a bunch of commands to open apps. ✦F = Figma, ✦S = Slack, etc. Timesaver and endless possibilities!

I just stumbled over life-os by Gabriel Vadivia. It’s a super interesting, markdown based knowledge base, journal and diary and looks very interesting to me. I struggled a lot with creating something like this because I really overthought the folder structure. Just letting Claude run and maintain that in the background sounds so good.

I'm currently building this TIL section within Notion because it's just the easiest and most convenient for me. But every new entry requires a redeploy. I now set up a custom script with a redeploy hook on Vercel so I can redeploy my website just with a Raycast command. Big time saver.

I’ve been quite enthusiastic about keyboard shortcuts lately. I looked for a way to reactivate the mini player in the Dia browser while watching a video with another tab active. It turns out that pressing "I" on your keyboard in YouTube activates their mini player. This also resolved my Dia issue!

I stumbled upon the Chrome DevTools MCP and set it up with Claude Code. It's especially useful for making small updates or running experiments on an existing page. This feels great. Currently, my biggest challenge is making quick iterations on existing pages with AI when I don't have direct access to the code. This remains a significant issue in large companies, where there's a clear separation between designers and developers, or in unconventional agency setups. Overall, this is a pretty cool solution. Now I just have to make it persistent somehow.