[whynotmaybe]

I'm still balancing on whether we "need" to know what's happening.

Very few understand deeply what's happening within the computer between the cou and the bridges and the rest.

The fdiv bug in 1994 took us all by surprise because we were in a situation where bug couldn't exist in hardware, because it either works or it doesn't.

When I'm using firebase or aws, I don't know the underlying system, I don't know why some resources can be created with an underscore or other can't start with a number.

Yet it works.

We're working in layers where usually we only touch the last one. Yes, understanding the others is great to debug.

I'm even wondering whether we need tests when they are written by the same llm that wrote the code.

[bluefirebrand]

> I'm still balancing on whether we "need" to know what's happening.

Of course we do. Otherwise we start trying to water crops with Brawndo

> Very few understand deeply what's happening within the computer between the cou and the bridges and the rest

But it's very very important that those people deeply understand it. We cannot replace their actual knowledge with LLM approximations of their knowledge

[whynotmaybe]

>Otherwise we start trying to water crops with Brawndo

But it got electrolytes !

For now it seems we're veering towards even more specialization in roles.

The concept of "Full Stack" might disappear because, well any LLM can center a div now and create the sql query that fills it with data.

When asking a LLM about "any sre interview question that LLM got wrong ?", it identifies the questions and the corrects answers.

I should take some time to discuss with an LLM to see their answer for one of my last assignment where the underlying issue revealed by bad performance was simply that the client shouldn't have used relational db for almost immutable documents.

And that they should have bought a math library instead of writing their own.