Egil Østhus

Does it allow the developer to work more efficiently together with others? And secondly, also, it's about the commercial thinking. So does this really fit into the open source part or does it fit more into kind of the enterprise part? Is this something we should bundle this as a value add? So that's more the commercial conversation of everything.

And when it comes to technical depth, it's sort of you need to trust the developers. You need to trust your engineering acumen. It's just saying you are going to take shortcuts along the way. Technical depth might be okay. But you also need to allow and make sure that you continue to have a clean code or as clean as possible.

And when it comes to technical depth, it's sort of you need to trust the developers. You need to trust your engineering acumen. It's just saying you are going to take shortcuts along the way. Technical depth might be okay. But you also need to allow and make sure that you continue to have a clean code or as clean as possible.

And when it comes to technical depth, it's sort of you need to trust the developers. You need to trust your engineering acumen. It's just saying you are going to take shortcuts along the way. Technical depth might be okay. But you also need to allow and make sure that you continue to have a clean code or as clean as possible.

It's really important also to involve the developers into the prioritization, saying, OK, this is what we're thinking we need to build next. What else is there? Does this make sense? Is there anything that you think is more important? So we have actually had a few releases also of Unleash where it was really hard to see the difference.

It's really important also to involve the developers into the prioritization, saying, OK, this is what we're thinking we need to build next. What else is there? Does this make sense? Is there anything that you think is more important? So we have actually had a few releases also of Unleash where it was really hard to see the difference.

It's really important also to involve the developers into the prioritization, saying, OK, this is what we're thinking we need to build next. What else is there? Does this make sense? Is there anything that you think is more important? So we have actually had a few releases also of Unleash where it was really hard to see the difference.

But down there in the code, we know that we clean up quite a bit in order for us to kind of make sure that when we continue to develop the product, it It's still healthy. It's still good. So I'm not sure. It's not an easy answer as a product person or kind of developing a great product for yourself. You need to kind of set the direction of how do you want to make those prioritizations.

But down there in the code, we know that we clean up quite a bit in order for us to kind of make sure that when we continue to develop the product, it It's still healthy. It's still good. So I'm not sure. It's not an easy answer as a product person or kind of developing a great product for yourself. You need to kind of set the direction of how do you want to make those prioritizations.

But down there in the code, we know that we clean up quite a bit in order for us to kind of make sure that when we continue to develop the product, it It's still healthy. It's still good. So I'm not sure. It's not an easy answer as a product person or kind of developing a great product for yourself. You need to kind of set the direction of how do you want to make those prioritizations.

And of course, more than anything, you need to be true to them because as soon as you start having paying customers and the bigger the contracts and the bigger the clients, the more leverage they will have in order to kind of, we really, really need this. If you have a really good direction of the product, it's also easier to kind of push back and say, yeah, I hear you.

And of course, more than anything, you need to be true to them because as soon as you start having paying customers and the bigger the contracts and the bigger the clients, the more leverage they will have in order to kind of, we really, really need this. If you have a really good direction of the product, it's also easier to kind of push back and say, yeah, I hear you.

And of course, more than anything, you need to be true to them because as soon as you start having paying customers and the bigger the contracts and the bigger the clients, the more leverage they will have in order to kind of, we really, really need this. If you have a really good direction of the product, it's also easier to kind of push back and say, yeah, I hear you.

Let's focus on does this really bring the value that you're really solving for?

Let's focus on does this really bring the value that you're really solving for?

Let's focus on does this really bring the value that you're really solving for?

I think we're looking for a healthy balance of experience and hunger or ambition. you need to have experience on a team, right? You need to have somebody that know the ins and outs and the playbooks, but also you're looking for people that is super eager to join you.

I think we're looking for a healthy balance of experience and hunger or ambition. you need to have experience on a team, right? You need to have somebody that know the ins and outs and the playbooks, but also you're looking for people that is super eager to join you.

I think we're looking for a healthy balance of experience and hunger or ambition. you need to have experience on a team, right? You need to have somebody that know the ins and outs and the playbooks, but also you're looking for people that is super eager to join you.

And initially we were also looking for individuals that was sort of open for just come and build, because one thing is to come and build the product, but also part of that is also how do we build the product? Meaning we don't have every process defined, obviously we don't have everything sorted. So it's sort of a different kind of state of mind or a species actually that, that,