Frictionless Experience

-

Lost in Translation: Now With More AI

Setting: Conference room. Morning. Coffee cups. One says “Disruptor.” The executive has just returned from a tech conference. The architect has just returned from debugging a production issue involving a single missing comma.

🎬 Scene 1: The Grand Vision

Executive: "Hey! Quick sync. Big idea. We’re going AI-first."

Architect: "Okay. What does that mean?"

Executive: "It means we start with AI. You know—intelligent by default."

Architect: "Like personalization? Recommendations? Chatbot support?"

Executive: "Yes, yes, and yes. But simple. Frictionless. Invisible AI."

Architect: "So... AI that does everything but nobody notices?"

Executive: "Exactly! Like Netflix meets ChatGPT, but for our business."

🎬 Scene 2: Vibes-Based Strategy

Architect: "Do you have a specific user flow in mind?"

Executive: "Not exactly. It just needs to feel inevitable."

Architect: "Inevitable like predictive UX? Or like AI apocalypse?"

Executive: "Like... it just works. The user doesn’t click, they glide."

🎬 Scene 3: Target Audience (Maybe?)

Architect: "Who’s the experience for?"

Executive: "Our customers."

Architect: "Which ones?"

Executive: "The loyal ones. And the ones we lost. And maybe future customers we haven’t met yet."

🎬 Scene 4: Budget & Magic

Architect: "Okay. Do we have a budget?"

Executive: "We want to be lean. This should mostly be calling an API, right? I heard OpenAI has something for this."

Architect: "They do. None of them do what you’re describing."

Executive: "Well, the AI will figure it out. That’s the point."

Post-Meeting Recap

  • Executive leaves inspired: “We're officially AI-powered.”
  • Architect opens a Confluence doc titled: “Vision Draft – AI-First, Budget-Neutral, Slightly Creepy Platform for Undifferentiated Users.”
  • Kickoff scheduled. No agenda. Pastries promised.

The Moral

Everyone’s aligned—except on what they’re doing, why they’re doing it, how it works, who it’s for, and how much it costs.

In other words: business as usual.

Pro tip: If your AI plan can’t survive a basic question like “what does it do and a hypothosis on how it will provide value to someone?”—you don’t have a strategy. You have a conference buzzword with calendar invites attached.

Comments

Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules ...
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa...
Read more

webxr with Babylonjs, A-frame/Threejs, and Unity

-
I've been working quite extensively on a webxr side project. Originally it was built with a-frame / threejs. You can take a look at it here at Immersive Idea . Recently I relized I was "fighting the framework" more than I was "getting things done". Originally, I chose a-frame because it was essentially a "no code" (well just html markup) way to build scenes. Additionally it's ECS framework was very well documented and easy to use. In an effort to broaden my perspective I started looking at alternatives (Unity with OpenXr, Babylonjs) as I was struggling to keep the pieces working together. This is my (slightly long) recap of my observations. A-Frame A-frame is wonderful...it is well documented, easy to use, and the community is super friendly and helpful. If I simplly wanted to render scenes in webxr with minimal ability to manipulate the environment, I wouldn't even think twice about using it.... Heck I still use it for quick m...
Read more