Ben Hofferber
Vibe coding with Claude can lead to fast code and bad abstractions. Learn how the OODA Loop and interview step improve AI-generated code quality. Part of the 2025 AI Coding Workflow Best Practices Series.
Named Design Contexts and Design Contexts as Code (DCaC) can greatly simplify the process of creating a scalable design system that is easier to understand and more friendly to change.
Contentful, Sanity, and Strapi are the headless CMS platforms we recommend most often to our clients. Here's a comparison of features that matter, plus an in-depth guide to choosing the right headless CMS platform for you.
A headless CMS offers more flexibility to integrate with a variety of front-end solutions and devices, making it an excellent option for highly scalable and performance-focused websites. Non-technical team members can edit content, optimize for SEO and performance, and use the same content across different channels and touch points.
Plus, what AI won’t tell you about how to choose a headless CMS. Read how Sanity, Contentful, and Strapi compare on features that matter.
We use Junior, Intermediate, and Senior in our conversation, but know these seniorities are somewhat arbitrary. During our talk, we discuss that the Junior archetype needs support to complete complex tasks and learn new tools. Intermediate developers are looking to tackle larger problems but don't have the problem-solving experience required to tackle difficult problems without support. Senior developers are the first to reframe a problem and efficiently solve problems and match the problem to its appropriate context. We see Seniors as developers with the most problem-solving experience and not developers with the most knowledge.
Angular has its roots in AngularJS, and many of the models from that initial framework remain relevant in the version we use today. Even with new changes like Standalone Components coming to the language, teams should be aware of the history and methodology at work here. Architects especially need to look for language features and anti-patterns that might trap their team and lead to performance bottlenecks in their systems.
Classic content management systems (CMSs) allowed authors to show up with their content without needing much help from developers or designers to update content on these sites. As time progressed, these CMSs became burdensome to those utilizing them. We see teams lack the flexibility to work with the tooling that they desire, leading to hiring challenges. Publishing slows, and time-to-market for new changes slows to a crawl. IT budget jumps as adaptations to configure custom solutions to solve business problems slow upgrades and further work. Customers struggle with longer load times and notice features missing compared to other newer sites.