Rotem Hermon

You would think this would be a simple task for an AI agent: “I have a document from our PM describing E2E scenarios for a feature in our product.

When I work on specs or designs with agents, it usually becomes a collaborative process.

I’ve been thinking quite a lot about AI-driven agentic development and what it takes to make it safer when developing sensitive products.

In my last post I introduced my side project, BEAR - a tool that tries to show how agentic development may be done in a safer way, by creating boundaries for agents as they develop, and allowing humans to be alerted when agents try to expand these boundar…

In the last few posts I’ve been thinking about how development might change when agents can write large amounts of code very quickly.

Lately there are many posts celebrating the death of friction, praising how AI removes the friction of writing code and increases development velocity.

When we look at the history of programming language revolutions, there’s a consistent pattern.

Look, vibe coding is great.

Software, as a technology, is now underlying almost every aspect of our world.

I came across this recent post by Mikko Alasaarela - The Rise of Emotionally Intelligent AI.

There are some things in life that everyone tells you not to do.

When modeling data in Elasticsearch, a common question is how to design the data to capture relationships between entities, to allow at least some level of “joins”.

When building a distributed service, there are cases where you need to broadcast messages to all nodes running your service.

During 2011-2013 I had the pleasure of working as Chief Architect for serendip.me, helping to build it from the ground up together with Sagee and Asaf, Serendip’s founders.

Elasticsearch is the hot new kid on the NoSQL-Big-Data block.