Channels

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

Patterns

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

  1. Type-Safe Environment Variables in Convexconvex.devstory
  2. Site Up. Costs Down: Optimizing OpenClaw’s 1M Weekly Active Usersconvex.devstory
  3. Authorization In Practiceconvex.devstory
  4. Argument Validation without Repetitionconvex.devstory
  5. AI Agents with Built-in Memoryconvex.devstory
  6. Merging Streams of Convex dataconvex.devstory
  7. Translate SQL into Convex Queriesconvex.devstory
  8. Types and Validators: A Convex Cookbookconvex.devstory
  9. Optimize Transaction Throughput: 3 Patterns for Scaling with Convex and ACID Databasesconvex.devstory
  10. Convex Cookbook: Dynamic Query Buildersconvex.devstory
  11. Can your database do this? Ep 3: Zero-downtime, type-safe migrationsconvex.devstory
  12. Going local-first with Automerge and Convexconvex.devstory
  13. Components for your Backendconvex.devstory
  14. Database Triggersconvex.devstory
  15. Convex in Multiple Repositoriesconvex.devstory
  16. CRUD APIs: Functional, but Inefficientconvex.devstory
  17. Take Control of Paginationconvex.devstory
  18. Can your database do this? Ep. 1: Magic cachingconvex.devstory
  19. Log Streams: Common usesconvex.devstory
  20. AI Chat with HTTP Streamingconvex.devstory
  21. SELECT DISTINCT without SQLconvex.devstory
  22. Rate Limiting at the Application Layerconvex.devstory
  23. Work Stealing: Load-balancing for compute-heavy tasksconvex.devstory
  24. Implementing work stealing with a reactive databaseconvex.devstory
  25. Stateful Online Migrations using Mutationsconvex.devstory
  26. Operational maturity for productionconvex.devstory
  27. Testing patterns for peace of mindconvex.devstory
  28. Observing your app in productionconvex.devstory
  29. YOLO: Get to an MVP fastconvex.devstory
  30. Using TypeScript to Write Complex Query Filtersconvex.devstory
  31. Queries that scaleconvex.devstory
  32. Automatically Retry Actionsconvex.devstory
  33. Convex Ents: Manage your document relationshipsconvex.devstory
  34. Session Tracking Via Parameter Injectionconvex.devstory
  35. Using branded types in validatorsconvex.devstory
  36. Database Relationship Helpersconvex.devstory
  37. 4 Devs, 1 Idea, 4 Apps in 4 Hours(!!) with Convexconvex.devstory
  38. Zod with TypeScript for Server-side Validation and End-to-End Typesconvex.devstory
  39. Customizing serverless functions without middlewareconvex.devstory
  40. Seeding Data for Preview Deploymentsconvex.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