The cloud adoption trend isn’t slowing down. That’s no wonder: cloud computing has completely changed the way we think about IT infrastructure. However, for organizations that deal with never-ending deployments, the complexity of provisioning and managing all the infrastructure elements can become a headache and a source of serious issues. In this case, infrastructure codification, known as Infrastructure as Code, comes to the rescue.
Part I of this article focused on awareness and gave a few examples of how technology choice can have serious consequences for the future of your product: to the point of making or breaking your business. Part II investigates how and why the ripple effect of this one decision can reach as far as your recruitment schedule, delivery plans and innovation potential. Mind you, this applies not only to technologies in FinTech!
I’ve always been passionate about technology and that’s why I was shocked by the meeting I had recently. I was in my home office talking on Skype with a CTO from a FinTech startup (let’s call him Richard). Richard explained that he wanted us to build some payment processing service but, to my surprise, what he said was…
With more than 400 completed projects at Code & Pepper, we’ve worked out an optimal development approach, which allows us to successfully deliver FinTech solutions, no matter what your product does and where your business is located. This approach is based on some fundamental values shared in our teams: transparency, agile approach, deep technical knowledge, excitement and motivation with every new project and challenge. If you would like to know what to expect from Code & Pepper, this is where you’ll find the answers to many questions.