Engineering Ideas

Engineering Ideas

Ethics, safety of artificial intelligence, the science behind intelligence and decision-making, as well as the development of organizations and communities, along with methodological approaches.

National
English
Newsletter (Digital)

Outlet metrics

Domain Authority
92
Ranking

Global

N/A

Country

N/A

Category

N/A

Traffic sources
Monthly visitors

Articles

  • Jan 7, 2025 | engineeringideas.substack.com | Roman Leventov

    Everyone is talking about AI agent architectures, frameworks, and protocols at the moment. Let me apply John Doyle’s architecture theory lens to this topic, as well as Micah Beck’s hourglass model (2019). In this first post in this series, I present the key ideas from the architecture theory and the hourglass model. In the next post, I will apply these ideas in the domain AI agents. The two core concepts in John Doyle’s architecture theory are levels and layers.

  • Oct 12, 2024 | engineeringideas.substack.com | Roman Leventov

    This post is a reply to Eugene Kirpichov's post on Linkedin.

  • Sep 6, 2024 | engineeringideas.substack.com | Roman Leventov

    This article is the ultimate one in the five-piece series:1. “The future of OLAP table storage is not Iceberg” argues for why object storage-based open table formats: Apache Iceberg, Apache Hudi, and Delta Lake, although they may completely cover all analytical querying needs for some data teams, impose several significant limitations and inefficiencies for some OLAP use cases, and therefore shouldn’t be trumpeted as the “future” of columnar table storage. 2.

  • Sep 4, 2024 | engineeringideas.substack.com | Roman Leventov

    In the previous article, I argued that there is an opportunity for creating a new family of protocols: table transfer protocols, namely Table Read and Table Write protocols to address the M x N interoperability problem between OLAP, timeseries, vector, and search databases on the one hand and data processing/query and ML engines on the other hand.

  • Jul 15, 2024 | engineeringideas.substack.com | Roman Leventov

    Software engineers often gravitate towards projects with minimal non-software components and minimal direct interaction with the real world. This tendency, akin to searching for lost keys under a streetlight, stems from their desire to avoid real-world bottlenecks and business risks that can leave them feeling idle or powerless to influence the fate of the product they are working on.