2000 episodios
- How do you change an aging application without losing the business knowledge buried inside it? On Tech Talks Daily, I'm joined by Veli Pehlivanov, co-founder and CTO of Resolute Software. We talk about systems that still do valuable work but have become difficult to change, particularly when some of the rules live in the heads of a few experienced employees rather than in the documentation.
Veli explains where his team finds AI useful: reading unfamiliar code, tracing dependencies, generating tests, and helping with well-defined changes. He also explains why they check those conclusions against conventional analysis tools, runtime evidence, and conversations with domain experts. Code that looks correct can still do the wrong job. Understanding what a system does is a different task from deciding which behavior the business needs to preserve.
We also discuss why moving an application onto a newer framework doesn't necessarily make it easier to maintain. Veli describes an incremental approach in which old and new components can work alongside each other while teams decide what to keep, replace, or buy. The questions become more cautious around areas such as financial operations, sensitive data, and access controls, where a small mistake can affect people well beyond the development team.
For leaders assessing the return on this work, we look beyond lines of code and test counts to changes the business can see: shorter delivery times, fewer defects, lower ownership costs, or a capability the old system couldn't support. We also talk about counting the cost of validation and rework when deciding whether AI saved time. Which application would you modernize first, and how would you know the result was better for the people using it? Share your thoughts with me.
Useful Links
LinkedIn Resolute: https://www.linkedin.com/company/resolute-software-hq
LinkedIn Veli: https://www.linkedin.com/in/vpehlivanov/
X Resolute: https://x.com/ResoluteSoftHQ
Facebook Resolute: https://www.facebook.com/ResoluteSoft
Instagram Resolute: https://www.instagram.com/resolutesoftware/ - How much do you know about the code your business runs, and what could you prove about it if a customer asked tomorrow?
On Tech Talks Daily, I'm joined by Quincy Castro, CISO at Chainguard. He describes open source as an act of generosity: people publish code so others can build on it. The security question is how a company takes advantage of that work while checking what goes into its software and how those components are built and maintained.
We discuss what useful evidence looks like. Quincy talks about identifying the original source, checking components for signs of tampering, and publishing a software bill of materials and a cryptographic signature.
A bill of materials tells you what went into the software, and a signature can help you verify its origin and integrity when checked against a trusted signer. Neither tells you on its own whether the code is safe to run. Quincy makes a similar point about supplier audits. They can give buyers useful assurance, and he also wants to see how a supplier's controls work when someone asks to look behind the paperwork.
I ask Quincy where security leaders should start when the list of vulnerabilities is long and taking a service offline comes with real costs. His starting point is what the business needs to keep running after an incident. Once you know which service matters most, you can follow it back to the systems, dependencies, and people responsible for it. We also talk about the gap between what an audit samples and what an attacker might try, and how lessons from incidents can feed back into the way teams build and maintain software.
The interview closes with Chainguard's approach to AI in software development. Quincy explains why the company built Harness to help test applications with advanced AI models and Workspaces to give developers and agents isolated environments in which to collaborate.
What interested me was the question this poses for any team introducing a coding agent: what can it access, what can it change, and who checks the result before it goes live? I'd love to hear your experience. If a customer asked you to prove where a component came from and how it was built, what could your team show them today?
Please share your thoughts. - What does IGEL reaching unicorn status mean for the customers and people behind the company? It was lovely to welcome my friend Klaus back to Tech Talks Daily for a conversation that felt like a catch-up with some particularly good news.
We've spoken many times over the years, from Frankfurt to Miami, and this time we began with IGEL's valuation above one billion dollars and the arrival of Vitruvian Partners alongside TA Associates. Klaus describes what the milestone means to a team that has spent years building the business. We also talk about the company's reported annual recurring revenue growth above 40%, its expansion plans, and why he sees the investment as support for the next stage of the journey.
The conversation soon turns to why endpoint security deserves attention now. Employees are accessing company information through applications, browsers, AI tools, and increasingly agents, creating questions about access, policy, and intellectual property.
Klaus explains IGEL's prevention-focused approach, its immutable operating system, and how conditional access can work with existing identity and security investments.
His case is that the endpoint should support the wider security architecture as the way people work changes. We discuss the purpose and intended benefits of that model without treating any operating system as a guarantee against every form of attack.
Business continuity is where the discussion becomes especially tangible. IGEL Emergency Mode is an administrator-led feature within IGEL Business Continuity & Disaster Recovery.
On supported Windows endpoints already enabled for Dual Boot, it allows administrators to centrally initiate a reboot into IGEL OS during a cyberattack, ransomware event, or Windows outage.
The aim is to restore access to approved applications, virtual desktops, and SaaS tools in minutes while leaving the affected Windows partition untouched for forensic investigation and remediation. It is a prepared route back to approved work services, rather than a tool that cleans the Windows installation or repairs the whole environment.
For employees facing a disrupted working day, that distinction between waiting for device remediation and regaining access to work is worth understanding.
We also discuss the financial case for endpoint modernization and Klaus's hopes for Now & Next in Fort Lauderdale in February 2027. He describes a gathering built around partners, industry conversations, roundtables, and the chance for customers to say what they need next.
After all our conversations over the years, it was good to hear both the pride in what the team has achieved and the energy for what still needs doing.
A valuation is a milestone; the continuing test is the value customers receive in security, continuity, and day-to-day operations.
What would give your organization greater confidence that people could keep working through an endpoint disruption, and how are you preparing for that possibility? Share your thoughts with me. - Would you put an AI answer in front of your board if you couldn't tell which source supported its most important claim? On Tech Talks Daily, I'm joined by Julia Lecocq, who leads corporate sales in Europe and Asia-Pacific for AlphaSense. Julia works with teams making decisions about acquisitions, new markets, and competitive threats. We discuss why having access to thousands of documents can still leave someone with the hardest part of the job: working out which evidence applies to the decision in front of them.
Julia uses earnings call preparation to explain the difference between finding a document and putting it to work. A search might turn up an earnings report. An investor relations team also needs to know what executives have said before, whether outside evidence supports the proposed message, and what analysts might ask next. Julia also describes an unnamed M&A team using AlphaSense's SuperAnalyst to identify gaps in its strategy and compare possible acquisition or partnership targets. The output gave the team a starting point for further research. The decision about which targets to pursue still belonged to the people responsible for the deal.
We talk about what happens when a confident answer contains an outdated figure or rests on an assumption that nobody checks. Julia says a mistake early in a multi-step research task can carry through to the final recommendation. A citation gives an analyst somewhere to start. They still need to open the source, check when it was published, see whether it supports the exact claim, and look for evidence that points in a different direction. Julia also raises a point for managers: when AI takes on the initial research, teams need to agree who checks the work and how analysts will continue developing their judgment.
I joked that technology had been promising me spare time since I was a boy, yet I still haven't made it to the cinema on a Wednesday afternoon. Julia's answer was to look beyond hours saved and ask whether the team identified a risk earlier or spotted an opportunity it might have missed. I'd love to hear how you measure this in your own work. Has AI helped your team make a better decision, and what evidence persuaded you? Please share your thoughts. - How much time passes between discovering a vulnerability and getting the right person to fix it? On Tech Talks Daily, I'm joined by Vineet Edupuganti, co-founder and CEO of Cogent Security, to talk about the work that takes place after a scanner finds a problem.
Vineet describes it as an assembly line: someone has to find the affected systems, work out where they're exposed, identify the owner, and get the fix completed. Each handoff gives a ticket somewhere to get stuck.
One of the simplest examples Vineet gives is a vulnerability sent to the wrong person. The agent may have identified a real problem, but the recipient can't act on it. The ticket goes back and forth while the system stays exposed. We talk about how Cogent brings together security and operational data to help agents determine who owns what, and why the quality of those records affects what you can ask an agent to do.
We also discuss what Vineet calls governed autonomy. He describes customers setting their own boundaries and starting in environments where the consequences of a mistake are easier to contain. A development system and a customer-facing production service may need different permissions. He makes the case for auditable actions and limits on what an agent can change. I ask where analysts still need to be involved, especially when a fix could interrupt the business or when someone has to weigh a security risk against the cost of downtime.
For anyone considering another security tool, Vineet suggests looking at measures such as time to remediate and how often teams fix issues within their agreed deadlines. We also discuss the trade-off between a broader platform and a specialist tool that may do one job better.
I'd love to hear what you're seeing in your own organization. Which handoff would you trust an agent to handle today, and where would you still want a person to make the call? Please share your thoughts.
Más podcasts de Noticias
Podcasts a la moda de Noticias
Acerca de Tech Talks Daily
If every company is now a tech company and digital transformation is a journey rather than a destination, how do you keep up with the relentless pace of technological change?
Every day, Tech Talks Daily brings you insights from the brightest minds in tech, business, and innovation, breaking down complex ideas into clear, actionable takeaways.
Hosted by Neil C. Hughes, Tech Talks Daily explores how emerging technologies such as AI, cybersecurity, cloud computing, fintech, quantum computing, Web3, and more are shaping industries and solving real-world challenges in modern businesses.
Through candid conversations with industry leaders, CEOs, Fortune 500 executives, startup founders, and even the occasional celebrity, Tech Talks Daily uncovers the trends driving digital transformation and the strategies behind successful tech adoption. But this isn't just about buzzwords.
We go beyond the hype to demystify the biggest tech trends and determine their real-world impact. From cybersecurity and blockchain to AI sovereignty, robotics, and post-quantum cryptography, we explore the measurable difference these innovations can make.
Whether improving security, enhancing customer experiences, or driving business growth, we also investigate the ROI of cutting-edge tech projects, asking the tough questions about what works, what doesn't, and how businesses can maximize their investments.
Whether you're a business leader, IT professional, or simply curious about technology's role in our lives, you'll find engaging discussions that challenge perspectives, share diverse viewpoints, and spark new ideas.
New episodes are released daily, 365 days a year, breaking down complex ideas into clear, actionable takeaways around technology and the future of business.
Sitio web del podcastEscucha Tech Talks Daily, Más de uno y muchos más podcasts de todo el mundo con la aplicación de radio.es

Descarga la app gratuita: radio.es
- Añadir radios y podcasts a favoritos
- Transmisión por Wi-Fi y Bluetooth
- Carplay & Android Auto compatible
- Muchas otras funciones de la app
Tech Talks Daily: Podcasts del grupo






































