Radar

Links, articles, and things I find interesting around the web.

Why I built this →
Also found this post on hackernews: https://news.ycombinator.com/item?id=47281593
"As somebody who used em-dashes a lot pre-ChatGPT, I have genuinely struggled with feeling I should change my writing style to appear more human. I would be happy with a double dash--but many programs autocorrect that to a full em-dash. So I'm left anxious that people will think I find them so unimportant I have offloaded communication with them to an LLM. So this post resonated with me"

This is so true! I still use em-dashes heavily in my natural writing, time to revisit that.
this css proves me human I don't think I can build a fence with these posts... will-keleher.com
This is the future I'd like to see..
Moving Product Planning to a Git Repo: Simplifying Workflow | Carl Edwards posted on the topic | LinkedIn I moved our product planning into a git repo. Not Jira. Not Notion. Not Google Docs. Markdown. Version controlled. Here’s what last week looked like: Pulled data from Jira, Amplitude, Slack, support. Drafted the cycle proposal. Had a planning call with our CEO. Fed the transcript to Claude Code. Minutes later: updated proposal. Priorities adjusted. Rationale captured. I reviewed the diff, made a few tweaks, merged it. Every decision now has a commit. Every shift has a diff. The whole team can see exactly what changed — and why. On a small team, leverage matters. Planning shouldn’t live across five tools. It should compound like code. I wrote up the full pattern — how we structured the repo, how AI fits in, and why this is working better than traditional PM workflows. Full post here: https://lnkd.in/gUiNEMha | 32 comments on LinkedIn linkedin.com