Thomas Dohmke

And you can kind of like do this software decomposition part first and take a big problem and break it into smaller parts.

And I think that

ultimately is what engineering means.

And then you know where to stop with the decomposition.

And now you can start coding.

And in the past, you had to start at a very low level.

Before we started the live stream, you showed me a very old computer.

And back then, it was very hard.

You had to go very low level.

Today, most engineers actually already start on code written by others, right?

They use open source libraries.

They use open source operating systems.

They have an editor that they're not building themselves and a debugger and a compiler and a container orchestration.

like Kubernetes and all these things, right?

So we're already composing different pieces into software and we're moving up the abstraction and then AI will help us, you know, to achieve that.

And then we will review the work of the AI to make sure it's, you know, secure and compliant and runs efficiently and hopefully, you know, returns some profit for the corporations or the teams we're working for.

I actually have some Legos in my hands and behind me too.

In some ways, I actually think it is a bit like Lego, right?

Because when you start working with Lego, you're not thinking about plastic, you know, pieces and forms to build bricks first before you assemble the bricks.

I think the thing that really changed through Copilot in my own coding projects, which are mostly hobby projects on weekends, is that I match faster back into the flow state.