@socoloffalex — Cal Sans, open-source font by cal.com
Open Source Font of the Day
Cal Sans by @calcom - Link in comments
Nearly 1,000 people bookmarked this. Cal Sans is the geometric sans-serif that cal.com uses across their product — clean, slightly rounded, immediately recognizable. It's free, it's on GitHub, and it's one of those fonts that looks better than most commercial options you'd pay for. If you're building something and need a headline font that doesn't scream "I downloaded this from Google Fonts," worth a look.
@peduarte — VSCode should handle this by default
Crazy you need a VSCode extension for this instead of being default
Pedro didn't name the extension in the tweet, but from context and the screenshot it's about file nesting — collapsing related files (index.ts, index.test.ts, index.module.css) under a single parent in the explorer. It's a pattern that's been standard in JetBrains IDEs forever. The fact that you need a third-party extension for something this fundamental in 2024 says something about VSCode's philosophy: ship the minimum, let the ecosystem fill the gaps. Works great until the ecosystem fills it inconsistently and you spend 20 minutes comparing file-nesting-updater vs native config.
@steventey — preventing accidental domain misconfiguration in dub.co
We just made a small but significant UX improvement to @dubdotco's project creation flow:
In the past, when users add their custom domains to Dub, they sometimes end up adding their main website domain by accident.
Solution: A @shadcn radio group check confirmation check 😁
Smart, because the bug isn't a code bug — it's a user expectation mismatch. People expect to add their company.com when they mean go.company.com. A radio group confirmation step adds just enough friction to surface the question "wait, is this right?" without being a hard blocker. Low implementation cost, catches a mistake that's annoying to undo. The shadcn RadioGroup handles the UI cleanly here — this is the kind of thing a good component library makes trivially easy to reach for.
@jameesy — minimal writing workflow in Obsidian
My minimal writing workflow in @obsdmd.
It uses the Kanban plugin to bring some order to the files in my Output folder.
Every month I move all of the files to archive so the board doesn't get cluttered.
The more of my workflow I can handle in Obsidian, the better.
Honestly just saved this as a reference point. I keep coming back to the question of whether to manage writing state (draft / in-review / published) in the file system, in frontmatter, or in a separate tool. Using the Kanban plugin to visualize that state inside Obsidian is a clean answer — no external tool, no sync issues, everything in one vault. The monthly archive flush is the kind of maintenance habit that keeps a system usable long-term instead of slowly drowning in stale cards.