Aldo Sarmiento

Number Porting, or f*****g up a customers business as it��s also known, is a massive problem in our industry. From “typo’s” on post codes to last minute desperate save attempts, it’s all a bit much isn’t it. Especially for the customer who relies on that number for their customers to speak to them and to help generate and sustain revenue. I understand that nobody likes to lose a customer, but, if you’ve not done your best throughout or your solution no longer fits, move on. Off-boarding a customer is equally as important as onboarding. They may come back, they may change their requirements in a few years. The industry needs to smarten up, in my experience it’s mostly the bigger players who are at fault. What’s your experience?

11

5 Comments

I pushed some exciting example applications to the Live Assist SDK repository to help developers build more interactive, voice-first applications. - Voice agent for Food Ordering, given the PDF / Image of food menu with prices - Kids / Parents assist to find key moments (video demo) Deployment is flexible: Local: - Fully containerized Docker setup. - Link: https://lnkd.in/gBJDzenJ Cloud - Instant integration via the Whissle hosted API. - Link: https://lnkd.in/gqeHGiya #Javascript #EmotionalAI #NoLLM #MetaAware #OpenSource #Cloud #VoiceAI

32

"The best companies don't have customers, they have hostages." Are you really going to vibe code audit logging, SSO, SCIM provisioning, fine grain authorization, nested soft deletions and restorations, and so much more? So I decided to put that to the test. When Retool told me that SCIM required me to upgarde to the enterprise plan, effectively doubling our bill to $50k / year, well, that was the final straw. I vibe coded a replacement in #fsharp with a fully functioning audit log, fine grain permissions, and SSO/SCIM - in a week. Couple reflections: 1. #fsharp is *insanely* good for LLMs - ultra strong guard rails meant #codex could go for a super long time and verify the behavior was correct 2. FSharp is also absurdly token efficient - the whole project cost ~$400, and my rough estimate is that CSharp would have increased the cost by 50% https://lnkd.in/gEEiK3ZU 3. The *only* bugs I ran into were ticky tacky bugs on the frontend. The backend (with test coverage) was basically one shotted.

33

4 Comments

Overnight, Claude hit #1 on the App Store. Yes, politics is playing a role right now. But real talk... Claude is genuinely the better product. Opus 4.6 is #1 on every major benchmark. Claude Code is the most widely adopted coding agent in the industry. Projects and Skills let you build persistent AI workspaces that actually know your business. MCP integrations mean Claude reads and writes to your real tools - Airtable, Google Calendar, Gmail, Drive. Cowork just dropped for teams with plugins and parallel agents. It's not a chatbot. It's an operating system. The politics accelerated the timeline. But the product was already winning. I left Google and built my entire consulting and training business on Claude - workshop outlines, proposals, pipeline, client delivery, content, daily ops, agents. Nothing else comes close for complex, real work. Dario Amodei was VP of Research at OpenAI. He led the teams that built GPT-2 and GPT-3. Co-invented the training technique that made ChatGPT possible. Then left because he wanted to build AI differently - safety-first, no ads, no surveillance. If you've been on the fence about switching, now is the time.

9

There's a disconnect that shows up in almost every team we talk to. IT Directors see upgrades as: schedule it, execute it, move on. DBAs see upgrades as: test it in staging (which doesn't match production), identify every dependency that could break, build a rollback plan for the 15 things that might go wrong, coordinate with 3 other teams, execute during a window that's too short, and then monitor for 48 hours hoping nothing surfaces. Neither side is wrong. They're just seeing different parts of the same elephant. The teams that handle upgrades well aren't the ones with the best DBAs or the best IT Directors. They're the ones where both sides have the same visibility into what's happening, what's at risk, and what the fallback is. When was the last time your DBA and IT Director sat down and mapped out an upgrade end-to-end together?

14

1 Comment