<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on myvirtualcloud.net</title><link>https://myvirtualcloud.net/tags/ai/</link><description>Recent content in Ai on myvirtualcloud.net</description><generator>Hugo</generator><language>en-us</language><copyright>Andre Leibovici</copyright><lastBuildDate>Mon, 07 Sep 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://myvirtualcloud.net/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>The Answer Was Already in Teams. We Just Couldn't Find It.</title><link>https://myvirtualcloud.net/the-answer-was-already-in-teams-we-just-couldnt-find-it/</link><pubDate>Mon, 07 Sep 2026 09:00:00 +0000</pubDate><guid>https://myvirtualcloud.net/the-answer-was-already-in-teams-we-just-couldnt-find-it/</guid><description>&lt;p&gt;Somewhere in your company&amp;#39;s chat history is the exact fix for the problem you are debugging right now. Someone wrote it down two years ago, in a thread, at 11pm. Good luck finding it.&lt;/p&gt;&#10;&lt;p&gt;That was the problem I set out to solve at ASI Solutions. Our knowledge was not missing. It was scattered. Decisions lived in Microsoft Teams. Delivery history lived in Linear. Deal context lived in HubSpot. Documents lived in SharePoint. Meeting notes lived in Granola. Proposals lived in PandaDoc. Invoices lived in Xero. Code and pull requests lived in GitHub.&lt;/p&gt;</description></item><item><title>How our document classifier votes before it ever asks a language model</title><link>https://myvirtualcloud.net/how-our-document-classifier-votes-before-it-ever-asks-a-language-model/</link><pubDate>Thu, 11 Jun 2026 09:00:00 +1200</pubDate><guid>https://myvirtualcloud.net/how-our-document-classifier-votes-before-it-ever-asks-a-language-model/</guid><description>&lt;p&gt;A district council we work with has about 4 TB of files in SharePoint and more on internal SMB shares, and they need to know what is in them: which documents are contracts, which hold personal information, and which should have been disposed of years ago under the Public Records Act 2005. Every one of those files has to be read, classified into one of roughly 30 document types, and scored for sensitivity.&lt;/p&gt;</description></item><item><title>How I Built ASI's Marketing Engine Around AI Agents</title><link>https://myvirtualcloud.net/how-i-built-asis-marketing-engine-around-ai-agents/</link><pubDate>Mon, 11 May 2026 09:00:00 +0000</pubDate><guid>https://myvirtualcloud.net/how-i-built-asis-marketing-engine-around-ai-agents/</guid><description>&lt;p&gt;This is a long one, and I mean that as a recommendation rather than a warning. Most of what gets written about AI in marketing right now skips the part that actually matters — the specifics: what broke, what surprised you, what you'd do differently. This piece doesn't skip it. If you're building something similar, or wondering whether any of this is real, I think you'll find it useful.&lt;/p&gt;</description></item><item><title>From XGBoost to LightGBM: How Our ML Model Adapted to Two Market Regimes</title><link>https://myvirtualcloud.net/from-xgboost-to-lightgbm-how-our-ml-model-adapted-to-two-market-regimes/</link><pubDate>Sun, 19 Apr 2026 09:00:00 +0000</pubDate><guid>https://myvirtualcloud.net/from-xgboost-to-lightgbm-how-our-ml-model-adapted-to-two-market-regimes/</guid><description>&lt;p&gt;When we first wrote about SignalScope's ML backtesting pipeline in March, the model of record was XGBoost. Six weeks and hundreds of experiments later, it isn't. The current production model is a single LightGBM regressor with forty trees and depth two, trained on three-day forward returns, pulling almost all of its out-of-sample skill from a single feature. Mean information coefficient — the rank correlation between how the model ranks tickers and how they actually perform, where 0 is random and higher is better — has climbed from 0.006 on our first Ridge baseline to 0.161 today, a roughly 27x improvement. But the path between those two numbers wasn't monotonic. Twice in the last six weeks, a regime shift in the underlying data quietly invalidated our best model and forced us to start over. This is the story of how we rebuilt the pipeline three times — and what those rebuilds taught us about model stewardship in markets that keep changing underneath you.&lt;/p&gt;</description></item><item><title>Announcing the Ollama GPU Calculator</title><link>https://myvirtualcloud.net/announcing-the-ollama-gpu-calculator/</link><pubDate>Mon, 28 Oct 2024 05:37:02 +0000</pubDate><guid>https://myvirtualcloud.net/announcing-the-ollama-gpu-calculator/</guid><description>&lt;p&gt;If you have spent any time running local models with Ollama, you already know the awkward part: picking a model is easy; knowing whether your GPU can actually host it is not. Parameter count, quantization, context length, and VRAM interact in ways that are hard to eyeball — especially once you start mixing cards or looking at Apple Silicon unified memory.&lt;/p&gt;</description></item><item><title>Four Advantages of Capacity Forecasting and Analytics with Hyperconvergence</title><link>https://myvirtualcloud.net/four-advantages-of-capacity-forecasting-and-analytics-with-hyperconvergence/</link><pubDate>Tue, 14 Jun 2016 07:15:32 +0000</pubDate><guid>https://myvirtualcloud.net/four-advantages-of-capacity-forecasting-and-analytics-with-hyperconvergence/</guid><description>&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-8075 size-full" style="border: 0px;" src="https://myvirtualcloud.net/wp-content/uploads/2016/06/Screen-Shot-2016-06-13-at-4.57.53-PM.jpg" width="807" height="499" /&gt;&lt;/p&gt;&#10;&lt;p&gt;…read the full article at CIOReview Magazine &lt;a href="http://www.cioreview.com/cxoinsight/four-advantages-of-capacity-forecasting-and-analytics-with-hyperconvergence-nid-14972-cid-89.html" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&#10;&lt;p&gt;This article was first published by Andre Leibovici (@andreleibovici) at myvirtualcloud.net&lt;/p&gt;</description></item></channel></rss>