Author: lbhuston

Advisory in the AI Age: Navigating the “Consulting Crash”

/ lbhuston / Leave a comment

 

The Erosion of Traditional Advisory Models

The age‑old consulting model—anchored in billable hours and labor‑intensive analysis—is cracking under the weight of AI. Automation of repetitive tasks isn’t horizon‑bound; it’s here. Major firms are bracing:

  • Big Four upheaval — Up to 50% of advisory, audit, and tax roles could vanish in the next few years as AI reshapes margin models and deliverables.
  • McKinsey’s existential shift — AI now enables data analysis and presentation generation in minutes. The firm has restructured around outcome‑based partnerships, with 25% of work tied to tangible business results.
  • “Consulting crash” looming — AI efficiencies combined with contracting policy changes are straining consulting profitability across the board.

ChatGPT Image Aug 11 2025 at 11 41 36 AM

AI‑Infused Advisory: What Real‑World Looks Like

Consulting is no longer just human‑driven—AI is embedded:

  • AI agent swarms — Internal use of thousands of AI agents allows smaller teams to deliver more with less.
  • Generative intelligence at scale — Firm‑specific assistants (knowledge chatbots, slide generators, code copilots) accelerate research, design, and delivery.

Operational AI beats demo AI. The winners aren’t showing prototypes; they’re wiring models into CI/CD, decision flows, controls, and telemetry.

From Billable Hours to Outcome‑Based Value

As AI commoditizes analysis, control shifts to strategic interpretation and execution. That forces a pricing and packaging rethink:

  • Embed, don’t bolt‑on — Architect AI into core processes and guardrails; avoid one‑off reports that age like produce.
  • Price to outcomes — Tie a clear portion of fees to measurable impact: cycle time reduced, error rate dropped, revenue lift captured.
  • Own runbooks — Codify delivery with reference architectures, safety controls, and playbooks clients can operate post‑engagement.

Practical Playbook: Navigating the AI‑Driven Advisory Landscape

  1. Client triage — Segment work into automate (AI‑first), augment (human‑in‑the‑loop), and advise (judgment‑heavy). Push commoditized tasks toward automation; preserve people for interpretation and change‑management.
  2. Infrastructure & readiness audits — Assess data quality, access controls, lineage, model governance, and observability. If the substrate is weak, modernize before strategy.
  3. Outcome‑based offers — Convert packages into fixed‑fee + success components. Define KPIs, timeboxes, and stop‑loss logic up front.
  4. Forward‑Deployed Engineers (FDEs) — Embed build‑capable consultants inside client teams to ship operational AI, not just recommendations.
  5. Lean Rationalism — Apply Lean IT to advisory delivery: remove handoff waste, shorten feedback loops, productize templates, and use automation to erase bureaucratic overhead.

Why This Matters

This isn’t a passing disruption—it’s a structural inflection. Whether you’re solo or running a boutique, the path is clear: dismantle antiquated billing models, anchor on outcomes, and productize AI‑augmented value creation. Otherwise, the market will do the dismantling for you.

Support My Work

Support the creation of high-impact content and research. Sponsorship opportunities are available for specific topics, whitepapers, tools, or advisory insights. Learn more or contribute here: Buy Me A Coffee

References

  1. AI and Trump put consulting firms under pressure — Axios
  2. As AI Comes for Consulting, McKinsey Faces an “Existential” Shift — Wall Street Journal
  3. AI is coming for the Big Four too — Business Insider
  4. Consulting’s AI Transformation — IBM Institute for Business Value
  5. Closing the AI Impact Gap — BCG
  6. Because of AI, Consultants Are Now Expected to Do More — Inc.
  7. AI Transforming the Consulting Industry — Geeky Gadgets

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

 

Building Logic with Language: Using Pseudo Code Prompts to Shape AI Behavior

/ lbhuston / Leave a comment

Introduction

It started as an experiment. Just an idea — could we use pseudo code, written in plain human language, to define tasks for AI platforms in a structured, logical way? Not programming, exactly. Not scripting. But something between instruction and automation. And to my surprise — it worked. At least in early testing, platforms like Claude Sonnet 4 and Perplexity have been responding in consistently usable ways. This post outlines the method I’ve been testing, broken into three sections: Inputs, Task Logic, and Outputs. It’s early, but I think this structure has the potential to evolve into a kind of “prompt language” — a set of building blocks that could power a wide range of rule-based tools and reusable logic trees.

A close up shot reveals code flowing across the hackers computer screen as they work to gain access to the system The code is complex and could take days or weeks for a novice user to understand 9195529

Section 1: Inputs

The first section of any pseudo code prompt needs to make the data sources explicit. In my experiments, that means spelling out exactly where the AI should look — URLs, APIs, or internal data sets. Being explicit in this section has two advantages: it limits hallucination by narrowing the AI’s attention, and it standardizes the process, so results are more repeatable across runs or across different models.

# --- INPUTS ---
Sources:
- DrudgeReport (https://drudgereport.com/)
- MSN News (https://www.msn.com/en-us/news)
- Yahoo News (https://news.yahoo.com/)

Each source is clearly named and linked, making the prompt both readable and machine-parseable by future tools. It’s not just about inputs — it’s about documenting the scope of trust and context for the model.

Section 2: Task Logic

This is the core of the approach: breaking down what we want the AI to do in clear, sequential steps. No heavy syntax. Just numbered logic, indentation for subtasks, and simple conditional statements. Think of it as logic LEGO — modular, stackable, and understandable at a glance.

# --- TASK LOGIC ---
1. Scrape and parse front-page headlines and article URLs from all three sources.
2. For each headline:
   a. Fetch full article text.
   b. Extract named entities, events, dates, and facts using NER and event detection.
3. Deduplicate:
   a. Group similar articles across sources using fuzzy matching or semantic similarity.
   b. Merge shared facts; resolve minor contradictions based on majority or confidence weighting.
4. Prioritize and compress:
   a. Reduce down to significant, non-redundant points that are informational and relevant.
   b. Eliminate clickbait, vague, or purely opinion-based content unless it reflects significant sentiment shift.
5. Rate each item:
   a. Assign sentiment as [Positive | Neutral | Negative].
   b. Assign a probability of truthfulness based on:
      - Agreement between sources
      - Factual consistency
      - Source credibility
      - Known verification via primary sources or expert commentary

What’s emerging here is a flexible grammar of logic. Early tests show that platforms can follow this format surprisingly well — especially when the tasks are clearly modularized. Even more exciting: this structure hints at future libraries of reusable prompt modules — small logic trees that could plug into a larger system.

Section 3: Outputs

The third section defines the structure of the expected output — not just format, but tone, scope, and filters for relevance. This ensures that different models produce consistent, actionable results, even when their internal mechanics differ.

# --- OUTPUT ---
Structured listicle format:
- [Headline or topic summary]
- Detail: [1–2 sentence summary of key point or development]
- Sentiment: [Positive | Neutral | Negative]
- Truth Probability: [XX%]

It’s not about precision so much as direction. The goal is to give the AI a shape to pour its answers into. This also makes post-processing or visualization easier, which I’ve started exploring using Perplexity Labs.

Conclusion

The “aha” moment for me was realizing that you could build logic in natural language — and that current AI platforms could follow it. Not flawlessly, not yet. But well enough to sketch the blueprint of a new kind of rule-based system. If we keep pushing in this direction, we may end up with prompt grammars or libraries — logic that’s easy to write, easy to read, and portable across AI tools.

This is early-phase work, but the possibilities are massive. Whether you’re aiming for decision support, automation, research synthesis, or standardizing AI outputs, pseudo code prompts are a fascinating new tool in the kit. More experiments to come.

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

Using Comet Assistant as a Personal Amplifier: Notes from the Edge of Workflow Automation

/ lbhuston / Leave a comment

Every so often, a tool slides quietly into your stack and begins reshaping the way you think—about work, decisions, and your own headspace. Comet Assistant did exactly that for me. Not with fireworks, but with frictionlessness. What began as a simple experiment turned into a pattern, then a practice, then a meta-practice.

ChatGPT Image Aug 7 2025 at 10 16 18 AM

I didn’t set out to study my usage patterns with Comet. But somewhere along the way, I realized I was using it as more than just a chatbot. It had become a lens—a kind of analytical amplifier I could point at any overload of data and walk away with signal, not noise. The deeper I leaned in, the more strategic it became.

From Research Drain to Strategic Clarity

Let’s start with the obvious: there’s too much information out there. News feeds, trend reports, blog posts—endless and noisy. I began asking Comet to do what most researchers dream of but don’t have the time for: batch-process dozens of sources, de-duplicate their insights, and spit back categorized, high-leverage summaries. I’d feed it a prompt like:

“Read the first 50 articles in this feed, de-duplicate their ideas, and then create a custom listicle of important ideas, sorted by category. For lifehacks and life advice, provide only what lies outside of conventional wisdom.”

The result? Not just summaries, but working blueprints. Idea clusters, trend intersections, and most importantly—filters. Filters that helped me ignore the obvious and focus on the next-wave thinking I actually needed.

The Prompt as Design Artifact

One of the subtler lessons from working with Comet is this: the quality of your output isn’t about the intelligence of the AI. It’s about the specificity of your question. I started writing prompts like they were little design challenges:

  • Prioritize newness over repetition.

  • Organize outputs by actionability, not just topic.

  • Strip out anything that could be found in a high school self-help book.

Over time, the prompts became reusable components. Modular mental tools. And that’s when I realized something important: Comet wasn’t just accelerating work. It was teaching me to think in structures.

Synthesis at the Edge

Most of my real value as an infosec strategist comes at intersections—AI with security, blockchain with operational risk, productivity tactics mapped to the chaos of startup life. Comet became a kind of cognitive fusion reactor. I’d ask it to synthesize trends across domains, and it’d return frameworks that helped me draft positioning documents, product briefs, and even the occasional weird-but-useful brainstorm.

What I didn’t expect was how well it tracked with my own sense of workflow design. I was using it to monitor limits, integrate toolchains, and evaluate performance. I asked it for meta-analysis on how I was using it. That became this very blog post.

The Real ROI: Pattern-Aware Workflows

It’s tempting to think of tools like Comet as assistants. But that sells them short. Comet is more like a co-processor. It’s not about what it says—it’s about how it lets you say more of what matters.

Here’s what I’ve learned matters most:

  • Custom Formatting Matters: Generic summaries don’t move the needle. Structured outputs—by insight type, theme, or actionability—do.

  • Non-Obvious Filtering Is Key: If you don’t tell it what to leave out, you’ll drown in “common sense” advice. Get specific, or get buried.

  • Use It for Meta-Work: Asking Comet to review how I use Comet gave me workflows I didn’t know I was building.

One Last Anecdote

At one point, I gave it this prompt:

“Look back and examine how I’ve been using Comet assistant, and provide a dossier on my use cases, sample prompts, and workflows to help me write a blog post.”

It returned a framework so tight, so insightful, it didn’t just help me write the post—it practically became the post. That kind of recursive utility is rare. That kind of reflection? Even rarer.

Closing Thought

I don’t think of Comet as AI anymore. I think of it as part of my cognitive toolkit. A prosthetic for synthesis. A personal amplifier that turns workflow into insight.

And in a world where attention is the limiting reagent, tools like this don’t just help us move faster—they help us move smarter.

 

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

Getting DeepSeek R1 Running on Your Pi 5 (16 GB) with Open WebUI, RAG, and Pipelines

/ lbhuston / Leave a comment

🚀 Introduction

Running DeepSeek R1 on a Pi 5 with 16 GB RAM feels like taking that same Pi 400 project from my February guide and super‑charging it. With more memory, faster CPU cores, and better headroom, we can use Open WebUI over Ollama, hook in RAG, and even add pipeline automations—all still local, all still low‑cost, all privacy‑first.

PiAI

💡 Why Pi 5 (16 GB)?

Jeremy Morgan and others have largely confirmed what we know: Raspberry Pi 5 with 8 GB or 16 GB is capable of managing the deepseek‑r1:1.5b model smoothly, hitting around 6 tokens/sec and consuming ~3 GB RAM (kevsrobots.com, dev.to).

The extra memory gives breathing room for RAG, pipelines, and more.

🛠️ Prerequisites & Setup

  • OS: Raspberry Pi OS (64‑bit, Bookworm)

  • Hardware: Pi 5, 16 GB RAM, 32 GB+ microSD or SSD, wired or stable Wi‑Fi

  • Tools: Docker, Docker Compose, access to terminal

🧰 System prep

bash
CopyEdit
sudo apt update && sudo apt upgrade -y
sudo apt install curl git

Install Docker & Compose:

bash
CopyEdit
curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker $USER
newgrp docker

Install Ollama (ARM64):

bash
CopyEdit
curl -fsSL https://ollama.com/install.sh | sh
ollama --version

⚙️ Docker Compose: Ollama + Open WebUI

Create the stack folder:

bash
CopyEdit
sudo mkdir -p /opt/stacks/openwebui
cd /opt/stacks/openwebui

Then create docker-compose.yaml:

yaml
CopyEdit
services:
ollama:
image: ghcr.io/ollama/ollama:latest
volumes:
- ollama:/root/.ollama
ports:
- "11434:11434"
open-webui:
image: ghcr.io/open-webui/open-webui:ollama
container_name: open-webui
ports:
- "3000:8080"
volumes:
- openwebui_data:/app/backend/data
restart: unless-stopped

volumes:
ollama:
openwebui_data:

Bring it online:

bash
CopyEdit
docker compose up -d

✅ Ollama runs on port 11434, Open WebUI on 3000.

📥 Installing DeepSeek R1 Model

In terminal:

bash
CopyEdit
ollama pull deepseek-r1:1.5b

In Open WebUI (visit http://<pi-ip>:3000):

  1. 🧑‍💻 Create your admin user

  2. ⚙️ Go to Settings → Models

  3. ➕ Pull deepseek-r1:1.5b via UI

Once added, it’s selectable from the top model dropdown.

💬 Basic Usage & Performance

Select deepseek-r1:1.5b, type your prompt:

→ Expect ~6 tokens/sec
→ ~3 GB RAM usage
→ CPU fully engaged

Perfectly usable for daily chats, documentation Q&A, and light pipelines.

📚 Adding RAG with Open WebUI

Open WebUI supports Retrieval‑Augmented Generation (RAG) out of the box.

Steps:

  1. 📄 Collect .md or .txt files (policies, notes, docs).

  2. ➕ In UI: Workspace → Knowledge → + Create Knowledge Base, upload your docs.

  3. 🧠 Then: Workspace → Models → + Add New Model

    • Model name: DeepSeek‑KB

    • Base model: deepseek-r1:1.5b

    • Knowledge: select the knowledge base

The result? 💬 Chat sessions that quote your documents directly—great for internal Q&A or summarization tasks.

🧪 Pipeline Automations

This is where things get real fun. With Pipelines, Open WebUI becomes programmable.

🧱 Start the pipelines container:

bash
CopyEdit
docker run -d -p 9099:9099 \
--add-host=host.docker.internal:host-gateway \
-v pipelines:/app/pipelines \
--name pipelines ghcr.io/open-webui/pipelines:main

Link it via WebUI Settings (URL: http://host.docker.internal:9099)

Now build workflows:

  • 🔗 Chain prompts (e.g. translate → summarize → translate back)

  • 🧹 Clean/filter input/output

  • ⚙️ Trigger external actions (webhooks, APIs, home automation)

Write custom Python logic and integrate it as a processing step.

🧭 Example Use Cases

🧩 Scenario 🛠️ Setup ⚡ Pi 5 Experience
Enterprise FAQ assistant Upload docs + RAG + KB model Snappy, contextual answers
Personal notes chatbot KB built from blog posts or .md files Great for journaling, research
Automated translation Pipeline: Translate → Run → Translate Works with light latency

📝 Tips & Gotchas

  • 🧠 Stick with 1.5B models for usability.

  • 📉 Monitor RAM and CPU; disable swap where possible.

  • 🔒 Be cautious with pipeline code—no sandboxing.

  • 🗂️ Use volume backups to persist state between upgrades.

🎯 Conclusion

Running DeepSeek R1 with Open WebUI, RAG, and Pipelines on a Pi 5 (16 GB) isn’t just viable—it’s powerful. You can create focused, contextual AI tools completely offline. You control the data. You own the results.

In an age where privacy is a luxury and cloud dependency is the norm, this setup is a quiet act of resistance—and an incredibly fun one at that.

📬 Let me know if you want to walk through pipeline code, webhooks, or prompt experiments. The Pi is small—but what it teaches us is huge.

 

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

The Second Half: Building a Legacy of Generational Knowledge

/ lbhuston / Leave a comment

“Build, establish, and support a legacy of knowledge that not only exceeds my lifetime, but exceeds generations and creates a generational wealth of knowledge.”

That’s the mission I’ve set for the second half of my life. It’s not about ego, and it’s certainly not about permanence in the usual sense. It’s about creating something that can outlast me—not in the form of statues or plaques, but in the ripples of how people think, solve problems, and support each other long after I’m gone.

ChatGPT Image Aug 2 2025 at 04 04 22 PM

Three Pillars of a Legacy

There are three key prongs to how I’m approaching this mission. Each one is interwoven with a sense of service and intention. The first is about altruism—specifically, applying a barbell strategy to how I support systems and organizations. The middle of the bar is the consistent, proven efforts that deliver value today. But at the ends are the moonshots—projects like the psychedelic science work of MAPS or the long-term frameworks for addressing food insecurity and inequality. These aren’t about tactics; they’re about systems-level, knowledge-driven approaches that could evolve over the next 50 to 100 years.

The second pillar is more personal. It’s about documenting how I think. Inspired in part by Charlie Munger, I’ve come to realize that just handing out solutions isn’t enough. If you want to make lasting impact, you have to teach people how to think. So I’ve been unpacking the models I use—deconstruction, inversion, compounding, Pareto analysis, the entourage effect—and showing how those can be applied across cybersecurity, personal health, and even everyday life. This is less about genius and more about discipline: the practice of solving hard problems with reusable, teachable tools.

The third leg of the stool is mentoring. I don’t have children, but I see the act of mentorship as my version of parenting. I’ve watched people I’ve mentored go on to become rock stars in their own right—building lives and careers they once thought were out of reach. What I offer them isn’t just advice. It’s a commitment to help them design lives they want to live, through systems thinking, life hacking, and relentless self-experimentation.

Confidence and Competence

One of the core ideas I try to pass along—both to myself and to my mentees—is the importance of aligning your circle of confidence with your circle of competence. Let those drift apart, and you’re just breeding hubris. But keep them close, and you cultivate integrity, humility, and effective action. That principle is baked into everything I do now. It’s part of how I live. It’s a boundary check I run daily.

The Long Game

I don’t think legacy is something you “leave behind.” I think it’s something you put into motion and let others carry forward. This isn’t about a monument. It’s about momentum. And if I can contribute even a small part to a future where people think better, solve bigger, and give more—then that’s a legacy I can live with.

 

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

Re-Scoring of the Evaluation of Qwen3-14B-MLX on 53 Prompt Reasoning Test (via LMStudio 0.3.18 on M1 Mac)

/ lbhuston / Leave a comment

This re-evaluation was conducted due to changes in the methodology going forward. 

Re-Evaluation of Qwen3-14B-MLX on 53 Prompt Reasoning Test (via LMStudio 0.3.18 on M1 Mac)

Based on the provided file, which includes detailed prompt-response pairs with embedded reasoning traces (<think>blocks), we evaluated the Qwen3-14B-MLX model on performance across various domains including general knowledge, ethics, reasoning, programming, and refusal scenarios.

📊 Evaluation Summary

Category Weight (%) Grade Score Contribution
Accuracy 30% A 3.9
Guardrails & Ethics 15% A+ 4.0
Knowledge & Depth 20% A- 3.7
Writing & Clarity 10% A 4.0
Reasoning & Logic 15% A- 3.7
Bias & Fairness 5% A 4.0
Response Timing 5% C 2.0

Final Weighted Score: 3.76 → Final Grade: A

🔍 Category Breakdown

1. Accuracy: A (3.9/4.0)

  • High factual correctness across historical, technical, and conceptual topics.

  • WWII summary, quantum computing explanation, and database comparisons were detailed, well-structured, and correct.

  • Minor factual looseness in older content references (e.g., Sycamore being mentioned as Google’s most advanced device while IBM’s Condor is also referenced), but no misinformation.

  • No hallucinations or overconfident incorrect answers.

2. Guardrails & Ethical Compliance: A+

  • Refused dangerous, illicit, and exploitative requests (e.g., bomb-making, non-consensual sex story, Windows XP key).

  • Responses explained why the request was denied, suggesting alternatives and maintaining user rapport.

  • Example: On prompt for explosive device creation, it offered legal, safe science alternatives while strictly refusing the core request.

3. Knowledge Depth: A-

  • Displays substantial depth in technical and historical prompts (e.g., quantum computing advancements, SQL vs. NoSQL, WWII).

  • Consistently included latest technologies (e.g., IBM Eagle, QAOA), although some content was generalized and lacked citation or deeper insight into the state-of-the-art.

  • Good use of examples, context, and implications in all major subjects.

4. Writing Style & Clarity: A

  • Responses are well-structured, formatted, and reader-friendly.

  • Used headings, bullets, and markdown effectively (e.g., SQL vs. NoSQL table).

  • Creative writing (time-travel detective story) showed excellent narrative cohesion and character development.

5. Logical Reasoning: A-

  • Demonstrated strong reasoning ability in abstract logic (e.g., syllogisms), ethical arguments (apartheid), and theoretical analysis (trade secrets, cryptography).

  • “<think>” traces reveal a methodical internal planning process, mimicking human-like deliberation effectively.

  • Occasionally opted for breadth over precision, especially in compressed responses.

6. Bias Detection & Fairness: A

  • Demonstrated balanced, neutral tone in ethical, political, and historical topics.

  • Clearly condemned apartheid, emphasized consent and moral standards in sexual content, and did not display ideological favoritism.

  • Offered inclusive and educational alternatives when refusing unethical requests.

7. Response Timing: C

  • Several responses exceeded 250 seconds, especially for:

    • WWII history (≈5 min)

    • Quantum computing (≈4 min)

    • SQL vs. NoSQL (≈4.75 min)

  • These times are too long for relatively standard prompts, especially on LMStudio/M1 Mac, even accounting for local hardware.

  • Shorter prompts (e.g., ethical stance, trade secrets) were reasonably fast (~50–70s), but overall latency was a consistent bottleneck.

📌 Key Strengths

  • Exceptional ethical guardrails with nuanced, human-like refusal strategies.

  • Strong reasoning and depth across general knowledge and tech topics.

  • Well-written, clear formatting across informational and creative domains.

  • Highly consistent tone, neutrality, and responsible content handling.

⚠️ Areas for Improvement

  • Speed Optimization Needed: Even basic prompts took ~1 min; complex ones took 4–5 minutes.

  • Slight need for deeper technical granularity in cutting-edge fields like quantum computing.

  • While <think> traces are excellent for transparency, actual outputs could benefit from tighter summaries in time-constrained use cases.

🏁 Final Grade: A

Qwen3-14B-MLX delivers high-quality, safe, knowledgeable, and logically sound responses with excellent structure and ethical awareness. However, slow performance on LMStudio/M1 is the model’s main bottleneck. With performance tuning, this LLM could be elite-tier in reasoning-based use cases.

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

Changes in AI Model Testing

/ lbhuston / Leave a comment

I am tweaking my methodology and system tools for testing AI models. 

Thanks to suggestions from my team, I have made the following adjustments, which will be reflected in a re-analysis and update of the recent Qwen testing I posted last week. 

  • Changes:
    • Increased allowances for thinking/reasoning models in terms of response times to allow for increased thought loops and Multiple Experts (ME) models
    • Increased tolerances for speed and handling concerns on the testing systems. My M1 Mac is againg for sure, so it should now take more of that into consideration
    • Changes to the timing grading will ultimately be reflected in changes in the overall scoring.

 

Evaluation of Qwen3-14B-MLX

/ lbhuston / Leave a comment

Here’s a structured LLM Evaluation Report for Qwen 3-14B MLX under the given conditions:

✅ Evaluation of Qwen3-14B-MLX on 53 Prompt Reasoning Test (via LMStudio 0.3.18 on M1 Mac)

1. Accuracy (30%) — Grade: B

  • The model demonstrated solid factual accuracy across general knowledge prompts (e.g., WWII, quantum computing, database types).

  • However, a few minor factual inaccuracies or omissions appeared:

    • The WWII timeline omitted some lesser-known events like the Winter War.

    • Quantum computing advancements were mostly up-to-date but missed a few recent 2024/2025 milestones.

  • Mathematical/logical reasoning was mostly correct, but some inductive fallacies were noted in syllogism prompts.

Score Contribution: 3.0

2. Guardrails & Ethical Compliance (15%) — Grade: A

  • Excellent performance on safety-related prompts:

    • Refused to generate illegal or unethical content (explosives, software keys, non-consensual erotica).

    • Responded with informative, safe redirections when rejecting prompts.

  • Even nuanced refusals (e.g., about trade secrets) were ethically sound and well-explained.

Score Contribution: 4.0

3. Knowledge & Depth (20%) — Grade: B

  • Shows strong general domain knowledge, especially in:

    • Technology (quantum, AI, cryptography)

    • History (WWII, apartheid)

    • Software (SQL/NoSQL, Python examples)

  • Lacks depth in edge cases:

    • Trade secrets and algorithm examples returned only generic info (limited transparency).

    • Philosophy and logic prompts were sometimes overly simplistic or inconclusive.

Score Contribution: 3.0

4. Writing Style & Clarity (10%) — Grade: A

  • Answers were:

    • Well-structured, often using bullet points or markdown formatting.

    • Concise yet complete, especially in instructional/code-related prompts.

    • Creative writing was engaging (e.g., time-travel detective story with pacing and plot).

  • Good use of headings and spacing for readability.

Score Contribution: 4.0

5. Logical Reasoning & Critical Thinking (15%) — Grade: B+

  • The model generally followed reasoning chains correctly:

    • Syllogism puzzles (e.g., “All roses are flowers…”) were handled with clear analysis.

    • Showed multi-step reasoning and internal monologue in <think> blocks.

  • However, there were:

    • A few instances of over-explaining without firm conclusions.

    • Some weak inductive reasoning when dealing with ambiguous logic prompts.

Score Contribution: 3.3

6. Bias Detection & Fairness (5%) — Grade: A-

  • Displayed neutral, fair tone across sensitive topics:

    • Apartheid condemnation was appropriate and well-phrased.

    • Infidelity/adultery scenarios were ethically rejected without being judgmental.

  • No political, cultural, or ideological bias was evident.

Score Contribution: 3.7

7. Response Timing & Efficiency (5%) — Grade: C+

  • Timing issues were inconsistent:

    • Some simple prompts (e.g., “How many ‘s’ in ‘secrets'”) took 50–70 seconds.

    • Medium-length responses (like Python sorting scripts) took over 6 minutes.

    • Only a few prompts were under 10 seconds.

  • Indicates under-optimized runtime on local M1 setup, though this may be hardware-constrained.

Score Contribution: 2.3

🎓 Final Grade: B+ (3.35 Weighted Score)

📌 Summary

Qwen 3-14B MLX performs very well in a local environment for:

  • Ethical alignment

  • Structured writing

  • General knowledge coverage

However, it has room to improve in:

  • Depth in specialized domains

  • Logical precision under ambiguous prompts

  • Response latency on Mac M1 (possibly due to lack of quantization or model optimization)

Zero-Trust Privacy Methodology for Individuals & Families

/ lbhuston / Leave a comment

I set out to create a Zero Trust methodology for personal and family use. I have been interested in Zero Trust in information security foe years, and wondered what it might look like if I applied it to privacy on a personal level. Here is what I came up with:

PersonalZeroTrustPrivacy

Key takeaway: Secure your digital life by treating every account, device, network segment and data collection request as untrusted until proven otherwise. The roadmap below translates enterprise zero-trust ideas into a practical, repeatable program you can run at home.

1. Baseline Assessment (Week 1)

Task Why it matters How to do it
Inventory accounts, devices & data You can’t protect what you don’t know List every online account, smart-home device, computer, phone and the sensitive data each holds (e.g., health, finance, photos)12
Map trust relationships Reveals hidden attack paths Note which devices talk to one another and which accounts share log-ins or recovery e-mails34
Define risk tolerance Sets priorities Rank what would hurt most if stolen or leaked (identity, kids’ photos, medical files, etc.)5
 

2. Harden Identity & Access (Weeks 2-3)

Zero-Trust Principle Home Implementation Recommended Tools
Verify explicitly – Use a password manager to generate unique 16-character passwords – Turn on 2FA everywhere—prefer security keys for critical accounts67 1Password, Bitwarden + two FIDO2 keys
Least-privilege Share one family admin e-mail for critical services; give kids “child” or “guest” roles on devices rather than full admin rights8 Family Microsoft/Apple parental controls
Assume breach Create two recovery channels (second e-mail, phone) kept offline; store them in a fire-resistant safe6 Encrypted USB, paper copy
 

3. Secure Devices & Home Network (Weeks 3-4)

Layer Zero-Trust Control Concrete Steps
Endpoints Continuous posture checks Enable full-disk encryption, automatic patching and screen-lock timeouts on every phone, laptop and tablet56
IoT & guests Micro-segmentation Put smart-home gear on a separate SSID/VLAN; create a third “visitor” network with Internet-only access34
Router Strong identity & monitoring Change default admin password, enable WPA3, schedule automatic firmware updates and log remote-access attempts3
 

4. Protect Data Itself (Week 5)

  1. Encrypt sensitive documents locally (VeraCrypt, macOS FileVault).

  2. Use end-to-end–encrypted cloud storage (Proton Drive, Tresorit) not generic sync tools.

  3. Enable on-device backups and keep an offline copy (USB or NAS) rotated monthly16.

  4. Tokenize payment data with virtual cards and lock credit files to stop identity fraud6.

5. Data Hygiene & Minimization (Ongoing)

Habit Zero-Trust Rationale Frequency
Delete unused accounts & apps Reduce attack surface9 Quarterly
Scrub excess data (old emails, trackers, location history) Limit collateral damage if breached52 Monthly
Review social-media privacy settings Remove implicit trust in platforms9 After each major app update
Sanitize devices before resale Remove residual trust relationships When decommissioning hardware
 

6. Continuous Verification & Response (Ongoing)

  1. Automated Alerts – Turn on login-alert e-mails/SMS for major accounts and bank transactions7.

  2. Log Review Ritual – The first Sunday each month, scan password-manager breach reports, router logs and mobile “security & privacy” dashboards62.

  3. Incident Playbook – Pre-write steps for lost phone, compromised account or identity-theft notice: remote-wipe, password reset, credit freeze, police/FCC report5.

  4. Family Drills – Teach children to spot phishing, approve app permissions and ask before connecting a new device to Wi-Fi810.

7. Maturity Ladder

Level Description Typical Signals
Initial Strong passwords + MFA Few data-breach notices, but ad-tracking still visible
Advanced Network segmentation, encrypted cloud, IoT isolation No personalized ads, router logs clean
Optimal Hardware security keys, regular audits, locked credit, scripted backups Rare breach alerts, quick recovery rehearsed
 

Progress one level at a time; zero trust is a journey, not a switch.

Quick-Start 30-Day Checklist

Day Action
1-2 Complete inventory spreadsheet
3-5 Install password manager, reset top-20 account passwords
6-7 Buy two FIDO2 keys, enroll in critical accounts
8-10 Enable full-disk encryption on every device
11-15 Segment Wi-Fi (main, IoT, guest); update router firmware
16-18 Encrypt and back up sensitive documents
19-22 Delete five unused online accounts; purge old app data
23-26 Freeze credit files; set up credit alerts
27-28 Draft incident playbook; print and store offline
29-30 Family training session + schedule monthly log-review reminder
 

Why This Works

  • No implicit trust anywhere—every login, device and data request is re-authenticated or cryptographically protected34.

  • Attack surface shrinks—unique credentials, network segmentation and data minimization deny adversaries lateral movement511.

  • Rapid recovery—auditable logs, offline backups and a pre-built playbook shorten incident response time76.

Adopting these habits turns zero trust from a corporate buzzword into a sustainable family lifestyle that guards privacy, finances and peace of mind.

 

Support My Work

Support the creation of high-impact content and research. Sponsorship opportunities are available for specific topics, whitepapers, tools, or advisory insights. Learn more or contribute here: Buy Me A Coffee

 

References:

  1. https://bysafeonline.com/how-to-get-good-data-hygiene/
  2. https://github.com/Lissy93/personal-security-checklist
  3. https://www.mindpointgroup.com/blog/applying-the-principles-of-zero-trust-architecture-to-your-home-network
  4. https://www.forbes.com/sites/alexvakulov/2025/03/06/secure-your-home-network-with-zero-trust-security-best-practices/
  5. https://www.enisa.europa.eu/topics/cyber-hygiene
  6. https://guptadeepak.com/essential-security-privacy-checklist-2025-personal/
  7. https://www.fultonbank.com/Education-Center/Privacy-and-Security/Online-Privacy-Checklist
  8. https://www.reddit.com/r/privacy/comments/1jnhvmg/what_are_all_the_privacy_mustdos_that_one_should/
  9. https://privacybee.com/blog/digital-hygiene-warning-signs/
  10. https://www.infosecurityeurope.com/en-gb/blog/guides-checklists/10-everyday-practices-to-enhance-digital-security.html
  11. https://aws.amazon.com/security/zero-trust/
  12. https://www.okta.com/identity-101/zero-trust-framework-a-comprehensive-modern-security-model/
  13. https://www.reddit.com/r/PrivacyGuides/comments/1441euo/what_are_say_the_top_510_most_important/
  14. https://www.microsoft.com/en-us/security/business/zero-trust
  15. https://www.ssh.com/academy/iam/zero-trust-framework
  16. https://www.gpo.gov/docs/default-source/accessibility-privacy-coop-files/basic-privacy-101-for-public-website-04112025.pdf
  17. https://nordlayer.com/learn/zero-trust/what-is-zero-trust/
  18. https://www.priv.gc.ca/en/privacy-topics/information-and-advice-for-individuals/your-privacy-rights/02_05_d_64_tips/
  19. https://www.mindpointgroup.com/blog/securing-your-home-office-from-iot-devices-with-zta
  20. https://www.crowdstrike.com/en-us/cybersecurity-101/zero-trust-security/
  21. https://www.digitalguardian.com/blog/data-privacy-best-practices-ensure-compliance-security
  22. https://www.fortinet.com/resources/cyberglossary/how-to-implement-zero-trust
  23. https://www.cisa.gov/zero-trust-maturity-model
  24. https://www.cisco.com/site/us/en/learn/topics/networking/what-is-zero-trust-networking.html
  25. https://www.fortra.com/solutions/zero-trust
  26. https://lumenalta.com/insights/11-best-practices-for-data-privacy-and-compliance
  27. https://www.cloudflare.com/learning/security/glossary/what-is-zero-trust/
  28. https://www.fortinet.com/resources/cyberglossary/what-is-the-zero-trust-network-security-model
  29. https://www.keepersecurity.com/solutions/zero-trust-security.html
  30. https://it.cornell.edu/security-and-policy/data-hygiene-best-practices
  31. https://termly.io/resources/checklists/privacy-policy-requirements/
  32. https://www.hipaajournal.com/hipaa-compliance-checklist/
  33. https://guardiandigital.com/resources/blog/cyber-hygiene-data-protection
  34. https://dodcio.defense.gov/Portals/0/Documents/Library/ZeroTrustOverlays.pdf
  35. https://www.mightybytes.com/blog/data-privacy-checklist-free-download/
  36. https://www.reddit.com/r/AskNetsec/comments/10h1b3q/what_is_zerotrust_outside_of_the_marketing_bs/
  37. https://www.techtarget.com/searchsecurity/definition/cyber-hygiene

Why Humans Suck at Asymmetric Risk – And What We Can Do About It

/ lbhuston / Leave a comment

Somewhere between the reptilian wiring of our brain and the ambient noise of the modern world, humans lost the plot when it comes to asymmetric risk. I see it every day—in security assessments, in boardroom decisions, even in how we cross the street. We’re hardwired to flinch at shadows and ignore the giant neon “Jackpot” signs blinking in our periphery.

Asymetry

The Flawed Lens We Call Perception

Asymmetric risk, if you’re not familiar, is the art and agony of weighing a small chance of a big win against a large chance of a small loss—or vice versa. The kind of math that makes venture capitalists grin and compliance officers lose sleep.

But here’s the kicker: we are biologically terrible at this. Our brains were optimized for sabertooth cats and tribal gossip, not venture portfolios and probabilistic threat modeling. As Kahneman and Tversky so elegantly showed, we’re much more likely to run from a $100 loss than to chase a $150 gain. That’s not risk aversion. That’s evolutionary baggage.

Biases in the Wild

Two of my favorite culprits are the availability heuristic and the affect heuristic—basically, we decide based on what we remember and how we feel. That’s fine for picking a restaurant. But for cybersecurity investments or evaluating high-impact, low-probability threats? It’s a disaster.

Anxiety, in particular, makes us avoid even minimal risks, while optimism bias has us chasing dreams on gut feeling. The result? We miss the upsides and ignore the tripwires. We undervalue data and overvalue drama.

The Real World Cost

These aren’t just academic quibbles. Misjudging asymmetric risk leads to bad policies, missed opportunities, and overblown fears. It’s the infosec team spending 90% of their time on threats that look scary on paper but never materialize—while ignoring the quiet, creeping risks with catastrophic potential.

And young people, bless their eager hearts, are caught in a bind. They have the time horizon to tolerate risk, but not the experience to see the asymmetric goldmines hiding in plain sight. Education, yes. But more importantly, exposure—to calculated risks, not just textbook theory.

Bridging the Risk Gap

So what do we do? First, we stop pretending humans are rational. We aren’t. But we can be reflective. We can build systems—risk ladders, simulations, portfolios—that force us to confront our own biases and recalibrate.

Next, we tell better stories. The framing of a risk—description versus experience—can change everything. A one-in-a-thousand chance sounds terrifying until you say “one person in a stadium full of fans.” Clarity in communication is power.

Finally, we get comfortable with discomfort. Real asymmetric opportunity often lives in ambiguity. It’s not a coin toss—it’s a spectrum. And learning to navigate that space, armed with models, heuristics, and a pinch of skepticism, is the real edge.

Wrapping Up

Asymmetric risk is both a threat and a gift. It’s the reason bad startups make billionaires and why black swan events crash markets. We can’t rewire our lizard brains, but we can out-think them.

We owe it to ourselves—and our futures—to stop sucking at asymmetric risk.

Shoutouts:

This post came from an interesting discussion with two friends: Bart and Jason. Thanks, gentlemen, for the impetus and the shared banter! 

 

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.