Tech Talks Daily

How do you introduce electric vehicles and AI-assisted safety technology into a collection fleet that customers depend on every day?
On Tech Talks Daily, I'm joined by Brett Rogers, Vice President of Operations Technology at Republic Services, to discuss the engineering, infrastructure, and human decisions behind modern waste and recycling operations. Brett's background includes work at Toyota, General Motors, and Cruise. He describes arriving from the automotive sector and discovering how much complexity sits behind a service most people expect to happen without thinking about it.
We give particular attention to electric refuse trucks. Range is part of the calculation, but the vehicle also powers equipment that lifts containers and handles material. Brett explains how Republic Services models energy use across the chassis and collection body, taking account of terrain, climate, speed, and the work required on a route. The goal is to identify where an electric vehicle can replace a conventional truck while maintaining service.
Route selection can produce some surprising answers. A residential truck making frequent stops may benefit from regenerative braking, while a vehicle with fewer container lifts can spend much of its day covering distance. Brett describes why his team began with residential applications, then used operational data to inform expansion into other vehicle types. The number of lifts alone does not tell the whole story.
Charging has its own planning cycle. Brett says utility discussions, design, and construction can require decisions roughly two years before trucks are needed. We discuss why depot readiness has to lead vehicle delivery, alongside the arrangements that keep service running if power is interrupted. He describes spare vehicles and equipment that can accept emergency power, while on-site storage and renewable energy form part of the options being considered. These approaches have different levels of maturity, and the conversation keeps that distinction clear.
Technology-enabled safety is the other major focus. Brett describes adding a bird's-eye camera view to help drivers see around large vehicles, then working with vendors on systems that distinguish people from objects. Spoken alerts such as "pedestrian rear" are intended to tell a driver what is happening and where, without requiring them to keep checking another screen.
The discussion goes beyond installing cameras. Brett says in-cab alerts were associated with an initial reduction of around 20% to 30% in what Republic Services calls unfocused behaviors. He reports a reduction of 95% after coaching was added to the approach. These are company-reported behavioral measures, not a claim that collisions fell by 95%. No evaluation period or underlying methodology is provided in the interview. The useful operational lesson is the connection between technology, explanation, and the opportunity for drivers to correct a recurring behavior.
We also discuss employee adoption. Brett recalls drivers who were initially reluctant to move from diesel trucks and describes how time in the electric vehicles changed their view. He points to lower noise, vibration, and heat, alongside cab design. His account is a reminder that the experience of the person doing the job can determine whether a promising deployment becomes a useful everyday tool.
We finish with routing visibility for municipal customers and plans to use AI and other tools to improve operations. For fleet leaders, the conversation offers practical considerations around duty cycles, charging resilience, driver support, and measuring results. For everyone else, it reveals the work behind a truck arriving on the right street at the right time.
I'd welcome your thoughts. What would give you the most confidence in an electric fleet rollout, and how should organizations demonstrate that their safety technology is helping drivers and communities?

What would make you comfortable giving an AI agent the authority to act inside a live business process?
In this episode of Tech Talks Daily, I speak with Valerie Henderson, CEO of Caylent, about what has to happen between a successful demonstration and a system a business can depend on. The conversation centers on production readiness, including access controls, spending limits, traceability, workflow design, and the people responsible for the outcome.
Valerie describes why introducing agents requires changes to how work gets done. If an organization adds new technology without reconsidering the handoffs and decisions around it, the hoped-for productivity gains can remain difficult to achieve. Her advice is to begin with a bounded problem where automating a few steps could provide a clear benefit, then build on the evidence rather than starting with an ambitious network of agents.
We discuss the difference between read-only workloads and agents that can alter live systems. Valerie says many customers are already comfortable with agents retrieving information, while autonomous operations such as self-healing infrastructure are concentrated among the most advanced customers she sees. Those observations reflect her experience with Caylent engagements. They do not establish a universal level of enterprise adoption.
For me, one of the most useful questions is what meaningful human oversight looks like. Valerie is clear that people remain accountable for the instructions and access they give agents. She emphasizes deliberate testing, appropriate governance, and the ability to understand what a system has done. We also discuss how agents can repeat work without producing anything useful, creating a bill that needs to be considered alongside accuracy and reliability.
The conversation moves into Caylent's own operating model. Valerie describes moving away from assumptions built around human time and materials, making existing technical knowledge easier to reuse, and changing delivery incentives to reward speed and customer satisfaction. It is a practical reminder that organizations adopting AI may need to reconsider what they reward as well as which tools they buy.
She also shares a customer example involving Smarsh. According to Valerie, redesigning its software delivery process with agentic AI freed engineering capacity that could be reinvested in the business. She describes that capacity in financial terms, but the interview does not establish a measurement period or separate capacity value from realized cash savings. The useful lesson is the connection between a defined objective and a decision about how to use the resulting capacity.
We touch on Caylent's agentic AI readiness research, while keeping the broader discussion focused on practical experience. The useful question for leaders is what controls and evidence should come before greater autonomy, and how they will reassess that decision as the system changes.
Finally, Valerie explains how she thinks about success for employees as well as customers. She wants technologists to have time for difficult problems and opportunities to develop their skills. She also argues that customers should be able to explain the value of the work they have undertaken. Model performance is part of that assessment, alongside the environment, permissions, costs, and business process in which the agent operates.
I would love to hear how your team is making these decisions, so please share your thoughts. Which responsibilities are you ready to delegate to an AI agent, and what evidence would you need before going further?

Useful Links
Caylent website: https://caylent.com/

Caylent's Agentic AI Readiness survey report: https://caylent.com/blog/agentic-engineering-survey-report

What makes an AI fall alert useful to the person who needs help and the team responsible for responding?
In this episode of Tech Talks Daily, I speak with Mike Link, chief operating officer at KamiVision, about deploying computer vision in residential care. We discuss the connection between the sensor, the people receiving its notifications, and the decisions that follow. The conversation also looks at privacy, connectivity, false alarms, and why a system that works in a care facility needs further work before it can serve a wide range of homes.
Mike describes KamiVision's path from home-security cameras to its KamiCare platform. His account of fall detection involves three stages. A device identifies a possible event, a cloud model filters notifications, and a person reviews a blurred, encrypted clip before an alert reaches the user. The human review is part of the service he describes, so it belongs in any discussion of how the system performs.
I ask about the company's 99.5% accuracy claim and what buyers should understand before relying on a number like that. Mike explains the filtering process, but the interview does not establish a test population, a missed-event rate, or a complete statistical definition. His answer is a starting point for further questions about performance across the whole service, rather than proof that a device detects 99.5% of all falls by itself.
One of the most useful examples concerns a resident found on the floor. Mike describes how reviewing an event can help staff understand whether someone fell or deliberately lowered themselves because they needed help with a task. That information may lead to a change in a routine or room layout. It is an example of how visual context can inform care, rather than an independently measured claim that the technology prevents injuries.
We also discuss the difference between a managed care setting and a home. A residential facility can have relatively consistent room layouts and lighting. Homes introduce furniture, pets, several rooms, and areas outside a sensor's view. Mike talks about investigating other sensing technologies to address those gaps. He presents those ideas as work under consideration, not a set of generally available capabilities.
Connectivity is another practical issue. Mike says the version discussed uses Wi-Fi and that a cellular option has been considered. He also explains that the consumer version was being tested with families and was not yet available to purchase at the time of recording. That distinction between an established care-facility offering and a product still being developed matters when assessing where the technology can be used today.
Privacy and consent are part of deployment. Mike says facilities obtain consent from residents or an appropriate representative, and he describes the service as focused on event clips rather than live viewing into a room. Those explanations help frame the conversation a buyer should have about access, retention, review, and the information people are agreeing to share.
Finally, we discuss the business case. Mike connects the value of event information with staff response, communication with families, and adjustments to care. He also describes possible reporting and risk-identification capabilities that had not been deployed. The interview offers a view of the operational questions involved, without establishing a controlled clinical result or a fully quantified return on investment.
I would love to hear your thoughts, so please share your experiences. How should care providers assess whether an AI alert improves the work people do, while respecting the privacy and choices of those receiving care?

What can a crypto exchange's proof of reserves establish, and what might still be missing from the picture?
On Tech Talks Daily, I'm joined by Harvey Liu, co-founder and CEO of LeveX, to discuss transparency, platform engineering, and the responsibilities that come with operating a centralized exchange. Harvey brings a computer science background, an MBA, and experience in venture capital. Our conversation looks at how becoming a founder changed the questions he asks about growth, spending, product delivery, and customer assets.
We begin with the community idea behind LeveX. Harvey recalls meeting other crypto investors and wanting an online environment where people could discuss ideas alongside trading. He describes that as part of the motivation for building the company. The interview also makes clear that some social features remain in development or are planned for a later release. A community vision and a finished product roadmap are different things, and the discussion gives listeners a view of that work in progress.
The central technology question is proof of reserves. Harvey explains why a snapshot should be considered in context, including its date, the assets it contains, and the liabilities it may not reveal. He discusses the limitations of relying on a platform's own token and the difficulty of understanding obligations outside the information shown. Publishing reserve information can contribute evidence, but the conversation does not establish that a snapshot alone proves a business is solvent or that customer assets are protected under every condition.
We also discuss the engineering approach Harvey says LeveX uses. He describes Merkle-tree verification, user account inclusion, and separating parts of the reporting process from the live trading environment. The challenge is to provide useful information while managing privacy and system load. His explanation is a founder's account of the architecture, rather than an independent technical audit or a live demonstration.
From there, the conversation turns to the realities of building the business. Harvey says he underestimated how much product development investment would be needed to compete with larger teams. He also describes the difference between taking a minority investment position and being responsible for the operation itself. Cash flow, customer growth, infrastructure decisions, and the consequences of a failure become immediate concerns rather than topics for a periodic review.
Security and AI bring further tradeoffs. Harvey describes security reviews, operational controls, and the ability to suspend certain functions if something appears wrong. He also discusses AI-assisted development and analysis, alongside agents being built to help with order placement. These ideas raise questions about access, authorization, accuracy, and responsibility. The interview does not demonstrate those systems or establish that AI-generated analysis improves trading results.
Availability is another part of the discussion. Harvey says LeveX restricts access from jurisdictions including the United States, the United Kingdom, Singapore, and mainland China. He describes licensing work as being in progress, rather than announcing completed authorizations. This episode examines a technology business and its founder's decisions. It does not recommend opening an account or imply the service is available in every listener's location.
We close with Harvey's views on decentralized exchanges and plans for additional social features, competitions, and copy trading. These remain company plans as described at recording, without a verified delivery schedule or a promise of financial returns. For listeners interested in platform design and founder accountability, the useful thread is how to question evidence, distinguish current operations from future ambitions, and assess what a company is actually claiming.
Please share your thoughts. What should exchanges make easier to understand about their reserves, liabilities, and operating controls so people can assess their claims with greater clarity?

What needs to happen before an IT team can trust an AI agent to resolve a problem rather than simply report it?
In this episode of Tech Talks Daily, I welcome Jed Ayres, CEO of ControlUp, and Gadi Feldman, Chief Product Officer, to discuss autonomous endpoint management and the practical work behind it. We begin with a familiar problem for enterprise IT teams, plenty of monitoring data and recurring issues that still require investigation, ticket transfers and manual intervention. Jed explains why the aim is to follow an operational problem through to an authorized action and then verify that the issue has been resolved.
Gadi describes how specialist agents could bring together expertise across areas such as endpoint management, networking and storage. We discuss the connections those agents need to existing tools and why an understanding of the technology is only part of the job. Agents also need access to company procedures, priorities and knowledge, much as a new member of an IT team needs to learn how the organization works. Gadi explains how configurable human approval and other controls form part of that approach, with teams able to begin with analysis and recommendations before allowing additional actions.
Jed shares a CHRISTUS Health example involving an audio driver issue across approximately 900 devices, illustrating the value of seeing a common pattern rather than treating every device as a separate support problem. We also discuss what a useful business case should measure. Alongside the time spent by IT, leaders need to consider the employee's experience of waiting for help or finding a workaround. Device performance and software usage can also inform decisions about equipment replacement and unused licenses.
The conversation considers what becomes possible when repetitive work takes less of the team's time, while acknowledging the need to establish trust and define the limits of autonomy. For leaders looking for a starting point, Jed describes ControlUp's seven-day challenge, and Gadi recommends understanding the fleet already in place. Which recurring IT problem would you address first, and what evidence would convince your team that automation was helping? Please share your thoughts with me.