A client had ten thousand messy biographical records that needed to become a clean knowledge graph. GPT-4o would have done it and cost a fortune, so I used GliNER2 instead: schema-driven extraction that runs on a CPU.
A WooCommerce recommendation engine scored 0.85 AUC in staging and fell apart on launch day because the live audience did not match the training data. Inverse probability weighting is how I got an honest read on what the model was really doing.
A client’s hourly sales model lost its accuracy every night at midnight because it read 23:00 and 00:00 as far apart. Sine and cosine encoding puts the hours back on a circle, which is where they belong.
A client bought a 64-core Threadripper and their script still ran on one core for an hour. Ray brought it down to about two minutes, with less code than the multiprocessing version I tried first.
A client’s research pipeline kept hallucinating specs until we stopped writing one giant prompt. Notes on using IntelliNode’s VibeFlow to compile intent into a task graph, plus the code we run in production.
Predicting lead conversion from 800 WooCommerce rows, where XGBoost just memorized the noise. Why TabPFN and in-context learning made a better baseline than another afternoon of hyperparameter tuning.
I spent hours refining a mega-prompt and still got different output every session. Here is why that logic moved into a custom AI assistant, how the MATCH framework structures one, and when a private local session is the better call.
A client’s detector found the gearboxes and ignored the bolts, and the problem was the loss function rather than the dataset. Here is how the YOLOv1 loss splits into five terms, why width and height get a square root, and what the lambdas are for.
A friend’s AI resume draft claimed an Azure certification he never had. Three hours of prompt tweaking did not stop it, but indexing his verified work history did, and a grounded mini model beat an ungrounded larger one.
A client’s weekend-built AI agent fell apart the moment real users touched it. Here is what the NeMo Agent Toolkit handled for us that my own custom wrapper could not: YAML config, grounded tools, and a server you get for free.