Jens Becker

Honestly, this is the most accurate diagram I've seen. Waterfall: You plan for 18 months and deliver exactly what nobody needs anymore. Agile: You deliver something usable at every step, but the CEO keeps asking, "Where's the car?" AI: You get the car on day one. It has six wheels, the doors are on backwards, and it has a rocket launcher. You spend more time making it yours than actually "building"; it's shaping. owning. verifying. That's what the best AI developers do now. They don't build. They shape and own.

@SeanZubrickas @payloadcms Yes, that’s the easy part 😄 The edit view is where it gets more challenging, since there isn’t a dedicated slot for the timestamp fields, at least as far as I’m aware.

@jhb_dev @payloadcms If you wanted to do this in the list view you could simply make a custom cell component! I don’t think it would be too difficult

call us MGM because we added more slots in @payloadcms 🎰

We’ve made all CDN serving on Vercel 10% faster (P75), while reducing memory by 15%. Learn the behind the scenes of applying Bloom filters to this problem, while serving 1T monthly requests. vercel.com/blog/how-we-ma…

My current Claude Code flow that I love: 1. Give Claude Code a task 2. Set auto-accept edits to ON 3. Review its changes 4. Git-stage the good changes immediately 5. Repeat step 1 for adjustments 6. Git commit ✅ Staging lets me confidently commit. Unstaged means still refining

@wiesson @astrodotbuild 💯😄

@astrodotbuild feature request - it would be cool if we could have "LLM" here :)

@neversitdull Ah, okay. Cool!

@jhb_dev For this project just using SQLite and turso, so no. Definitely want to tinker with setting up and hosting Postgres though next time!

Just self-hosted my first Nextjs/Payload site! Still a huge fan of Vercel, but feeling pretty empowered by how easy Dokploy/Coolify make it all!

@SebastianRoehl @starter_story That's so cool, congrats Sebastian! 🎉

I had the honor to be featured on @starter_story and talk about my business and how I got it started!

@marckohlbrugge I can definitely recommend you to use it inside Cursor. Gives you the best of both worlds, especially with Claude's IDE integration!

Been playing around with Claude Code a bit more. What's crazy is that there's no code editor. You CANNOT see your files or edit them. You can only "vibe-code". My first thought was this would be horrible. I want to see my code! But Claude Code's system prompt and tool calling seems really well implemented. With the same model (sonnet 4), I'm getting better "one-shot" results from Claude Code than I get from Cursor. When you ask it to do something, it will automatically make a plan, review your existing code, and then incrementally work towards your goal. You just occasionally have to approve a (potentially dangerous) tool call. But other than that it goes all the way from prompt to finished result by itself. Whereas Cursor's agent mode sometimes seems a bit aimless, making changes you didn't ask for. Or asking for more input DURING the implementation, rather than front loading it all (e.g. like ChatGPT Deep Research does). I think because it lacks this planning step. The difference could potentially be explained by Cursor being more token-constrained (because they have to pay Claude whereas Claude doesn't need to pay itself). Or it could simply be that Cursor's agent is more optimized for the workflow where the programmer is more actively involved. And it's true that for me Cursor works best when I ask it to work in incremental steps where I review in between. (This is one of the reason I haven't used the new Background Agents that much yet) Having said all that, I do WANT to see my code. So I still much prefer Cursor's UX. Even when I use Claude Code, I find myself opening Cursor to review the code changes. I hope (and expect) that Cursor takes some inspiration and uses more of this "planning" approach in its agent. It seems to work really well. For now I'll keep using both. Fun to see the different approaches.

Tried Claude Code today, and wow, it's powerful! But setting it up inside Cursor on Windows was trickier than I expected. To save you some time, I just wrote a step-by-step setup guide to set it up using WSL: jhb.software/en/articles/cl…

BIG DAY. @payloadcms has joined @figma! We're about to take things up a notch. So proud of what we've built, and I know where we're going... can't wait to share more.

Geat idea! I would also block paths containing .env, which I frequently see in website logs.

@payloadcms Awesome 🤩 good job

Introducing Payload Folders (beta) ... → Supports any type of Collection → Browse by media, or browse by anything → Set permissions on folders → Drag n' drop files into folders → Multi-select with CMD + Click & Shift + Click Get started in one line: npx create-payload-app

@picsoung @pqoqubbw @brandfetch Thanks for sharing! One suggestion: use aria-hidden on the duplicate images to avoid redundant content for screen readers.

@pqoqubbw Really cool! Got inspired to build something to easily create such animations using @brandfetch APIs 🤩 Example here: 👇 marquee-builder.lovable.app/?domains=githu…

hear me out you don’t need js to create a marquee animation just a couple of lines of css and duplicated children with `aria-hidden`

@CollierAdam @motiondotdev @astrodotbuild Looks great 😍

Added a new photos page to my personal site and liked the idea of having a stack of photos that expanded into a carousel (utilising scroll snap), built with @motiondotdev and @astrodotbuild

@jacobsfletch @payloadcms That's great!

Just added a progress bar to @payloadcms and it feels so much faster to navigate. React Suspense is great, but it meant rendering skeleton UI for full page transitions. This way users still get immediate visual feedback, plus the resulting page renders in its entirety.

@tweetsbycolin @peer_rich I would render this part of the footer on the server instead of serving it statically. With @astrodotbuild I would use a server island for this.

Fun bug on @peer_rich's personal site... The footer shows 2024, but the footer has: {new Date().getFullYear()} Looks to be cached at the build step. What's the best way to solve this?

@ImSh4yy @payloadcms is the best CMS.

Markdown is the best CMS.

@colinhacks Astro is great! It even supports link prefetching, so you don’t have to miss out on that feature: docs.astro.build/en/guides/pref…

the equivalent in Astro...is pretty fresh it must be admitted that the final Astro build is 29kb vs 841kb for Next.js. but Next.js gives me link prefetching and image optimization out of the box. i also like .ts files idk