Thomas Dohmke

The fun part is to implement something and I can see it appear in front of me on my screen.

I have the magic in my hands and I could create something with just code, right?

You hit the head on the nail.

Is that how you say it?

You hit the head on the nail.

The hammer on the nail.

No, but I think software development is a combination of creative work, of art, something that's very similar to what an artist does, and it's also production.

what Bill Gates famously called the software factory and both of these things are combined and so part of the job of a developer is being creative implementing something in software and the other part is working with the team developers product managers designers to verify the product and that is both from a UI UX perspective like looking if the product actually does and look like it was intended to be but also from a code quality perspective from a does the you know the

The piece of software I produce, does that align with what the rest of my team has been doing?

Or is there now a conflict between those things?

So a lot of the time that developers are spending every day is actually on that production side of the creative process.

And often that is the more boring piece for many developers.

And that's where automation is great because I actually want to spend more time in the creative part of it.

You know, designing ultimately what I'm shipping to my customers and automate as much as I can on the production side.

So to give one example over the last...

10, maybe 20 years, almost all production deployment has been automated.

So it used to be, you know, in the late 90s and early 2000s when the internet started, you would have some files in your local machine and you would use a protocol like a so-called FTP, file transfer protocol, and upload files to a box somewhere.

then replicate that process and maybe had a script to automate that to some degree.

But that was a very manual process and if something went wrong, your page went down and then you had to figure out what did I do wrong or what server has a problem.

Today, all you really do is you use this pull request that you described so eloquently where I submit my work for review by my team.