Channels

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

Engineering

Filed under this by 32 pieces from 6 sources · the whole ledger

  1. Elected as a Fellowwallawalla.eduphoto
  2. Нумерологія в API: 5 систем розрахунку за одним маршрутомastroway.infostory
  3. Карта каталогу: як влаштовані 700+ ендпоінтів AstroWayastroway.infostory
  4. Engineering paw safetywallawalla.eduphoto
  5. Три офіційні SDK: TypeScript, Python, PHP замість сирого curlastroway.infostory
  6. Doing the right thing when things go wrongintercom.comstory
  7. Doing the right thing when things go wrongintercom.comstory
  8. X-Cache header: видимий cache-status для оптимізації клієнтських інтеграційastroway.infostory
  9. Reports V2: один ендпоінт замість дванадцяти - `/v1/reports/generate`astroway.infostory
  10. Vedic-астрологія через API: від Парашари до Лал Кітаб у 354 ендпоінтахastroway.infostory
  11. White-label PDF без WordPress: inline branding через одне полеastroway.infostory
  12. Як збудувати астрологічний застосунок: повний путівник для розробникаastroway.infostory
  13. Швидкий старт API астрології: TypeScript і Python за 5 хвилинastroway.infostory
  14. Rectification API: корекція часу народження для розробниківastroway.infostory
  15. Go is the Best Language for AI Agentsgetbruin.comstory
  16. Go is the Best Language for AI Agentsgetbruin.comstory
  17. Bruin VS Code Extension: The Architectural Challenge of Integrating Vue.js Webviewsgetbruin.comstory
  18. Bruin VS Code Extension: The Architectural Challenge of Integrating Vue.js Webviewsgetbruin.comstory
  19. Python vs SQL: Choosing the Right Toolgetbruin.comstory
  20. Python vs SQL: Choosing the Right Toolgetbruin.comstory
  21. The Effective LLM Multi-Tenant Security Solutiongetbruin.comstory
  22. dbt vs Bruin: Why End-to-End Wins Over Transformation-Onlygetbruin.comstory
  23. dbt vs Bruin: Why End-to-End Wins Over Transformation-Onlygetbruin.comstory
  24. The Effective LLM Multi-Tenant Security Solutiongetbruin.comstory
  25. Fivetran vs Bruin: Beyond Data Ingestiongetbruin.comstory
  26. Fivetran vs Bruin: Beyond Data Ingestiongetbruin.comstory
  27. How I Survived (and Thrived) in the Zombie Apocalypsegetbruin.comstory
  28. How I Survived (and Thrived) in the Zombie Apocalypsegetbruin.comstory
  29. The Hidden Costs of DIY Data Pipelinesgetbruin.comstory
  30. The Hidden Costs of DIY Data Pipelinesgetbruin.comstory
  31. The Pains of Data Ingestiongetbruin.comstory
  32. The Pains of Data Ingestiongetbruin.comstory

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