Daniel Solberg

Your commute is an underrated part of your job hunt. A few friends recently mentioned to me how frustrating it is to try finding roles near public transit. You find a promising listing, then have to manually look up where the office actually is. Repeat for every role. And I realized that popular job boards like LinkedIn, Indeed, and Wellfound don't have a "map view" that lets you browse listings by proximity to Caltrain or BART stations. It genuinely surprised me that this doesn't exist. So I've been using Claude Code to vibe-code exactly that: Search a role and quickly see which openings are close to a given station (and which aren't worth the commute). Still early, but here's where it's at: - Adzuna for job listings (scraping LinkedIn is legally dicey, lol) - Leaflet for the open-source interactive map - Nominatim for geocoding company office locations Nominatim struggles with lesser-known companies, so I'm swapping it out for the Google Places API next to see if that improves accuracy in the mapping pins. The UI is all Claude Code-generated for now. Planning to try the Code-to-Canvas Figma MCP connection soon to see if I can make the UI more polished from there.

@m_atoms @round That's awesome! Thanks for sharing. I'll definitely be looking into it for my project.

@without_daniel @round Claude rips with MapLibre so my experience has been great

Introducing Republic - the best way to monitor the situation in your city. Track political news, crime, permits, events, community groups, and more across the city and in your neighborhood!

@CamiloVlies @X Happy to connect, Camilo 👋🏻

Hello, @X Could you connect me to a few great Founding Product Designers? 🎨 Also open to folks who are into 0→1 product, design systems, prototyping, UX writing, motion/interaction, brand-to-product, and AI-native design workflows. I’m building in public, learning every day, and I’d love to meet designers who like to move fast, ship often, and think like builders.

Agreed. This is the same sentiment I've been bringing to conversations at my company. We may still introduce a chat interface at some point as a means to describe what you care about and want to see out of the system, but I'm confident that we can provide value without needing to do that through understanding what our users care about most and designing/surfacing accordingly.

my take is most b2b saas users don’t want a chat interface as their entry point. they don’t want to ask for things, they want to see them the real job as the builder is curation and deciding what data and tools show up first not every platform needs to make you prompt your way to value

@m_atoms @round Thanks!! How has your experience been with it so far? I'm working on a side project that uses Leaflet for the map (first project I've done with a map aspect to it) so I'm always curious to learn about other options I haven't heard of before.

@without_daniel @round Thanks! I'm using MapLibre GL

Agreed on all fronts. And sometimes when I do prompt with a level of granularity to get it exactly how I want it (rather than something vague and high-level), it would have taken me just as much time (if not less) to simply go and make the actual change myself, thus defeating the purpose.

This is something I noticed using AI design and vibe coding tools in general: The chat UI nudges you toward giving vague prompts. “Make the font slightly bigger” “Make this section a bit more lightweight” “Make the color slightly more vibrant” But most of these tools are aimed at professional designers — people who actually know what size feels right, why a layout feels heavy, which color carries the energy you want. interesting that the interface defaults to outsourcing that judgment rather than supporting it. And also a looming risk: if we stop articulating specific design choices, we’re slowly unlearning the craft.

I'm rebuilding the office finder UI around the philosophy that kickstarted this side project in the first place: the map is the value prop for job seekers who care about proximity to public transit, not the list. The core design decision I made in support of that is to hide the list view by default and make the map span full viewport width. This makes the map immersive, and the search overlay becomes far more out of the way and only there when you actually need it. I started experimenting with the Figma-to-Claude Code canvas connection to implement the new UI. My experience so far is that it does pretty well and executes quickly as long as the Figma frame you give to Claude isn't too complex. I hit one snag with the "show list" switch component. It turned out to be a mismatch between HeroUI's docs and how it actually needed to be implemented, which confused Claude for a few rounds. Finally I was frustrated enough with Claude getting it wrong repeatedly that I told simply told it to "think harder about what was going wrong" and then it figured it out lol. Also got Motion.dev hooked up. Excited to experiment more with movement in interactions and state changes. One thing I didn't quite anticipate when I opted to go with HeroUI as the design system was just how "AI-generated" the UI would unintentionally feel (I avoided using Shadcn for this exact reason). I may reconsider and try another system soon instead, but we'll see. For now I'm just having fun building and experimenting, and seeing the thing actually work piece by piece. A lot more tweaking, iteration, and new features ahead!

@FonsMans I completely agree. The ease of duplicating in-canvas (especially when the ideas really get flowing) really can’t be beat.

No matter how advanced creative tools get, I’ll always prefer to work on a canvas. Simply because I can duplicate my work every time I get a new idea. I want to see the progress and discover gems in past iterations.

@shashpicious_ @laurenloprete Agreed.

we’re not really “designing” right now, we’re just constantly switching contexts trying to not get left behind every week there’s a new tool claiming to be the future → paper, pencil, magicpatterns, magicpath… now noon shows up with $44M and changes the narrative again so instead of going deep, everyone’s just sampling everything trying prompts here, generating screens there, tweaking in figma, jumping to code, back to AI again half the industry is already inside code editors the other half is still figuring out which tool is even worth committing to fomo is doing more damage than we realise because depth needs stability and right now the stack itself is unstable so no one is mastering anything everyone is just trying to be early eventually this will settle and a default will emerge till then, we’re all just beta testers pretending to have a workflow 👀

@Johnogaga4 @zendadddy Totally makes sense! Thanks for sharing your insights :)

In my opinion, I’d approach it by focusing less on the title and more on clearly showing what you’ve actually shipped. Instead of trying to position yourself as a “Design Engineer,” it’s more effective to present yourself as a product designer who can take ideas all the way to production, even if that’s with AI-assisted tools like Claude Code. On a resume or portfolio, that means being very explicit about the work, highlighting the features you’ve designed and built, how you translated UI into working components, and the role AI played in helping you ship

It's wild how long the tech industry went dividing design / engineering into two separate camps. The 'design engineer' was this rare role, often people struggling to find a home and only the smartest companies knowing what to do with them. As a builder with my own side-projects, I've been in code for the past 20+ years. As an employee in corporate, I couldn't get the keys to Github. Now we're here. And it's really cool. And this will also change. Always does. 💡

@jenny_wen Same here

one silly AI thing i can’t get myself to fully adopt is meeting notes. there’s something about taking my own notes that locks things into memory for me, and seeing the notes in my own voice makes it easier to jog what happened.

I was conversing with Claude on how to create a CSS-only phased messaging component, and it asked me if I wanted it to spin up an artifact that I could use to experiment and fine-tune with in real time (see gif). Then it spit out all the files I needed to implement it into our web app. So cool

“I’ll figure it out” has gotten me further than any plan I’ve ever made

Being able to rely on Claude to help me remember and navigate git commands in the terminal has been an absolute lifesaver. Hoping I start memorizing them soon so I can go faster and feel more confident, etc

This looks awesome and so exciting!

@bandiaditya @noondesign Get Noon 🤩

I’m thrilled to announce we’ve raised $44M to build a new home for product design. Meet @noondesign. No workflow is more broken and fragmented in 2026 than the product designers’. The very same people who care most about building software don’t have software purpose built for them. @kushagrasinha7 and I have lived this problem first hand as designers ourselves. That’s why we built Noon. The first product design tool that works entirely on your product code, so you can design not only how a product looks, but also how it works. With AI at its core that works in seconds, not minutes. For the first time, you can create, iterate, build, test and ship. All in one canvas. No translations or roundtrips to the codebase and back. Comment “Get Noon” and we’ll get you on the list for early access.

@pablostanley I feel this way as well. Broadly speaking, it feels like I’m becoming more of a facilitator of things rather than a creator of them (if that makes sense 🤔)

I feel that lately... with AI I'm becoming less of a designer and more of a combo of a PM and an engineer and I don't know how to feel about it it's cool, I guess?

@MarlonCraft Great album, Marlon. I love the experimentation on this record and your willingness to be bold and try new things. Also the instrumentation is insane 🔥

my fourth album, many years in the making The Internet Killed The Neighborhood streaming everywhere now soulspazm.ffm.to/theinternetkil…