Unemployed. Building whatever I feel like.
Daejeon 🇰🇷
Joined February 2026
- Tweets468
- Following579
- Followers374
- Likes2.4K
Woonggi Min retweeted
여러분, 안녕하세요! 🇰🇷
We are days away from our first trip to Seoul!
Come meet us and @friendliai on Nov 5th.
We would love to see you there!
Register below ⬇️
luma.com/ollama-friendliai-m…
Read about building agents from an inference perspective.
A faster model doesn't always mean a faster coding agent.
AI coding performance depends on 4 layers:
🤖 Agents
🧠 Models
⚡ Inference
🖥️ GPUs
The real goal? Better task success, faster completion, and lower cost per task.
Explore the full stack 👇
friendli.ai/blog/ai-coding-a…
New idea: 3D-printing the palm rest as an integrated part of the keyboard’s top housing.
This way, the palm rest would be held in place by the weight of the keyboard itself. Let’s see if it’s feasible.
The hardest part of designing a wrist rest? Making it stay in one piece when I picked it up.
Several tolerance tweaks later, these two finally get along.
My honeycomb wrist rest for the Rule 60 V3. No screws, no magnets, just printed parts.
Free files:
makerworld.com/en/models/349…
There seems to be a problem with the website or somewhere on Linux (or Chromium)
At first, I thought it was a design
If you're using agents to code (why wouldn't you at this point in time?), as a creative developer, I recommend you to start exploring Rust, WASM and WGSL more. I've updated my previous portfolio to lisergia.dev and the entire ergonomics is incredible.
Omarchy tip
Pressing `Win + `` drops the default coding harness right over whatever you’re currently working on.
Pretty handy for quickly dumping random thoughts that just pop into your head.
Seoul just had a Grok Bot meetup. Would love to run one in Daejeon too.
KAIST city, so good spot for a casual build + share session (I’ve hosted several meetups before).
@benln interested?
The hardest part of designing a wrist rest? Making it stay in one piece when I picked it up.
Several tolerance tweaks later, these two finally get along.
My honeycomb wrist rest for the Rule 60 V3. No screws, no magnets, just printed parts.
Free files:
makerworld.com/en/models/349…
Picked up a @BambulabGlobal X2D AMS Combo for 16% off during Korea’s Black Friday sale.
Now, what should I print first?
Woonggi Min retweeted
gpu-unlock has been trending lately. Happened to have two RTX 3090s on hand, and since there weren't many real-world LLM benchmarks out there, I ran a 100K context test myself.
See comment for more details.
notion is dead
acard.dev/
Stop using Notion and Obsidian.
Let AI do the organizing.
Just talk to your AI. The conversation becomes your notes, your docs, your record.
Acard - local, open source
I'll make, $5 gets you the web app and everything else.
Woonggi Min retweeted
acard.dev/
Stop using Notion and Obsidian.
Let AI do the organizing.
Just talk to your AI. The conversation becomes your notes, your docs, your record.
Acard - local, open source
I'll make, $5 gets you the web app and everything else.
Woonggi Min retweeted
Dynamic sparse attention reads fewer tokens per query. So why doesn’t the KV cache necessarily shrink to match?
Sliding-window attention only looks at recent tokens. Once a token falls outside the window, that layer no longer needs its KV state to continue the sequence, so the runtime can release it.
Dynamic sparse attention works differently. Each query selects which tokens to attend to from across the history. A token skipped by this query may be exactly what the next one needs.
So the runtime may still need to keep the full KV history, even though each step reads only a subset. And selecting positions and gathering noncontiguous KV entries adds its own cost.
Fewer attention reads ≠ a smaller cache. For long-context agents, compute and memory are two different budgets.
Our deep dive covers what this, and hybrid models like Kimi K3, mean for prefix reuse, caching, and speculative decoding: friendli.ai/blog/llm-archite…
prime time to switch to @AsideAI
We've decided to sunset Arc on December 22, 2026.
That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community.
Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward.
We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how:
· Your passwords, bookmarks, extensions and history come over to Dia seamlessly.
· Spaces, Folders, and Tab Groups are in Dia and import over with your data intact.
· Dia now surpasses Arc benchmarks in stability, speed, and security.
· The browser features you use in Arc are free in Dia, and the AI is optional.
Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.