Technology

𝗧𝗵𝗲 𝗽𝗮𝗿𝗮𝗱𝗼𝘅 𝗼𝗳 𝗺𝗼𝗱𝗲𝗿𝗻 𝗵𝗲𝗮𝗹𝘁𝗵 𝘁𝗲𝗰𝗵: 𝗧𝗵𝗲 𝗺𝗼𝗿𝗲 𝘄𝗲 𝗺𝗼𝗻𝗶𝘁𝗼𝗿, 𝘁𝗵𝗲 𝗺𝗼𝗿𝗲 𝗮𝗻𝘅𝗶𝗼𝘂𝘀 𝘄𝗲 𝗯𝗲𝗰𝗼𝗺𝗲. We track our bodies 24/7. Count every calorie. Measure sleep, HRV, glucose, stress. From Apple Watch. To Oura Ring. To the latest “temple” device. Somewhere along the way, awareness turned into obsession. Here’s the paradox no one talks about: We have the best health-tracking tools in history, and some of the worst health outcomes. Something doesn’t add up. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗲 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘀𝗵𝗼𝘄𝘀 𝗦𝗹𝗲𝗲𝗽 𝘁𝗿𝗮𝗰𝗸𝗶𝗻𝗴 𝗰𝗮𝗻 𝘄𝗼𝗿𝘀𝗲𝗻 𝘀𝗹𝗲𝗲𝗽 Studies on orthosomnia (an obsession with “perfect” sleep metrics) show that people who fixate on sleep scores experience more sleep anxiety, lighter sleep, and poorer recovery—even when objective sleep doesn’t improve. Trying to optimize sleep can literally break it. 𝗛𝗥𝗩 𝗺𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲𝘀 𝘀𝘁𝗿𝗲𝘀𝘀 𝗳𝗼𝗿 𝗺𝗮𝗻𝘆 𝘂𝘀𝗲𝗿𝘀 HRV is a useful trend marker—but daily fluctuations are normal. Research shows that constant HRV checking can heighten health anxiety and perceived stress, especially when users don’t understand variability or context. Ironically, stressing about HRV often lowers HRV. 𝗠𝗼𝗿𝗲 𝗱𝗮𝘁𝗮 ≠ 𝗯𝗲𝘁𝘁𝗲𝗿 𝗵𝗲𝗮𝗹𝘁𝗵 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 Behavioral science research consistently finds that excessive self-monitoring leads to hypervigilance, loss of bodily trust, and decision fatigue. When every sensation becomes a data point, people stop listening to internal cues and start deferring to dashboards. In short: 𝗢𝘃𝗲𝗿-𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗺𝗲𝗻𝘁 𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝘀 𝗮𝘄𝗮𝗿𝗲𝗻𝗲𝘀𝘀 𝘄𝗶𝘁𝗵 𝗮𝗻𝘅𝗶𝗲𝘁𝘆. So what actually creates health? The same fundamentals that worked 5,000 years ago: • Deep, peaceful sleep • Regular sunlight • Real, nourishing food • Daily movement • Time with people you love These don’t need algorithms. They need presence. Use wearables if they serve you—I do, occasionally. But don’t let them become your master. Your life isn’t an algorithm waiting to be optimized. It’s a system meant to be felt, explored, and course-corrected. The best health coach you’ll ever have is already inside you. Trust it.

A milestone in quantum physics — rooted in a student project What began as a student's undergraduate thesis at Caltech — later continued as a graduate student at MIT — has grown into a collaborative experiment between researchers from MIT, Caltech, Harvard, Fermilab, and Google Quantum AI. Using Google’s Sycamore quantum processor, the team simulated traversable wormhole dynamics — a quantum system that behaves analogously to how certain wormholes are predicted to work in theoretical physics. Here’s what they did: Implemented two coupled SYK-like quantum systems on the processor that represent black holes in a holographic model. Sent a quantum state into one system. Applied an effective “negative energy” pulse to make the simulated wormhole traversable. Observed the state emerge on the other side — consistent with quantum teleportation. This wasn’t just classical computer modeling — it ran on real qubits, using 164 two-qubit quantum gates across nine qubits. Why it matters: The results are consistent with the ER=EPR conjecture, which suggests a deep link between quantum entanglement and spacetime geometry. In the holographic picture, patterns of entanglement can be interpreted as wormhole-like “bridges.” This experiment shows how quantum processors can begin to probe aspects of quantum gravity in a laboratory setting, complementing astrophysical observations and theoretical work. While no physical wormhole was created, this is a step toward using quantum computers to explore some of the most fundamental questions in physics. What breakthrough in science excites you most? Share your thoughts below — and let’s discuss how quantum computing is reshaping our understanding of reality. ♻️ Repost to help people in your network. And follow me for more posts like this. CC: thebrighterside

Two strikingly similar headlines surfaced this past week that should make every leader pause: • “Companies Are Pouring Billions Into A.I. It Has Yet to Pay Off.” — New York Times • “Companies Are Pouring Billions Into AI. Here’s Why They’re Not Seeing Returns” — Forbes The NYT points to the human side: employees resist tools they don’t trust. Forbes focuses on the technical side: most AI still can’t understand the context of work. Both are true, and they’re related. When AI lacks context, employees lose trust. It can’t tell the latest doc from last year’s draft. It summarizes a customer conversation but drops the follow-ups buried in the thread. It pulls a response from Slack while ignoring the context in Google Drive. Employees realize it creates more work than it saves, and stop using it. Pilots stall, deployments fade, and projects slide into the “trough of disillusionment" as the NYT describes. Unfortunately, that's the reality for many organizations. At Glean, we work hard to make sure AI understands the enterprise context the way a human does. If a subject matter expert says something, I trust it more. If something’s old, I double-check it. That’s how people think, and it’s how AI should work too. Yet every enterprise has its own documentation culture and quirks, so sometimes we struggle at first. But we persist and co-develop with customers until the system reaches the quality they need. Then we take those learnings to make it work automatically for the next customer. We’ve seen this approach deliver measurable impact for customers: • Booking.com: Glean Agents give teams faster access to customer insights, cutting video production time by 75% and doubling monthly output. • Confluent: Glean’s AI-powered search saves 15,000+ hours/month, boosts support satisfaction by 13%, and cuts ticket investigation time by 10 minutes. • Fortune 100 telecom company: Glean surfaces instant knowledge during support calls, reducing call resolution time by 17 seconds across 800+ agents. • Leading global consultancy: Glean Agents automate RFP workflows, cutting consulting project proposals from 4 weeks to a few hours (97% faster). • Wealthsimple: Glean gives employees instant access to policies and knowledge, driving $1M+ in annual productivity gains. When AI understands the real context of work—across people, tools, and workflows— employees trust it and use it. Instead of falling into the trough of disillusionment, companies climb a slope toward productivity gains and real ROI.

The New York Times profiled a start-up with 28 employees serving nearly 50 million users. That company is us. The traditional startup playbook: raise massive funding, hire hundreds of employees, and worry about profitability "later." But there's another way. Everyone at Gamma could fit in a small restaurant. We're not just surviving—we've been profitable for 15+ consecutive months, with revenue growing month over month, and lifetime negative net burn (we have more money in the bank than we've raised). This isn't an accident. We've deliberately designed our organization to maximize impact per person. Instead of creating specialist silos, we hire versatile generalists who can solve problems across domains. Rather than building management hierarchies, we find player-coaches who both lead and execute. Our team leverages AI tools throughout our workflow - Claude for data analysis, Cursor for coding efficiency, NotebookLM for customer research synthesis. These aren't just productivity hacks; they're force multipliers. Examples: — When our growth PM needed better analytics, he didn't file a ticket with a data team—he built a self-serve system that anyone can use without SQL knowledge. — When our marketing lead needed to understand our customers better, she fed thousands of interactions into an LLM and created actionable personas that now guide our entire strategy. — When our design team needs to test a hypothesis, we create a rapid prototype and show it to our power users. What we're seeing isn't just about "doing more with less." It's about fundamentally changing what's possible per person. The most valuable employees aren't specialists who excel in narrow domains - they're resourceful problem-solvers who continuously expand their capabilities. This approach creates remarkable resilience. Since everyone understands multiple functions, we don't have single points of failure when someone leaves or moves to another project. If you're building today, the question isn't how quickly you can scale headcount … it's how much impact you can create with the smallest possible team. The future belongs to tiny teams of extraordinary people.

You can't patch your way to the future. Picture this: a wide-open road stretching ahead, the left lane marked by familiar potholes, outdated signs, and traffic jams—let’s call that your legacy systems. On the right, a shiny, newly paved lane labeled Industry 4.0, buzzing with autonomous cars, AI-driven signs, and smart sensors optimizing traffic flow. And then, right in the middle, a single Band-Aid stretching feebly across a gaping crack labeled "digital divide," proudly announcing: "Another Dashboard!" Sound familiar? Too often, companies attempt digital transformation by tossing yet another fancy dashboard at deeply embedded, systemic problems. Dashboards are like Band-Aids—they might momentarily cover the crack, providing short-term comfort, but they never truly fix the road beneath. Here's why another dashboard won't save your company from the digital divide: 𝟏. 𝐈𝐧𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧 𝐎𝐯𝐞𝐫𝐥𝐨𝐚𝐝 ≠ 𝐈𝐧𝐬𝐢𝐠𝐡𝐭 Dashboards multiply data visibility, but without meaningful integration and actionable insights, they're just colorful confusion. It's like adding mirrors to your car to avoid potholes—you might see them better, but they're still there. 𝟐. 𝐒𝐮𝐫𝐟𝐚𝐜𝐞-𝐥𝐞𝐯𝐞𝐥 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 𝐅𝐚𝐢𝐥 𝐚𝐭 𝐒𝐜𝐚𝐥𝐞 A Band-Aid might be great for a scraped knee, but it's laughable when bridging a canyon-sized technology gap. True digital transformation requires fundamental changes to business processes, culture, and underlying technology. 𝟑. 𝐘𝐨𝐮'𝐫𝐞 𝐃𝐞𝐥𝐚𝐲𝐢𝐧𝐠 𝐭𝐡𝐞 𝐈𝐧𝐞𝐯𝐢𝐭𝐚𝐛𝐥𝐞 Quick fixes feel good now, but eventually, you'll still need to fix the underlying problems. Industry 4.0 isn't about simply digitizing old processes—it's about completely rethinking how your business operates. So, what's the real fix? Instead of Band-Aids, you need road construction. Invest in infrastructure—robust data architectures, AI-driven analytics, interconnected systems, and (most importantly) organizational alignment around digital goals. This isn't about just observing your problems; it's about solving them. Dashboards have their place—but not as patches. Use them as windows into new opportunities, supported by sturdy, future-proof foundations. 𝐅𝐮𝐥𝐥 𝐀𝐫𝐭𝐢𝐜𝐥𝐞: https://lnkd.in/e7wyDU_B ******************************************* • Visit www.jeffwinterinsights.com for access to all my content and to stay current on Industry 4.0 and other cool tech trends • Ring the 🔔 for notifications!

As organizations increasingly adopt hybrid-cloud architectures, understanding the right path and tools is crucial for professionals aiming to deliver resilient, scalable, and efficient applications. Here’s a Cloud Native roadmap breaking down the skills and tools to master across critical domains. Dive in and explore the ecosystem that powers modern applications! 🔴 𝟭. 𝗟𝗶𝗻𝘂𝘅 𝗙𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀   Linux remains at the heart of cloud-native systems. Get comfortable with terminal commands, bash scripting, and distributions like Ubuntu and Red Hat for a solid start. 🟢 𝟮. 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹𝘀   Protocols like HTTP, SSL, and SSH form the backbone of connectivity. Tools like Wireshark are invaluable for monitoring and securing network traffic. 🔵 𝟯. 𝗖𝗹𝗼𝘂𝗱 𝗦𝗲𝗿𝘃𝗶𝗰𝗲𝘀   The cloud is non-negotiable! Whether AWS, Azure, or Google Cloud, understanding SaaS, PaaS, and IaaS is key to harnessing the cloud's potential. 🟣 𝟰. 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆   Security is foundational in cloud-native environments. Tools like Open Policy Agent and Prisma provide the framework for enforcing policies and securing applications. 🟡 𝟱. 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀 & 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻   Containers revolutionized app deployment! Master Docker, Kubernetes, and service meshes like Istio to orchestrate, scale, and manage applications seamlessly. 🟠 𝟲. 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗖𝗼𝗱𝗲 (𝗜𝗮𝗖)   IaC tools like Terraform, Chef, and Puppet automate infrastructure, ensuring consistency and efficiency across deployments. IaC is a must for scalable cloud-native applications. 🟢 𝟳. 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆   With tools like Prometheus, Grafana, and Elastic Stack, observability gives you the visibility needed to monitor, troubleshoot, and optimize performance in real time. 🔵 𝟴. 𝗖𝗜/𝗖𝗗   Continuous Integration and Delivery streamline deployments. GitLab, Jenkins, and GitOps practices (Argo) enable rapid, reliable application delivery. This roadmap covers essential areas for cloud-native development, from Linux fundamentals to CI/CD and observability. But, the cloud-native landscape is vast and rapidly evolving! Did I miss any critical tools or concepts? Whether it's a tool you swear by or an emerging trend you're excited about, drop it in the comments! 👇

Germans have installed 500,000 balcony solar arrays, or "balkonkraftwerk." Installations has surged thanks to simplified permitting, the ability to buy panels at hardware stores for a few hundred dollars, and renters (not just owners) being able to install the panels. Cumulatively all of the installations account for 200MW of solar. Each system is small -- capped 800 watts, but I like the spirit of individual energy independence and decisions consumers can make to combat climate change and protect their wallets from surging electricity costs. Great example of deploying climate tech for the built world that exists now and makes financial sense. Image via Solar Monkey #realestate #climate

AI is becoming a make-or-break factor for banks. But success will not depend on their ability to offer #AI, but on their competence in integrating it. Let’s take a look.   Banking is forecasted to feel the biggest impact from generative AI among sectors and industries as a percentage of their revenues with the additional value calculated between $200 bn and $340 bn annually (source: McKinsey). But why is the impact so powerful? One of the main reasons is because the abrupt surge of gen AI is exponentially increasing the speed with which #banking is being transformed. That is not to say that the transformation has started with or due to AI. On the contrary: during the past 10 to 15 years banking was already in the middle of transforming from a human-based, relationship-first industry to a more automated and technology-driven business following the #fintech revolution and the ascend of nimbler and more innovative competitors. But AI now does 2 things: —  It brings the transition to a new level, across 3 dimensions: speed, outcome and impact. —  It turbo-charges one of the biggest challenges in modern FS: the combination of AI and data that brings under the same roof two inherently opposing forces: mass and customization. In other words, AI seems to find a credible answer to achieving hyper-personalization. In a recent report Deloitte has provided realistic examples on how this is done across both cost efficiency and income growth: Cost efficiency: —  Workforce acceleration efficiencies across the board: 0–15% of total staff cost —  IT development and maintenance acceleration: 10–20% of IT staff cost —  Improved credit-risk assessment leading to 10-15% savings in impairment charges —  Improved FinCrime/fraud detection reducing litigation/redress charges and fraud losses Income growth: —  Next generation market analysis / predictive trading algorithms: 5–7% uplift on trading income —  Improved customer retention: 1–2% uplift on fees & commissions —  Improved customer acquisition through hyper-personalised marketing: 5-10% uplift from interest income and fees & commissions —  Tailored loan pricing based on credit risk assessment: 2–3% increase on net interest income Despite all the excitement around these estimated benefits, success will not be a walk in the park. It will depend on the banks’ ability to integrate AI in a seamless way into their day-to-day operations. Going forward AI will be re-writing much of the scenarios and use cases of the banking value chain. That doesn’t necessarily mean that they will all be different, but most will certainly be enhanced with impact spanning both across the back-end and the front-end. Given that resources are limited, one of the main challenges will be how to identify the ones to focus on. Factors such as #strategy, potential impact and a match with the existing skillset should be guiding the selection process.   Opinions: my own, Graphic source and use cases: Deloitte

Last week, I described four design patterns for AI agentic workflows that I believe will drive significant progress: Reflection, Tool use, Planning and Multi-agent collaboration. Instead of having an LLM generate its final output directly, an agentic workflow prompts the LLM multiple times, giving it opportunities to build step by step to higher-quality output. Here, I'd like to discuss Reflection. It's relatively quick to implement, and I've seen it lead to surprising performance gains. You may have had the experience of prompting ChatGPT/Claude/Gemini, receiving unsatisfactory output, delivering critical feedback to help the LLM improve its response, and then getting a better response. What if you automate the step of delivering critical feedback, so the model automatically criticizes its own output and improves its response? This is the crux of Reflection. Take the task of asking an LLM to write code. We can prompt it to generate the desired code directly to carry out some task X. Then, we can prompt it to reflect on its own output, perhaps as follows: Here’s code intended for task X: [previously generated code] Check the code carefully for correctness, style, and efficiency, and give constructive criticism for how to improve it. Sometimes this causes the LLM to spot problems and come up with constructive suggestions. Next, we can prompt the LLM with context including (i) the previously generated code and (ii) the constructive feedback, and ask it to use the feedback to rewrite the code. This can lead to a better response. Repeating the criticism/rewrite process might yield further improvements. This self-reflection process allows the LLM to spot gaps and improve its output on a variety of tasks including producing code, writing text, and answering questions. And we can go beyond self-reflection by giving the LLM tools that help evaluate its output; for example, running its code through a few unit tests to check whether it generates correct results on test cases or searching the web to double-check text output. Then it can reflect on any errors it found and come up with ideas for improvement. Further, we can implement Reflection using a multi-agent framework. I've found it convenient to create two agents, one prompted to generate good outputs and the other prompted to give constructive criticism of the first agent's output. The resulting discussion between the two agents leads to improved responses. Reflection is a relatively basic type of agentic workflow, but I've been delighted by how much it improved my applications’ results. If you’re interested in learning more about reflection, I recommend: - Self-Refine: Iterative Refinement with Self-Feedback, by Madaan et al. (2023) - Reflexion: Language Agents with Verbal Reinforcement Learning, by Shinn et al. (2023) - CRITIC: Large Language Models Can Self-Correct with Tool-Interactive Critiquing, by Gou et al. (2024) [Original text: https://lnkd.in/g4bTuWtU ]

Orbiting #methane "speed cameras" are catching #oilandgas companies in the act. Satellite images are so clear it's possible to see methane #emissions at the individual asset level. At least two dozen high-resolution satellites are expected to be in orbit by the end of this year. The images sent back are crystal clear and leave little doubt about WHO is responsible for the leaks. These missions will usher in a new era of climate transparency and will help keep oil and gas companies accountable 👏 For example, the image below is of a methane release observed on 5th Feb near Exxon Mobil's Big Eddy Unit 156 that Exxon initially failed to disclose to state officials. After Bloomberg shared the imagery with Exxon, the company notified state regulators. Exxon blamed the omission on "human error" and said "someone forgot to file a form" 🙄 While fines and enforcement vary, companies increasingly face reputational risks and potential loss of business if their operations are seen as contributing more than peers to the climate crisis. Methane has 86x the warming power of carbon dioxide during its first two decades in the atmosphere. Halting emissions of the greenhouse gas could do more to slow climate change in the near-term than almost any other single measure. Facility-level information on emissions is hugely valuable because it's directly actionable. The methane observations are also exposing flaws in decades-old reporting approaches used by companies and government agencies that have typically underestimated emissions. For example, satellite data published earlier this year shows that in the US, methane emissions from oil and gas operations from 2010-2019 were 70% higher than amounts reported by the Environmental Protection Agency. This year could see a wave of new reports on operator leaks, as new orbitals increase the coverage and frequency of observations. For operators unable to halt their emissions, that may mean a loss of credibility, fees or trouble insuring future projects. Fossil fuel companies are running out of places to hide. #energy #sustainability #energytransition #emissionsreduction