We Built It. Then We Bought It.
Sometimes good engineering means walking away from something you built well. A real-world build-versus-buy story about evidence, sunk cost, engineering judgment, and knowing when simpler is better.
Sometimes good engineering means walking away from something you built well. A real-world build-versus-buy story about evidence, sunk cost, engineering judgment, and knowing when simpler is better.
by Brian Pollack BC, Alberta, and Manitoba gave the clock change the most polite Canadian middle finger. On Nov 1, many of their computers fall back anyway. The Rules Changed Faster Than the Systems Here's why. NTP, which keeps computer clocks in sync, only knows UTC, not time
What happens to our work after we leave? Scheduled blogs, documents, automations, and processes can keep our presence alive long after we've moved on.
AI applications can fail even when the model works perfectly. Real production failures show why timeouts, monitoring, logging, performance, and ordinary software engineering still matter.
by Brian Pollack I feel like it's inevitable that I will get hacked. Citizen Lab just proved spyware can arrive through an online ad without a single click. An Israeli company posing as an ad firm let spyware vendors aim ads at specific people. At least 45 computers
Pulling line items out of supplier invoices and work orders is the most requested AI job we see. We built it three different ways. Here's what each one wins, what each one costs, and how to tell which is yours.
A clever AI search architecture worked exactly as designed - until newer capabilities made it unnecessary. A real-world lesson in how yesterday’s expertise can become today’s complexity.
by Brian Pollack It's all over the news: no more Adobe licenses needed. This is much bigger news than "Claude, make me ph0tosh0p." The truth is wild and the repercussions will be extensive. When Expensive Software Is No Longer Irreplaceable The claim is simple: open source
AI may not have forgotten your instructions. They may be stored in the wrong place. Why persistent project rules need more than a conversation to survive.
When an AI agent gives the wrong answer, the model may not be the problem. A real debugging story shows why developers should check what the model actually received before rewriting the prompt.
The blog about "The Save Button That Doesn't" missed its own scheduled publish date. You can't make this stuff up.
by Brian Pollack If you needed to build a wall, would you hire a young go-getter with lots of energy and muscles or a wise mason with 30 years of experience? Honestly, you need both. Tech teams especially need a mix of senior developers and leads who have seen all