My Weekend Token Utilisation Report #Week 1

A lighthearted confession of how I spent my weekend feeding tokens to my local AI ecosystem instead of doing normal human things.

Takeaway

I spent my weekend tinkering with three open‑source AI tools — OpenWebUI, OpenCode, and OpenDesign — and accidentally built a tiny personal AI studio on my machine.

This is my “Weekend Token Utilisation Report,” because saying “I played with AI toys all weekend” doesn’t sound respectable enough for LinkedIn.

Saturday Morning: OpenWebUI — My AI Café

I started with OpenWebUI, which feels like a cozy café where your local LLM hangs out, waiting for you to ask questions ranging from “Explain quantum physics like Rajinikanth” to “Write me a grocery list.”

What it is

• A local-first AI chat interface

• Works with Ollama, LM Studio, remote APIs

• Supports agents, workflows, RAG, voice, extensions

• Lets you build your own mini AI tools

Why it’s fun

Because it doesn’t judge your prompts.
Ask it nonsense, ask it philosophy, ask it code — it just vibes.

Setup

• Install Ollama

• Install OpenWebUI

• Connect your models

• Start chatting like it’s Yahoo Messenger in 2004

Saturday Afternoon: OpenCode — My Coding Partner Who Never Sleeps

Then came OpenCode, which is basically VS Code after a spiritual awakening.

What it is

• A local AI coding environment

• Chat + code completion + debugging

• Works with local or cloud models

• Clean, distraction-free UI

Why it’s awesome

Because it feels like pair programming with a calm, polite engineer who never says, “Bro, you missed a semicolon.”

Setup

• Install the app

• Connect your model

• Start coding with AI whispering helpful suggestions

Sunday Morning: OpenDesign — The AI Design Studio That Actually Ships Real Output

OpenDesign is NOT an image generator. It’s a local-first design workspace that works with your coding agent to produce real, runnable design artifacts.

What it actually does

OpenDesign helps your AI agent generate:

• Landing pages (HTML/CSS you can deploy)

• Dashboards (responsive, styled layouts)

• Slide decks (HTML or PPTX)

• Social cards (HTML → PNG)

• Short videos (HTML → MP4)

• Design systems (brand styles in Markdown)

Think of it as giving your coding agent a full design department.

Why it’s addictive

Because you ask for a “Stripe-like landing page,” and it gives you real HTML you can host.
Ask for a “dashboard with a dark theme,” and it generates the layout.
Ask for a “slide deck summarizing my weekend token usage,” and it builds the slides.

Setup

• Install OpenDesign

• Connect it to your coding agent (OpenCode, Claude Code, Cursor, Gemini, etc.)

• Start generating real design output

Sunday Afternoon: Making All Three Work Together

This is where the magic happened — the three tools formed a local AI production pipeline.

The Trio

• OpenWebUI → Brainstorming, chatting, planning

• OpenCode → Coding, debugging, refining

• OpenDesign → Turning ideas into real design artifacts

Example workflow

1. Brainstorm landing page ideas in OpenWebUI

2. Build the backend logic in OpenCode

3. Generate the frontend layout in OpenDesign

4. Publish to Blogger/Substack/Hashnode

5. Feel proud of your weekend token utilisation

Why this matters

You’re not “using AI tools.”
You’re running a local AI studio — private, fast, flexible, and subscription-free.

Benefits (The Serious Part of the Naughty Title)

• Privacy — everything runs locally

• Speed — no cloud latency

• Creativity — chat + code + design in one loop

• Control — choose your models, workflows, extensions

• Zero subscription guilt — your wallet is safe

• Token utilisation bragging rights — you earned this

The Twist

“My Weekend Token Utilisation Report” sounds like something you’d present to your CFO.

But really, it’s just me saying:

“I spent my weekend feeding tokens to AI models instead of doing laundry.”

And honestly, I regret nothing.

~Mohan Krishnamurthy

www.leomohan.net 

From LDL & HDL to LLD & HLD: A Project Manager's Guide to Reading Blood Test Reports

Yesterday, during a customer meeting, the discussion unexpectedly moved from project documentation to health checkups.

The customer was reviewing his blood test report and confidently said:

"Doctor says my LLD is high, but HLD is also improving."

For a moment, my project management instincts kicked in.

LLD? Low-Level Design?

HLD? High-Level Design?

Then reality returned. He meant LDL and HDL.

But the accidental terminology crossover sparked an interesting thought: what if we interpreted a blood test report the way IT professionals interpret a project report?

Let's explore.

---

HDL (Good Cholesterol) = HLD (High-Level Design)

Every successful project starts with a strong High-Level Design.

It provides direction, structure, governance, and strategic clarity.

Similarly, HDL (High-Density Lipoprotein) is the "good cholesterol." It helps remove excess cholesterol from the bloodstream and keeps things running smoothly.

Health World	Project World
HDL	HLD
Provides protection	Provides direction
Higher is generally better	Better HLD means fewer surprises
Prevents future problems	Prevents future rework

Conclusion: A project with a solid HLD and a body with healthy HDL are both set up for long-term success.

---

LDL (Bad Cholesterol) = LLD Gone Wrong

Low-Level Design is essential.

However, excessive documentation, over-engineering, and unnecessary complexity can become project cholesterol.

LDL (Low-Density Lipoprotein) tends to accumulate where it shouldn't.

Similarly, poorly controlled LLDs tend to generate:

• Excessive dependencies

• Complicated workflows

• Technical debt

• Endless review meetings

Health World	Project World
High LDL creates blockages	Excessive complexity creates bottlenecks
Restricts flow	Restricts progress
Requires intervention	Requires redesign

Conclusion: Some LDL is necessary. Some LLD is necessary. Too much of either creates operational challenges.

---

Triglycerides = Pending Action Items

Every project has them.

Open tickets.

Pending approvals.

Unresolved risks.

Deferred decisions.

Individually harmless.

Collectively dangerous.

Just as elevated triglycerides indicate excess stored energy, a project overloaded with pending actions stores unfinished work that eventually slows delivery.

---

Blood Pressure = Project Pressure

A little pressure keeps things moving.

Too much pressure causes damage.

In medicine, sustained high blood pressure strains critical systems.

In projects, sustained management pressure leads to:

• Burnout

• Escalations

• Quality issues

• Resignations

Both doctors and project managers should remember:

Pressure is a metric, not a strategy.

---

Hemoglobin = Team Productivity

Hemoglobin carries oxygen.

Productive teams carry projects.

When hemoglobin levels are low, fatigue follows.

When team productivity is low, deadlines begin to drift.

In both cases, management's first reaction is usually the same:

"Let's investigate the root cause."

---

Vitamin D = Stakeholder Support

Everyone ignores it until it becomes a problem.

Projects with inadequate stakeholder support resemble people with Vitamin D deficiency:

• Progress slows

• Morale drops

• Unexpected symptoms appear

• Everyone wonders why things feel difficult

The prescription is remarkably similar:

Get more exposure.

---

HbA1c = Technical Debt Index

HbA1c doesn't tell you what happened yesterday.

It tells you what has been happening for months.

Technical debt behaves exactly the same way.

A project may appear healthy during a sprint review, but accumulated shortcuts eventually show up in architecture assessments just as HbA1c reveals long-term sugar management.

---

ECG = Project Audit

Nobody schedules one because they're excited.

They schedule one because they want assurance that everything is functioning correctly.

The findings are also similar:

• Normal

• Minor observations

• Needs monitoring

• Please come back immediately

---

Final Diagnosis

A healthy professional should monitor:

• HDL

• LDL

• Blood Pressure

• HbA1c

A healthy project should monitor:

• HLD

• LLD

• Team Pressure

• Technical Debt

And if a customer ever tells you that his LLD is high and HLD is improving, don't correct him immediately.

First ask:

"Are we discussing your health report or your project status report?"

Because in today's world, either answer could be correct.

Presenting Without Borders: How I Delivered a Seamless English–Arabic Hybrid Presentation

 

Most presentations are judged by their content, design, or delivery. But occasionally, the true test lies in something deeper: can every person in the room understand you?

When I recently presented to an Arabic-speaking audience, I decided to treat the language barrier not as an obstacle, but as a design challenge. What followed was a surprisingly elegant, fully hybrid workflow that blended Microsoft PowerPoint, Apple’s accessibility features, AI translation, and two smartphones into a single, frictionless experience.

This is the story of how that system came together — and why it worked.

Designing the Foundation: A Presentation Built for Two Languages

The process began in familiar territory: Microsoft PowerPoint. I created the full English deck and then wrote detailed speaker notes for every slide. These notes would become the backbone of the entire multilingual experience.

But instead of relying on human interpreters or last‑minute translation, I took a different route: I fed the speaker notes into an AI translator to generate a clean, modern Arabic script. This gave me a precise, consistent version of my narration — something that human interpreters often struggle to maintain across long presentations.

Turning Text Into Voice: A DIY Arabic Narration Studio

With the Arabic script ready, I moved to my MacBook.

• I pasted the Arabic text into TextEdit.

• I enabled Spoken Content, Apple’s built‑in text‑to‑speech feature.

• I opened QuickTime Player and started a new audio recording.

• Then, with a simple Option + Esc, the Mac began reading the Arabic script aloud.

The result? A clear, natural-sounding Arabic narration — recorded in one continuous flow.

Once exported, I inserted the audio file into PowerPoint and set it to Play Across Slides. Suddenly, my English presentation had a synchronized Arabic voiceover, ready to guide the audience through every idea.

Creating a Live Translation Loop: English ↔ Arabic in Real Time

The real magic happened during the Q&A.

On the right side of my MacBook, I placed my iPhone running Apple Translate. On the left, my Android phone running Google Translate.

This created a two-way translation loop:

• When the audience asked questions in Arabic, Apple Translate instantly converted them into English for me.

• When I responded in English, Google Translate spoke my answer aloud in Arabic.

I simply paused after each English sentence and let the phone “speak” on my behalf. The audience heard their language. I heard mine. And the conversation flowed without a single moment of confusion.

The Outcome: A Room Without Language Barriers

What could have been a fragmented, awkward multilingual session became a smooth, inclusive experience. Every participant — regardless of language — felt heard, understood, and respected.

The setup was simple. The tools were everyday devices. But the impact was profound.

This experience reminded me that technology, when orchestrated thoughtfully, can dissolve barriers that once felt immovable. It can turn a multilingual challenge into a moment of connection. And it can empower a presenter to speak confidently, knowing that every voice in the room can follow along.

~Mohan Krishnamurthy

How Many More Years Will It Take to Tell What’s Real?

 குறள் 423

அறிவுடைமை

எப்பொருள் யார்யார்வாய்க் கேட்பினும் அப்பொருள்
மெய்ப்பொருள் காண்ப தறிவு

It took me 20 years to realize that the “First Day First Show” movie celebrations I grew up admiring weren’t spontaneous fan frenzies at all—they were sponsored spectacles, carefully choreographed by producers, directors, or the hero’s team.

It took me 25 years to understand that search results aren’t arranged by relevance or merit alone. The ones at the top often get there simply because someone paid for the privilege.

It took me 30 years to realize that star ratings, reviews, and feedback on e-commerce platforms—things I once trusted blindly—can be bought in bulk, manufactured overnight, and manipulated at scale.

It took me 35 years to grasp that millions of views, likes, and followers on social media don’t necessarily indicate quality or influence. Many are purchased, automated, or inflated by bots.

It took me 40 years to understand that nearly 98% of the content on the internet is shaped, influenced, or driven by some form of propaganda—pro or anti—aligned with a particular ideology, product, belief, or agenda.

And yet, after all these years of lessons, I still don’t know how many more years it will take for me to fully distinguish reality from fabrication—to quickly identify what’s genuine and what’s engineered… not just in digital spaces, but in real life too.

Because today, truth isn’t just harder to find.
It is harder to recognize.

We live in a world where:

• authenticity can be manufactured,

• trust can be purchased,

• popularity can be simulated,

• opinions can be influenced invisibly, and

• narratives can be seeded at scale.

The lines between organic and orchestrated, real and rehearsed, truth and targeting are blurring faster than we can adapt.

But maybe the answer doesn’t lie in becoming cynical or paranoid.
Maybe it lies in developing a new form of literacy—a reality literacy—where we constantly question, examine, cross-check, and slow down long enough to think before we trust.

I still don’t know how many years it will take me to master that skill.
But acknowledging the problem is perhaps the first honest step toward clarity in an increasingly artificial world.

~ Mohan Krishnamurthy

#Article Collaborator OpenAI ChatGPT

Goodreads

Find my books on:

Goodreads

Latest Release:

Google Opal for Beginners: Learn, Apply, and Benefit: https://books2read.com/u/mZJVJB

Upcoming Release:

Drowning in Digital Defenders: How Too Many Cybersecurity Tools Can Actually Make You Less Safe

 

Image Courtesy: Google Opal

I. Introduction: The Paradox of Protection

Imagine buying 50 different locks for your front door, but each lock comes with its own tiny, unique key that you have to manage separately. Sounds like a nightmare, right? A Sisyphean exercise in security theater, where the act of protecting becomes more burdensome than the potential threat itself.

That's essentially what many enterprises are facing in cybersecurity. They're drowning in a sea of security products, leading to "tool sprawl" or "vendor sprawl." The cybersecurity landscape, once a carefully tended garden, has become an overgrown jungle.

Having too many security tools that don't talk to each other creates more problems than it solves, paradoxically weakening defenses instead of strengthening them. It's a cruel irony: the very instruments designed to safeguard become instruments of our potential downfall.

In this post, we'll dive into why this is happening, what it's costing businesses, and how we can untangle this complex web for a truly secure future. We'll explore the historical trajectory that led us here, the current state of affairs, and, most importantly, a potential roadmap towards a more streamlined and effective security posture.

II. A Walk Down Memory Lane: How We Got Here

To understand the current predicament, we must trace the evolution of cyber threats and the corresponding defensive responses.

• The Early Days (1960s-1980s): Simple Threats, Simple Solutions:

  The digital world, in its nascent stages, was a relatively innocent place. The "Creeper" virus and its "Reaper" antidote represent the primordial soup of cybersecurity. The rise of personal computers and early viruses like "Brain" necessitated the creation of antivirus software. Then came the Morris Worm, a wake-up call highlighting the inherent dangers of interconnected systems. These were simpler times, where the problems, though novel, were manageable with relatively straightforward solutions.

• The Internet Boom (1990s-Early 2000s): New Threats, More Tools:

  The advent of the internet unleashed a Pandora's Box of new threats. Email viruses like Melissa, phishing scams, and Distributed Denial-of-Service (DDoS) attacks became commonplace. Firewalls, once a niche technology, became a necessity. More ominously, organized cybercrime and nation-state attacks emerged, leading to an explosion of specialized tools: antivirus software, intrusion detection systems, firewalls, and a growing alphabet soup of security acronyms.

• The Modern Era (Past Decade): The Attack Surface Explodes & So Does the Toolset:

  In the last decade, the attack surface has expanded exponentially. Advanced Persistent Threats (APTs), ransomware, cloud computing, the Internet of Things (IoT), and mobile devices have created a threat landscape so complex and varied that it's almost unfathomable. Vendors have reacted by creating specialized "point solutions" for every new problem, resulting in organizations juggling anywhere from 45 to hundreds of different security tools. It's a digital arms race with no clear end in sight.

III. The Current Mess: Why More Isn't Always Merrier

• What is "Tool Sprawl"?

  It's when an excessive number of security tools become a detriment, creating complexity, inefficiency, and diminished security. It's the point where the forest of defenses obscures the actual threats lurking within.

• The Alarm Bells Are Ringing:

  Cybersecurity leaders are sounding the alarm. A significant percentage of CISOs are calling for consolidation, recognizing that the fragmented approach is simply not sustainable. Many enterprises use an astonishing number of tools, ranging from 45 to 83, and some even exceeding 100, with retail and financial services organizations being particularly burdened.

  This proliferation also gives rise to what we might term the "CTI Paradox": the more cyber threat intelligence (CTI) data we collect, the less actionable it becomes.

• The Headache-Inducing Causes:

  The causes of this tool sprawl are multifaceted:

  • Chasing the Dragon:The allure of the "latest and greatest" security tool, often purchased without considering its integration with existing systems.
  • Siloed Spending:Departments independently procuring tools, leading to incompatible systems and redundant capabilities.
  • Data Deluge:The sheer volume of data generated by these tools overwhelms security teams, leading to "alert fatigue" and missed threats.
  • IT Complexity:The rise of cloud computing, remote work, and mixed IT/OT environments demands broader coverage, but without proper orchestration, it results in chaos.
  • Human Limits:Security teams are experiencing burnout, stress, and cognitive overload, leading to poor decision-making.
  • No Master Plan:The absence of a clear, risk-based framework for selecting and deploying security tools.
  • Vendor Lock-in:Organizations finding themselves trapped with expensive and cumbersome solutions due to the difficulty of switching.
  • Cybersecurity Skills Shortage:A global shortage of skilled professionals to manage the growing mountain of tools.
  • Regulatory Burden:Compliance demands diverting resources and further complicating the security landscape.

• The Painful Impacts on Your Business:

  • Less Secure, More Vulnerable:Critical threats are lost in the noise, creating exploitable gaps and blind spots. The paradox is complete: more tools, less security.
  • Wallet Drain:Increased operational costs, direct financial losses, higher insurance premiums, and wasted money on redundant tools.
  • Team Burnout:Overwhelmed security analysts chasing false positives, leading to low productivity and high turnover.
  • Slow & Messy Responses:Longer time to detect and resolve incidents (MTTR) due to fragmented systems and lack of coordination.
  • Bad Decisions:Information overload leads to poor judgment and increased errors, such as falling victim to phishing attacks.
  • Shadow IT Nightmare:Unauthorized tools expanding the attack surface.

IV. Controversies & Debates: Is More Really Better?

The central question remains: is more really better when it comes to cybersecurity tools? Or have we reached a point of diminishing returns, where the sheer volume of defenses becomes a liability?

Research suggests that there's a "Security Tool Tipping Point," beyond which adding more tools actually increases risk. Businesses are spending more on cybersecurity, but a concerningly low percentage are confident in their ability to stop sophisticated attacks.

Perhaps we're prioritizing technology over the people and processes that make it work. Are we falling prey to the "Silver Bullet" Myth, believing that simply buying more tools will magically solve all our problems? Or is the industry primarily driven by vendors pushing products, rather than focusing on achieving tangible security outcomes?

V. The Light at the End of the Tunnel: Future Developments & Solutions

• The Push for Consolidation (Platformization!):

  To reduce complexity, cut costs, improve efficiency, and gain a unified view of the security landscape, organizations are increasingly moving towards consolidation. The goal is to transition from a multitude of disparate tools to comprehensive, all-in-one platforms. Major security firms are now offering integrated platforms, providing unified visibility, better integration, cost savings, and faster response times.

• Emerging Tech & Smart Strategies:

  • AI as Your Ally (and Foe!):Artificial intelligence (AI) is emerging as a powerful tool for both offense and defense. AI can enhance real-time threat detection, anomaly analysis, and automated responses, augmenting the capabilities of human security teams.
  • Zero Trust Architecture (ZTA):A fundamental shift in security philosophy, where "never trust, always verify" becomes the guiding principle. Strict access controls and continuous verification are becoming the norm.
  • XDR Technologies:Advanced, AI-powered platforms designed to detect and respond to threats across cloud environments, endpoints, and networks.
  • Beyond the Basics:Multi-factor authentication (MFA), secure communication platforms, and supply chain risk management (SBOMs) are becoming essential components of a robust security posture.
  • Cyber Resilience:Shifting the focus from solely preventing attacks to also ensuring rapid recovery.
  • Skills Gap Solutions:Automation, simpler tools, and continuous training are key to addressing the cybersecurity skills shortage.
  • Quantum Computing:A looming threat that requires proactive crypto-agile solutions.

• The Path Forward: A Proactive Approach

  • Define clear objectives for your security tools.
  • Implement smart filtering and prioritization for alerts.
  • Centralize data management (Security Data Lakes!).
  • Conduct regular security audits and continuous threat exposure management (CTEM).
  • Foster a culture of cybersecurity awareness.
  • Remember: Cybersecurity is a business issue, not just an IT one.

VI. Conclusion: Smarter Security, Not Just More Security

We've seen how the quest for security has inadvertently led to overload, creating new vulnerabilities and overwhelming security teams. The future isn't about amassing more security products; it's about smarter, integrated, and consolidated security.

It's time to declutter your digital defenses, consolidate wisely, and empower your teams to truly protect your enterprise.

Let's stop drowning in tools and start swimming towards a truly secure future. Let us strive for clarity and focus, rather than being blinded by the sheer volume of our defenses. Only then can we hope to navigate the complex and ever-evolving landscape of cybersecurity.

~ Mohan Krishnamurthy

Powered by: Google Opal