Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

Perspectives

Filed under this by 39 pieces from 1 source · the whole ledger

  1. I don't care about your database benchmarks (and neither should you)convex.devstory
  2. Lessons from Building an AI App Builder on Convexconvex.devstory
  3. Chef Cookbook: Tips For Working with AI App Buildersconvex.devstory
  4. Which LLM writes the best code? Convex Chef model comparisonconvex.devstory
  5. Agents Need Durable Workflows and Strong Guaranteesconvex.devstory
  6. Reimplementing Mastra Workflows: Lessons Learnedconvex.devstory
  7. Convex Evals: Behind the scenes of AI coding with Convexconvex.devstory
  8. Introducing Fullstack-Benchconvex.devstory
  9. Databased: Why Most Content Doesn't Work ft. Web Dev Codyconvex.devstory
  10. Why Convex Queries are the Ultimate Form of Derived Stateconvex.devstory
  11. Code Spelunking: Uncovering Convex's API Generation Secretsconvex.devstory
  12. Company Values that Matterconvex.devstory
  13. Convex: The Database that Made Me Switch Careersconvex.devstory
  14. An Object Sync Engine for Local-first Appsconvex.devstory
  15. Mobile-first: Building Google Photosconvex.devstory
  16. A Map of Syncconvex.devstory
  17. What is Sync?convex.devstory
  18. Configure Cron Jobs at Runtimeconvex.devstory
  19. The “full-stack framework” fallacyconvex.devstory
  20. The Ultimate Caching Definition: Invalidation, Optimization, and Layersconvex.devstory
  21. Work Stealing: Load-balancing for compute-heavy tasksconvex.devstory
  22. Databases are Spreadsheetsconvex.devstory
  23. How We Horizontally Scaled Function Executionconvex.devstory
  24. How Convex Worksconvex.devstory
  25. Compiling the Convex Open-Source Backendconvex.devstory
  26. Backends Should be Designed for Product Developersconvex.devstory
  27. Convex: The Software-Defined Databaseconvex.devstory
  28. Why I use Convex over Supabase as my BaaSconvex.devstory
  29. Building Context Augmented AI Chat in Practice: AICamp 2023 EOY Meetupconvex.devstory
  30. Everyone Can Be a Full-Stack Engineerconvex.devstory
  31. Searching for Sanityconvex.devstory
  32. It's not you, it's SQLconvex.devstory
  33. Ready for Actionsconvex.devstory
  34. Jamstack Conf 2022 Panel: The Future of Databasesconvex.devstory
  35. The serverless revolution deserves more than just a serverless databaseconvex.devstory
  36. The future of databases is not just a databaseconvex.devstory
  37. The platform you need, when you need itconvex.devstory
  38. Data Interactivity in the Serverless Future (HYTRADBOI 2022)convex.devstory
  39. The unfulfilled promise of functional ideals on the webconvex.devstory

A topic here is a label each publisher printed on its own piece. Equal labels from different publishers are shown together; that does not make them one subject.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Where this comes from

Solid branches are exact SourceFrontier census edges used by this page. Folded branches share the publisher but did not supply these items.

Hacker News

1 feed · 1 available · hn.algolia.com

text1 channel · 1 available
  1. Used here by hn-new hacker-attention Hacker News
    used on this pagehacker-attention

Latest

It's enough - vibecoding tag crossed from useless to harmfulThe vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of. Please split it or kill it. But we'd be better off without what exists today. Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting arviraptor lobste.rs