# cto Published articles for cto. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automattic CEO Matt Mullenweg returned after 33 hours of leave without a public explanation DevFeed: [Automattic CEO Matt Mullenweg returned after 33 hours of leave without a public explanation]() Original publisher: [Read original article]() Author: Adrian Bridgwater Published: 2026-09-16T20:39:42Z Content type: news Language: en Sources: [The New Stack]() Topics: [WordPress](), [App](), [Open Source](), [Tumblr]() Tags: [cloud-services](), [company](), [cto](), [developer-tools](), [governance](), [matt-mullenweg](), [open-source](), [wordpress]() ### AI overview Automattic CEO Matt Mullenweg was placed on leave and reinstated about 33 hours later. The company has not publicly explained what prompted the leave or return, while observers have raised--but not established--the possibility of an attempted change in control. ### Source excerpt There were unusual goings-on this month at Automattic, a company known for its free and open-source app for building WordPress The post Automattic says CEO Mullenweg was gone and back inside 33 hours. What happened between? appeared first on The New Stack. ## Why Code Verification Matters More Than Ever in the Age of AI DevFeed: [Why Code Verification Matters More Than Ever in the Age of AI]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-08-24T15:31:01Z Content type: article Language: en Sources: [ByteByteGo]() Topics: [Code](), [AI-assisted coding](), [Artificial Intelligence]() Tags: [ai](), [ai-assisted-coding](), [code](), [cto](), [developers](), [verification]() ### AI overview The article explains why code verification is becoming more important as AI-assisted coding makes software production faster. It discusses the growing review burden, low confidence in AI-generated code, and research indicating that increased AI use can create pressure on delivery stability and developer productivity. ### Source excerpt In this article, we will look at how code verification works, why the rise of AI-generated code puts more pressure on it, along with the extremely useful insights from Andrea on what the future may look like. ## Behind the Flame: Ellie Cherrill DevFeed: [Behind the Flame: Ellie Cherrill]() Original publisher: [Read original article]() Author: Megan Batterbury Published: 2026-07-02T14:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [coding](), [incident](), [Slack]() Tags: [coding](), [cto](), [customers](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [on-call](), [outage](), [post-mortem](), [slack](), [slack-incident]() ### AI overview This profile follows Ellie Cherrill, a Product Engineer at incident.io, describing her rapid-paced work, which is focused largely on coding and collaboration. She discusses customizing Slack alert messages for customers and contributing to the On-Call system, where changes must be assessed for their impact across the product. ### Source excerpt Meet Ellie Cherrill, Product Engineer here at incident.io. 🔥 ## 5 predictions about agentic AI and analytics in 2026 DevFeed: [5 predictions about agentic AI and analytics in 2026]() Original publisher: [Read original article]() Author: Kristin Crosier Published: 2026-05-12T00:00:00Z Content type: opinion Language: en Sources: [Redpanda]() Topics: [Artificial Intelligence](), [data](), [Security]() Tags: [2026](), [agentic](), [agentic-ai](), [ai](), [analytics](), [aws](), [collaboration](), [cto](), [executive](), [gartner](), [governance](), [predictions](), [thought-leadership]() ### AI overview The article presents five predictions about agentic AI and analytics in 2026, drawing on Gartner's research and Peter Corless's industry observations. It emphasizes the opportunities and governance risks of agentic systems, along with the need for executive accountability, cross-team collaboration, and new skills and best practices. ### Source excerpt Learn about what's top of mind among enterprises planning for agentic systems, and top AI predictions for 2026 and beyond. ## Using Tech to Tackle Homelessness. The Artisan of the Day Is Kevin McKee. DevFeed: [Using Tech to Tackle Homelessness. The Artisan of the Day Is Kevin McKee.]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-09-17T15:16:18Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Software as a service](), [Software](), [Framework](), [Security]() Tags: [cto](), [developers](), [laravel](), [platform](), [saas](), [secure-software](), [software]() ### AI overview Kevin McKee, CTO of Padmission, describes how Laravel powers the company's SaaS platform for government agencies, nonprofits, and case managers addressing homelessness. Laravel's speed, productivity, and security help a small team deliver affordable, scalable tools for housing services. ### Source excerpt Kevin McKee, CTO of Padmission, explains how he uses Laravel to power the SaaS platform helping communities fight homelessness with secure software solutions. ## How CTOs Can Justify Technology Investments to the Board DevFeed: [How CTOs Can Justify Technology Investments to the Board]() Original publisher: [Read original article]() Published: 2025-09-15T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [DevOps](), [Cloud](), [migration](), [Automation]() Tags: [automation](), [boardroom-advice](), [business](), [chainguard](), [chief-technical-officer](), [cloud](), [cloud-native](), [cost](), [cto](), [devops](), [digital-products](), [efficiency](), [executive](), [head-of-engineering](), [infrastructure](), [innovation](), [metrics](), [migration](), [teams](), [technology-investments](), [technology-procurement]() ### AI overview The article explains how CTOs and engineering leaders can justify technology investments by connecting initiatives to measurable business outcomes such as revenue growth, faster innovation, lower costs, and reduced risk. It emphasizes using a small set of clear, baselined, trackable metrics and illustrates how cloud-native migration, containerized workloads, automation, and DevOps metrics can support efficiency and savings. ### Source excerpt Learn how CTOs can tie technology investments to increasing revenue, speeding innovation, and reducing risk and cost to drive positive business outcomes. ## Building With Purpose: The Artisan of the Day Is Alpesh Nakrani. DevFeed: [Building With Purpose: The Artisan of the Day Is Alpesh Nakrani.]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-08-26T14:24:08Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [PHP](), [Accessibility]() Tags: [accessibility](), [advocacy](), [career](), [community](), [cto](), [discord](), [jobs](), [laravel](), [php](), [remote](), [support](), [whatsapp](), [workshops]() ### AI overview A profile of Alpesh Nakrani's Laravel career, community mentorship, and efforts to help differently abled artisans access training, jobs, and peer support. ### Source excerpt Alpesh Nakrani empowers the Laravel community through mentorship, inclusion, and innovation as CTO of Acquaint Softtech. ## Building a Secure Software Supply Chain: 5 Key Insights from GitLab's Field CTO DevFeed: [Building a Secure Software Supply Chain: 5 Key Insights from GitLab's Field CTO]() Original publisher: [Read original article]() Published: 2025-08-08T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Security](), [GitLab](), [CI/CD](), [toolchain](), [Developer experience](), [Open Source]() Tags: [chainguard-containers](), [ci-cd](), [container-images](), [cto](), [developer-experience](), [gitlab](), [head-of-engineering](), [open-source](), [secure-software-supply-chain](), [security](), [software-supply-chain-security](), [tooling]() ### AI overview This article presents takeaways from a Chainguard webinar with GitLab Field CTO George Kichukov about building a secure software supply chain. It highlights the need to move from security awareness to action, reduce toolchain sprawl, embed security into developer workflows, and maintain transparency when using open source. The supplied text ends before the fifth takeaway is provided. ### Source excerpt Chainguard and GitLab recently recorded a webinar discussing challenges organizations face in building a secure software supply chain. Get the key takeaways. ## Mike Krieger and Luis von Ahn join Figma's Board of Directors DevFeed: [Mike Krieger and Luis von Ahn join Figma's Board of Directors]() Original publisher: [Read original article]() Author: Figma Published: 2025-07-21T00:00:00Z Content type: news Language: en Sources: [Figma Blog]() Topics: [Figma](), [anthropic](), [Product Management]() Tags: [anthropic](), [ceo](), [cto](), [customer](), [design](), [education](), [engineering](), [executive](), [figma](), [infrastructure](), [product-design](), [product-engineering](), [product-management](), [recaptcha](), [security]() ### AI overview Figma announces that Mike Krieger, Chief Product Officer of Anthropic, and Luis von Ahn, co-founder and CEO of Duolingo, are joining its Board of Directors. The article highlights their experience in product development, design, engineering, infrastructure, education, and internet security. ### Source excerpt Mike Krieger, CPO of Anthropic, and Luis von Anh, co-founder and CEO of Duolingo, are joining Figma's Board of Directors. ## Power struggles and long-term strategy in startups DevFeed: [Power struggles and long-term strategy in startups]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2024-12-30T14:44:46Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [Tech Debt](), [Software Engineering](), [Agile](), [Self-organizing Team]() Tags: [agile](), [case-studies](), [collaboration](), [communication](), [complexity](), [cto](), [engineering](), [leadership](), [management](), [pitfalls](), [project-management](), [recommendations](), [roadmaps](), [safety](), [software-development](), [startups](), [team-dynamics](), [tech-debt]() ### AI overview This podcast discussion examines power struggles, short-term thinking, technical debt, and operational inefficiencies in startups and scale-ups. It covers team dynamics, project management, unplanned work, communication, psychological safety, and aligning engineering efforts with business goals. ### Source excerpt Mario Tomić, fractional CTO joined Adrian Stanek and Denis Čahuk for an exchange of situational studies and examples of power struggles and lack of long term strategy in startups. Highlights below 👇 ## Meet the new host for The Secure Developer podcast DevFeed: [Meet the new host for The Secure Developer podcast]() Original publisher: [Read original article]() Author: Mariah Gresham Published: 2024-05-09T05:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Security](), [DevSecOps](), [Open Source](), [ibm]() Tags: [announcement](), [awareness](), [blog](), [cto](), [developer](), [developers](), [devsecops](), [executive](), [interest](), [leadership](), [megawatt](), [open-source](), [podcast](), [recruiting](), [security](), [snyk](), [snyk-team](), [technology]() ### AI overview Snyk announces that Danny Allan, its CTO, is taking over as host of The Secure Developer podcast from Guy Podjarny. The podcast covers developer security, DevSecOps, cloud environments, open source software, and AI-assisted development. ### Source excerpt We're excited to announce that The Secure Developer has a new host! Let's welcome Danny Allan, Snyk CTO. ## Effective incident escalations DevFeed: [Effective incident escalations]() Original publisher: [Read original article]() Author: Chris Evans Published: 2023-07-10T06:32:43Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [Incident response](), [Routing (disambiguation)](), [Process]() Tags: [bank-transfers](), [cognitive-load](), [cto](), [customer](), [guide](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [payments](), [post-mortem](), [process](), [routing](), [scope](), [slack-incident](), [time]() ### AI overview The article explains incident escalation as routing an issue to the appropriate people when its scope, understanding, timing, or severity changes. It discusses escalation policies and plans as mechanisms for assigning incidents, reducing downtime and cognitive load, improving customer communication, and ensuring timely resolution. ### Source excerpt In the ever-evolving digital landscape, every organization must confront its fair share of incidents. Regardless of the sector or size, one common thread weaves through them all: the need for effective incident management. A crucial part of this management is incident escalation. ## Game Day: Stress-testing our response systems and processes DevFeed: [Game Day: Stress-testing our response systems and processes]() Original publisher: [Read original article]() Author: Rory Bain; Sam Starling Published: 2023-02-27T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident]() Tags: [communication](), [cto](), [customer](), [customers](), [engineering](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [insights](), [on-call](), [outage](), [post-mortem](), [skills](), [slack-incident]() ### AI overview incident.io describes a Game Day designed to improve its response to larger and more severe incidents. The exercise combined a tabletop discussion with simulated incidents involving engineering, customer success, and on-call responders, and produced improvements to incident processes, response skills, and product insights. ### Source excerpt Improving the way we respond to larger, more complex incidents. ## Managing incidents in a growing organization DevFeed: [Managing incidents in a growing organization]() Original publisher: [Read original article]() Author: incident.io Published: 2023-01-12T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [Agile](), [Artificial Intelligence]() Tags: [agile](), [ai](), [cryptocurrency](), [cto](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [slack-incident]() ### AI overview A podcast episode featuring Matt Huxtable, CTO at Ziglu, discusses how the engineering team evolved, building an agile culture, managing incidents, balancing technical fixes with communication, creative incident responses, and whether AI is ready to help solve incidents. ### Source excerpt In this week's episode, we're joined by Matt Huxtable, CTO at Ziglu (an e-money issuer, offering a variety of digital finance services, particularly well known for its cryptocurrency services). ## A CTO's Three Core Responsibilities: Technology, Engineering Teams, and Executive Strategy DevFeed: [A CTO's Three Core Responsibilities: Technology, Engineering Teams, and Executive Strategy]() Original publisher: [Read original article]() Author: Sergio Visinoni Published: 2022-06-26T07:42:51Z Content type: article Language: en Sources: [Sergio Visinoni]() Topics: [Software]() Tags: [architecture](), [article](), [cto](), [delegation](), [leadership](), [software-engineer](), [team](), [technology](), [technology-stack](), [technology-strategy]() ### AI overview The article argues that CTOs have three main areas of responsibility: technology, the engineering team and organization, and participation in overall business strategy. It emphasizes that CTOs can delegate details while retaining accountability for technology strategy and execution. ### Source excerpt Hello, I've moved to Substack. Read this article and the rest of my content in my newsletter https://makemeacto.substack.com/. Hope to see you there soon! ============= CTOs have many responsibilities, but only one cannot be delegated. This is a reality that many will understand implicitly. I believe making it very explicit will help many young or even not so young CTOs out there. In my experience, as a CTOs you have 3 main areas of responsibilities: Technology, the Engineering team and the Executive team. More specifically you will have to focus your activities around: Making sure the company has the best possible technology stack and architecture Making sure the company has the best possible engineering team and organisation Contributing to the overall business strategy as a member of the executive team Let's look at each one of them in detail to draw some observations. Best possible technology stack and architecture. This is often what first time CTOs tend to focus on the most, given that in many cases they've been growing into the role from a Software Engineer background. This is definitely the area of domain expertise that is required from any senior technology leader. As the team grows, as a CTO you'll surround yourself of more and more Staff and Principal engineers as well as Architects (either with a formal or informal title). They will take over more and more responsibilities both in defining and executing the details of the technology strategy. As a CTO you will retain full accountability for ensuring that there is a relevant technology strategy in place, and that it is being executed appropriately. Many details of which you will have delegated to key senior roles in your organisation. Delegation doesn't mean ignoring. You will need to be on top of those details, without becoming the bottleneck. Best possible engineering team and organisation. This is probably what most first time CTOs struggle with, especially the ones that didn't have the chance to learn ## A CTO's Personal Journey Through Startup Leadership and Development DevFeed: [A CTO's Personal Journey Through Startup Leadership and Development]() Original publisher: [Read original article]() Author: Yonatan (Yoni) Levin Published: 2018-08-28T19:06:14Z Content type: opinion Language: en Sources: [Stories by Yonatan V. Levin on Medium]() Topics: [Development](), [Back end](), [Mobile]() Tags: [blog-post](), [cto](), [development](), [entrepreneurship](), [journey](), [personal-experience](), [product-management](), [startup](), [startups]() ### AI overview The author reflects on becoming a CTO, describing how the role differs between startups and large companies. The account covers responsibilities spanning product, technology, management, development, investors, and meetings, along with the author's experience moving from Android development into backend work and startup leadership. ### Source excerpt Around three years ago, a day I will never forget, a day that changed the course of my life. Marked the beginning of both my personal life (the day that my dear daughter was born) as well the day that the legendary entrepreneur and investor -- Eyal Gura called me and asked me to join the visionary team at KolGene together with Dan Faszczyk and build a revolutionary idea -- a marketplace for genetic tests which turnout to be a platform to managing all genetic tests of the hospital. And the rest is the history :) KolGene's magic This post will not focus on how we raised our first seed round (but we did!) Or about how we made a successful pivot and acquired our first customers (hard work!) and all of the other fuck-ups we encountered along the way. But rather, about my personal journey to becoming and being a CTO. I was recently invited to talk with Zell students about what it means being a CTO in a startup world. While preparing for the presentation I became inspired to share and write this blog post. Not the same CTO The first thing you need to understand is that a CTO position ranges from company to company (Like every position!). For example, a CTO of a small startup is very different to a CTO of large corporate company. The first requires you to do everything -- from the product, tech, managing and of course developing all by yourself. While simultaneously acquire investors and attend meetings. While a CTO in a large corporate company is far more tech only oriented, where your main responsibilities are to find out the right tech stack for a company product and explain it to the rest of the companies stakeholders. Prelude: Personal experience I was lucky enough to be able to observe various CTO's in different companies embarking on different stages: from corporate to fast-growing startups like Gett. But, since this is mostly about my journey let's talk about my personal journey to becoming a CTO. For years I was "the" go-to guy, the guy that everyone looked to for sol ## 5 things I've learned being a CTO in startups DevFeed: [5 things I've learned being a CTO in startups]() Original publisher: [Read original article]() Author: Jean-Baptiste Escoyez Published: 2015-06-25T13:58:10Z Content type: article Language: en Sources: [eFounders]() Topics: [Development](), [business logic](), [Code](), [optimize](), [App](), [Users]() Tags: [business-logic](), [code](), [cto](), [dev](), [optimize](), [productivity](), [startups](), [users]() ### AI overview A startup CTO shares two rules for making technical decisions: align engineering work with business and customer outcomes, and organize code into small reusable modules to support speed and flexibility while limiting technical debt. ### Source excerpt In the past 5 years, I have been Chief Technical Officer of two startups -- one, GoCar has been acquired and one, Solved, has been discontinued -- and helped many others as a technical advisor. What characterizes startups is that they have to ship a lot of results with limited resources. As CTO, your daily job is to lead the technical team, set the goals and take the right technical decisions. You are in a constant tradeoff of immediate speed VS long-term productivity. In this article, I want to share 5 rules I follow in order to make my choices. So far, they enabled me to keep shipping while avoiding to pile up "technical debt". 1. Dedicate yourself to the business The goal of any startup is to build a solution which will bring value to its customers. There are chances that your business co-founder will spend most of his/her time talking to them and understanding their needs. On this basis, your co-founder will set the priorities and report what customers' problems are. Your role will be to find out and build an outstanding product that provides a solution to them. As a technical person, it is easy to get excited by a new technological challenge or a new service that looks promising. When it occurs to me, I ask myself this simple question: "What is the business outcome of what I am doing". This way, I always know if I am working on the right priority or not. At Solved, we even dedicated a weekly meeting with my business co-founder, Thomas, where we were reviewing the features to ensure they match the business priorities. At any moment, I and any member of my dev team could say why we were working on any feature. In order to ensure I did a good job, I was asking myself: how will it delight our users? how will it help our startup to make money? or help our operations team? If you can also answer these questions for your own project, there are chances you are on the right track. 2. Optimize for speed and flexibility In its early days, your startup's main challenge is to