80% AI-Written Code: How 1KOMMA5 Measured the Real Impact of AI on Engineering

Can you, before we go into the iTopic, first of all, thank you so much.

I really think it's a great goal and ambition that your company has that you're working for.

And, you know, I think we all know now the next heat wave is coming here across Europe, that this is something we definitely all need to tackle.

But I want to have one more question on your tech stack.

Can you tell me a little bit about what's the coding languages that people are using? What's your CI, CD look like? And if something has changed since you adopted AI, maybe let's take the state of what it was before you chose AI.

Yeah, so our tech stack, there's one very interesting bit, but I'll save this to the last.

So our tech stack is pretty, I would say, usual.

We are on GCP, we have GitHub Actions, we have TypeScript Stack, we have on Vercel some apps with Next.js and Nest.js, but we also have some Python apps.

And then we have this whole IoT layer.

So we actually created our whole own IoT device that we shipped to the households, which runs a set of microservices in that with that Aritmint Golang, which then connect and steer each individual household asset.

And the most interesting part, I would say, is that we have not introduced Kubernetes and are actively trying to avoid introducing Kubernetes.

We are purely running on Google Cloud Run, with one very small exception, just to stay faster and to avoid this overhead and a platform team of having to manage a whole Kubernetes cluster, especially when the startup is growing and fast changing.

This choice has been really good so far and we have not regretted it because CloudTrend also keeps adding capabilities and growing.

And I think this was also one of the arguments, either there was a question after your keynote or in the hallway when somebody said, so you're speaking at Cloud Native Summit Munich and you are saying you're not using Kubernetes, but then the point is Kubernetes doesn't mean Cloud Native, right? You're using all of the cloud services from Google to run your digital services.

But I got one question, though.

There's also GKE, right? If you want to avoid the overhead of running a Kubernetes cluster, was GKE ever a consideration?

We actually have GKE for our endpoint where the devices connect to.

So our IoT fleet connects to GKE just because we need MQTT there and you can only have HTTP endpoints in Cloud Run.

think they might have changed it recently.

But yeah, so this is our only GKE and we actually never had the need to introduce Kubernetes because we scale so well with Cloud Run so far.

But yeah, we looked into it, but thought okay the trade-off isn't there because you still need to manage all of around right so you still need to set up the whole platform stack i would say it's yes the clusters manage but you still need the whole platform stack and so far we've gone really well with cloudram

sandy

that's

an example of uh Picking technologies based on real reasons.

So Andy and I, I often bring up the fact that a lot of people will say, oh, I'm going to take and run this in Kubernetes because that's what everybody's doing.