If I could give only one piece advice for CTOs and IT teams, it would be this: Data security is not just an IT task—it comes down to people and processes. As a startup CTO, you’re often going to lead the charge when it comes to information security for your firm. According to the Identity Theft Resource Center, U.S. companies and government agencies suffered a record 1,093 data breaches in 2016—a 40 percent increase over 2015. We’ve all seen the headlines and the high-profile victims, but attackers don’t discriminate when it comes to security breaches. Any company can become a victim, leading to losses of your data, your customers’ data, financial information, proprietary product information, and, ultimately, a loss of goodwill in the market. As more processes move online and into the cloud, companies increasingly feel this burden of staying secure.To read this article in full or to leave a comment, please click here
If I could give only one piece advice for CTOs and IT teams, it would be this: Data security is not just an IT task—it comes down to people and processes. As a startup CTO, you’re often going to lead the charge when it comes to information security for your firm. According to the Identity Theft Resource Center, U.S. companies and government agencies suffered a record 1,093 data breaches in 2016—a 40 percent increase over 2015. We’ve all seen the headlines and the high-profile victims, but attackers don’t discriminate when it comes to security breaches. Any company can become a victim, leading to losses of your data, your customers’ data, financial information, proprietary product information, and, ultimately, a loss of goodwill in the market. As more processes move online and into the cloud, companies increasingly feel this burden of staying secure.To read this article in full or to leave a comment, please click here
As your business grows, it’s increasingly important to understand how to scale engineering processes and methodologies. The amount of time spent on setup, deployment and manually testing code is often ignored by technology teams and managers. Manual server configuration and code quality tests are not only error prone, but they ultimately result wasted time and money.3 steps to automate software development
Introducing automation into your Software Development Lifecycle (SDLC) and infrastructure scaling projects is the most effective way to improve code quality and deployment velocity. These three steps will help you do that:1. Implement a continuous integration strategy
Continuous integration (CI) is a development practice where code is checked into a code repository, tested and verified in an automated process. By regularly integrating changes into a centralized repository that is automatically tested for code quality, syntax errors and unit/integration test issues, errors can be detected and located more easily.To read this article in full or to leave a comment, please click here
Success of a company is often a double-edged sword for technology teams. Enthusiastic customers, positive sales numbers and increased opportunity generally mean only one thing for a CTO—the need to scale.For start-ups, determining how and when to scale can be a challenge. Just when you hire your first set of developers and build the product, you’re faced with the need to grow your team and ensure that technology can accommodate an expanding number of users. Resource management is also key—and technology and process, in addition to people, can help you to scale wisely without having to rebuild your product. After managing the challenge of scaling at a number of companies, I’ve narrowed it down to three elements of scaling to keep in mind when it comes to people.To read this article in full or to leave a comment, please click here
I’ve built my career in a field where trader voice technology has only improved incrementally over the past 40 years. After decades of building legacy technology, my co-founders and I set out to disrupt the industry we had helped build.Despite years of leading technology teams and large-scale product launches, I was presented with a unique opportunity to start from the ground up. I had to start from scratch with a new set of technology, build a team, create architecture that was future-proof, scalable, secure and compliant, and take on the task of educating our customers and my team about why WebRTC and the Amazon Cloud was the right technology for our stack. It was daunting task, but also a common set of circumstances for a modern startup CTO.To read this article in full or to leave a comment, please click here
I’ve built my career in a field where trader voice technology has only improved incrementally over the past 40 years. After decades of building legacy technology, my co-founders and I set out to disrupt the industry we had helped build.Despite years of leading technology teams and large-scale product launches, I was presented with a unique opportunity to start from the ground up. I had to start from scratch with a new set of technology, build a team, create architecture that was future-proof, scalable, secure and compliant, and take on the task of educating our customers and my team about why WebRTC and the Amazon Cloud was the right technology for our stack. It was daunting task, but also a common set of circumstances for a modern startup CTO.To read this article in full or to leave a comment, please click here
Leo Papadopoulos