As a CTO I am responsible for making technology-related decisions, taking into consideration the specific business objectives. My goal is to facilitate the working process within a company by shaping a strategic plan tailored to the company culture. I closely cooperate with Product Owers and developers utilizing my expertise in narrow technical domains.
Basing on the things we have learnt so far, we can now move on to discussing the techniques of debt measuring and their use in the prioritisation, monitoring and prevention of technical debt.
Technical debt and the software entropy it brings lie beneath a lot of software making failures. Read this post to find out what technical debt is and where does it come from.
Managing servers and infrastructures manually is not a very complicated task, but when you start working with multiple servers, manual configuration is getting more complex and almost unachievable. This is where the notion of Infrastructure as a Code comes in.
As a part-time Rubyist, I couldn’t ignore Crystal any longer (+ I enjoy learning new programming languages) so I decided to give it a try. Because I wanted to write something useful and contribute to the community, I was looking for a small idea in the Ruby world and spoiler alert… I found it.
