I said this quite often during several projects over the last years – and often directed to persons being “difficult” with regards to discussing hard, having different opinions, contradicting a Product Owner or an Architect with thoughtful arguments. This is something you will have to accept, even if it is hard to do so. And it is exhausting, it is stressful working with such people on a day-by-day basis.
But, I changed my mind.
Or, to put it differently, I am now in a position where I want to have such characters around me. Here at Cloudibility, we want persons having their own ideas and their own minds, we want them to contradict us and to proove us to be wrong.
We want to have such minds around us. Of course, they will have to stick to our rules of respect and culture, they will need to be compatible with customers and the team. But besides this: Have your own mind, contradict, improve, overtake us!
Different to other approaches, we don’t treat them as a remote team working for us, but as our team-members working a little bit down the road. They will be participating in our processes, meetings, etc. and will be a core part of our team.
Our Indian team members are “hand-selected” the very same way as our German stuff – they have to have the same culture, the same approach to cloud-native infrastructure and processes and the same greed for excellence.
Within the next four weeks, our Indian team will be extended to at least three employees, but we are actively looking for even more of them.
So, if you want to be a part of our journey, contact me or Pradeep, the head of our Indian partner!
I do often get this question when providing our specialist’s profiles to possible customers.
Well. No. We can’t. And we won’t.
Let me explain that bold statement a little bit. There are plenty of reasons for saying so. The most important one: We have some of the best specialists here at Cloudibility.
We love our experts.
We provide our bright minds with an environment which allows them to shine – a good work-life-balance, paid educational hours, etc. We do this, since we would have liked such an environment ourselves when being employed. But it was not possible due to calculation issues. Which forced us to quit our jobs.
Therefore, we want to pay our experts reasonable salaries and want them to gain even more knowledge. We want them to stay motivated and hunt for solutions instead of billed hours. We are investing a lot into our experts, and we are very happy and proud to do so. We know, that you deserve the best expert and the best approach for your project.
But it’s still expensive, though.
Do you know how much it costs, to do without good experts? Or to simply opt for the cheaper alternative since it is … cheaper? Can you really afford the second best or a somehow okayish solution? Just for the sake of saving some bucks forehand?
Our experts are worth their money.
They are experts and bright minds, they are able to solve problems, they are able to think outside the box. They save you time and money and nerves, they bring knowledge and experience into your projects.
So, no. We won’t do special prices.
We already have the best prices in the market since we have the best experts and the brightest minds here at Cloudibility.
Because you shut down your VMs at night. Automatically.
Because you have a Jenkins-installation.
Because you are moving to a cloud environment.
Because you have set up a “DevOps”-team.
Because you have a lot of meetings with stakeholders.
Because you want a Development team to run a software since the approach is often described as “You build it, you run it”.
Because you know about this nifty image on top.
Turns out: No.
You don’t do DevOps.
You just shut down your VMs at night, you just happen to have a Jenkins-installation, you’re just moving to a cloud environment, etc.
But this is not DevOps. At least not in the sense we at Cloudibility understand it and explain it to our customers and set it up with them. To us, DevOps is not about any specific technology or setting up a team.
DevOps is a mindset.
It is an approach to thinking about, developing and running software collaboratively. It is about the way you interact from the start to the end of a project with each other. It involves getting rid of this “throwing over the fence” mentality. It involves a process for collecting and maintaining knowledge in an ever-changing team and agile approaches to development and operations. It is about the way a team is set up and how it evolves, it is about the way we set up and execute operational processes. DevOps even is a way to organize collaboration in a whole company.
So, DevOps is way more than putting Dev and Ops on the same table. Or than moving into cloud environments. Or than being agile. Way more.
In the following months and weeks, I will give you insights into our approach to DevOps. I will give you some tips and hints. I will help you to see the whole picture. I will do this on a per-issue and per-aspect base, and it will be a loose series of articles.
At Cloudibility, we are currently growing enormously – by mindset, by knowledge, and by headcount.
Last week, our team was expanded by three bright minds (in no particular order:
Sandra Sandra was a Developer once (and a very good one!) and decided to opt for DevOps. She has very strong development skills and is able to transfer this into DevOps-territory. She likes working with CI/CD-components, ELK / EFK and Kubernetes. And from time to time she will be giving presentations and trainings and speeches. She joined our team as Senior DevOps Engineer.
Ronny has a profound knowledge in DevOps-technologies as well as Kubernetes. He is doing deep dives with technologies such as Linux, Docker, Ansible, Teraform, Vagrant, Virtualization (VMware, etc.) and many more. He has joined our team as Senior DevOps Engineer.
Emilie is part of our sales team. She as an impressive track record of sales even in difficult environments, can handle customers and partners and is a very positive person. She has joined our team as Sales Manager.
We have decided on several important things at Cloudibility the last weeks. One of the most important ones was about our new logo. We had several cool drafts to decide upon, ranging from pretty much the original logo to a very minimalistic one.
Finally, we decided to go with the logo you see in this posting. It is close to the original one, but a little bit more streamlined and reduced. We adjusted the color to be a bit darker and agreed on a font to be used for business cards, our homepage and our – soon to be revealed – publication.
Here you can compare the old vs the new version:
The process of getting another logo was an example of our company’s culture as well: Initially, Michael and I did not like the idea of changing the logo so soon. But Friederike, Head of Publishing, insisted on adjusting it and making it more refined – so we agreed. Additionally, I preferred a different draft of the logo, being even more reduced, but was convinced by Friederike, Julia and Emilie (our marketing team), Claudia (our COO) and Michael.
And, boy, they were right! Thank you for disagreeing and for arguing.
Today, I love our new logo.
PS: Yes, I am aware of our Homepage being a placeholder.
PPS: I will update the logo on the Homepage during the next days.
I am delivering a Xamarin workshop this week. Unfortunately for my sleeping habits, the location is Munich, appr. 550km away from home.
The best way to get there is by train, at least if you don’t like flying. So, my train was to depart at 4.30am. Which implied I would have to leave home at latest at 3.50am.
Well. So much for the theory.
In practice, I left home at 3.55am. Which caused me to directly head on the Autobahn towards Munich. Instead of having a somewhat relaxed trip to the Bavarian capital, I had an unrelaxing one in my car. And instead of elegantly driving with an ICE-train from Munich to Frankfurt and then back home on Friday, I’ll drive back home on Thursday and try to catch the morning train from Berlin to Frankfurt on Friday, since I don’t want do sit in my car for 10+ hours.
This makes five minutes quite important.
And that’s why I try to keep an eye on the details, though I’m the high-level guy at Cloudibility.
I’ve never seen a team being that committed. That focused. That inquisitive. That eager to learn. That funny. That great.
Team, I am so proud of working with you!
Next week, we will start our expansion. I mean: We will really start it. Three new Team-Members at the beginning of the month. Two more in the middle. One more beginning of August. One more at mid of August. One, two, three perhaps beginning of September.
But: I am not afraid. I know, that we already have a great team and we will continue to be one. We looked carefully at the new colleagues’ character and found them to match the team in culture and commitment.
Sandra, Ronny, Emily: Welcome!
You will be part of Cloudibility, you will shape us and you will grow with us. And I am very confident to count you in next time when I write about the: