A hill I’m willing to die on: the IDE is not the future of building software. I basically live in one now, so this isn’t IDE hate. I just think we’re mistaking where AI coding started for where it’s going. As agents get better at writing code, what do you think the actual interface for building software becomes? I have way too many thoughts about this, so naturally I wrote a way too long article about it. crisdobbins.substack.com/p/t…

Product and UX designers: how much of your existing design process are you bringing directly into your AI workflows? I've started giving agents the same artifacts I've used with teams for years: user journeys, system diagrams, wireframes, states, edge cases, jobs to be done. They're incredibly effective AI context. In some cases, a visual journey has communicated the system better than pages of prompting. It made me realize how closely design first principles map to good AI planning and prompting. What design practices have you found translate surprisingly well to working with AI?

I genuinely don't know what my job is anymore. I've been a product designer for 20 years, but now I'm writing code, building agents, designing systems, working on infrastructure, and still doing all the things I'd consider design. None of these titles quite fit anymore. Designers working this way: what are you calling yourself? And what parts of your job have you moved into that you never would have considered “design” a few years ago?

Hottest thing coming out of @soffi_dev right now is before and after images of UI changes on every PR. @donkeyscience from our team has been building Soffi Vision for visual diffs of UI changes that can be viewed in the Soffi UI next to code changes, as well as commented on PRs with summaries of what changed.