cartero Tuesday, August 11, 2026 · No. 25890
Graph Databases

Hans-Juergen Schoenig: Heterogeneous Graphs in SQL/PGQ on PostgreSQL 19

In the previous post, we discussed the basic syntax of graph queries in PostgreSQL 19 and discussed some simple SQL/PGQ examples. However, more often than not applications are more complex and need more than just two basic tables. Therefore, we want to dig a little deeper and see how we can write more complex queries and model some more sophisticated graphs based on real world scenarios. Loading sample data for graphs To demonstrate a couple queries, which happen to be increasingly adva...

Software Engineering

Slop Paralysis

Artificial Intelligence

When Science Goes Agentic

What happens to everything surrounding code—the conjectures that seed research, the review systems that validate it, and the platforms where it is shared—when science goes agentic?

Algorithms and Data Structures

Pegband

Bandying about possible solutions.

Multimodal AI

The Race to Reliable Visual Understanding

As vision-language models move from the lab into enterprise automation and robotics, the industry is discovering that "mostly right" is a recipe for failure.

Flink

Automated Schema Evolution in Pinterest’s Next-Generation DB Ingestion Framework

Yisheng Zhou | Software Engineer IILiang Mou | Sr Staff Software EngineerGabriel Raphael Garcia Montoya | Staff Software EngineerIstvan Podor | Staff Software EngineerIntroductionIn the first post of this series, we introduced Pinterest’s next-generation CDC-based ingestion platform built on Kafka, Flink, Spark, and Iceberg. In production, upstream schemas are constantly evolving, and in a distributed CDC pipeline, schema is not just metadata — it is a cross-system contract spanning ...

AI Agents

Vibhor Kumar: The AI Agent Layer: Architecture, Implementation, and the Future of Intelligent Enterprise Systems

Part 2: Planning, Tool Use, and Reflection Key takeaways Memory gives an agent continuity. It does not give it judgment. Planning, tool use, and reflection are the three capabilities that turn a well-informed model into a system that can act on a real business process. Treat the execution plan as an artifact, not a transcript. If you can’t persist it, version it, and pause it for human approval, it isn’t a plan — it’s improvisation with extra steps. A tool named ‘run a ...