Skip to content

ai

22 posts with the tag “ai”

AI SDLC

Another great Beyond Coding interview AWS Veteran: The New Software Development Life Cycle - YouTube.

The most practical takeaway is Lessa’s model cost discipline. After a single refactor cost 200 million tokens because Opus was “overthinking” every line, he split the workflow into three tiers:

Tier 1 — SOTA models (Opus, Sonnet): planning, spec writing, architecture decisions only Tier 2 — Mid-tier models: 70–80% of implementation work Tier 3 — Cheap models: code review, linting, adversarial checks

Product loop

  1. discovery Human
  2. whiteboard Human
  3. /roadmap Human+AI
  4. /roadmap —sync
  5. /new-work Human+AI
    • dev loop

Dev loop (Heitor Lessa)

  1. /opsx:explore - human+agent sota
  2. /opsx:plan - human+agent sota
  3. /opsx:apply - agent
  4. refinement - human+agent
  5. merge-check - agent+gate
  6. review & merge - human
  7. /retro - human. workflow loop

Kanata FTW!

Problem: Alt. keyboard layout issue differences between my exp. and laptop internal keeb.

I’m building my new custom low-profile 38-key (3x6) -2 +3 thumbs - but I need to solve a problem I’ll hit.

My Piantor is configured with Vial / QMK with

  • Colemak-DH
  • Home row mods
  • symbol layers
  • combo keys

The mac internal keyboard has no layers and minimal special functions.

  • Colemak-DH ANSI installed as input source
  • CapsLock as LeftCtrl per ModifierKeys
  • HyperKey allows Super ROpt / RMet
  • Aerospace keyboard shortcuts dont work when i switch, it needs stable input source.

The workaround so far: switch input source to Colemak-DH when on laptop with internal keyboard and to Australia when using the Piantor split keeb. Lots of down-sides:

  • no layers or combos on mac internal keyboard
  • Aerospace shortcuts I had to use the qwerty location always.

Action / Research

I’ve researched most of this before, I’ve tried Karabiner-Elements but I didn’t want the complexity of the kernal extension. I’d come across kanata, saw it needed that as a dependency and wrote it off.

A chance Gemini / Google AI mode question put me onto the path that let me rediscover kanata and how it can depend on the karabiner device-kit architecture.

Result

The result is I have a working base kanata configuration with qwerty (for others/troubleshooting) and colemak-dh. Keeps my Aerospace shortcuts same for either layout. I’ll continue to add the additional layers and combo keys I have from vial.

This enables me to try Sturdy / Magic Sturdy regularly till proficient - when working

It’s not 100% smooth, I’ll keep testing out and find any other issues. E.g My Arc shortcuts aren’t working.

Learnings

Continual probing of AI helps us explore the problem space and solution space quickly to eliminate sub-par paths and save time. I re-discovered a major problem worth solving (the issue was back of mind) it can help find the path to follow before commiting much time.

R&D / AI: mini-rag evaluation of cross-encoder efficiency

R&D / AI: Mini-RAG Cross-Encoder Efficiency Evaluation

Plenty of strong RAG content exists on papers and evaluation (e.g., Miraflow Guide).

Forked florianbuetow/mini-rag for local deep dive: how much efficiency gain from the cross-encoder?

Added token test in bdargan/mini-rag + bdargan/mini-rag-runner container. (Output posted below showing savings.)

See rag_token_test.py.

[TOKEN BENCHMARK REPORT]
• Baseline Prompt Tokens (K=10): 308
• Reranked Prompt Tokens (K=3): 112
• Absolute Token Savings: 196
• Efficiency Gains: 63.64%
PASSED

Key takeaways

  • Code from Gemini impressed again.
  • Follow-up: evaluate with Ragas

Priorities

Do you also struggle with those “frog” tasks that are important, but somehow you procrastinate enough to always put them off, till I probably used more time avoiding than it actually takes to complete. :facepalm:

Well I was trying a few ideas, beyond Eisenhower matrix, and came across the low energy task model and the Friction-Sized framework.

Google AI suggested a method to combine, so if identify tasks in md with X.Y.Z, it offered variations depending on tools used and search/filter needs see query

X=Importance (1-2) Y=Urgency (1-2) Z=Friction (1-4)

Z is 1-4 quadrants even though my rule of thumb is to batch the little things for a low energy time. I may sometimes hit those < 2mins immediately and skip the overhead of writing it down, but how many things reallly are 2mins and don’t spin you off distracted elsewhere.

An interesting experiment to help me match my mental energy with different tasks.

The “Friction-Sized” Framework

Because these tasks have deadlines and evoke reluctance, traditional advice like “Eat the Frog” actually backfires. When your mental energy is depleted, staring at a giant “frog” causes Executive Dysfunction—making you freeze and do nothing.To solve this, we must mathematically re-engineer how we measure task weight. Instead of measuring by Time (Duration), we must measure by Friction (Resistance to Start).

Total Effort = Friction (Energy to Start) + Drag (Energy to Complete)

1. The Friction Matrix

Use this 4-quadrant system to categorize both your work and personal life tasks. The goal is to isolate the “Sticky Notes”—tasks that take very little time to complete but have massive mental resistance.

Low Drag (Takes <15 Mins)High Drag (Takes >15 Mins)
High Friction(Reluctant to Start)🛑 The Sticky Notes
• Paying a bill / Renewing a license
• Sending a “difficult” but short email
• Booking a dentist appointment
🐸 The True Frogs
• Tax returns
• Writing a project proposal
• Planning a major trip
Low Friction(Easy to Start)⚡ Quick Wins
• Deleting spam / Sorting mail
• Putting away dishes
• Approving a simple request
🏃‍♂️ The Momentum Builders
• Organizing a closet / Desk
• Exercising / Walking
• Data entry while listening to music2.

2. The 3 Rules of Engagement

To defeat the “Sticky Notes” and “True Frogs” before their deadlines hit, apply these rules:

Rule 1: The “Micro-Leap” (For High Friction, Low Drag)

Never write the actual task on your to-do list. Write the absolute first physical action.

  • Instead of: “Pay car registration” (High Friction)
  • Write: “Open laptop and pull up registration email” (Zero Friction)
  • The Logic: Once the laptop is open and the email is in front of you, the friction drops to zero, and the 5-minute task gets done.

Rule 2: The 10-Minute “Micro-Block” (For True Frogs)

Do not try to “Eat the Frog” all at once. Set a timer for exactly 10 minutes. Tell yourself: “I am allowed to completely stop and quit after 10 minutes.”

  • The Logic: The hardest part of finite mental energy is the anticipation of the effort. A 10-minute boundary tricks your brain into starting. Usually, momentum takes over.

Rule 3: The Work-Life Hybrid Sweep

Never separate your personal and work to-do lists when energy is low. Your brain draws from the exact same central tank of mental energy for both. Batch your “Sticky Notes” (both work and personal) into a single 30-minute window right before lunch or at the very end of the day.

Excalisave for CodeBerg - try out grok build 0.1

I quite like this chrome extension - https://github.com/atharvakadlag/excalisave plugin.

Only problem is the lack of alternative providers.

While having some time to kill (watching a youth volleyball grand final!). I had plenty of time between points to prompt.

I’m trying out different models and providers, so I gave Grok 4.1 with opencode.ai.

Couple more hours Monday morning to get it working. I was hoping to just be in product mode, but I had to go to the codeberg api docs to identify a cause of failure on document create was the incorrect HTTP method. Kinda annoying, it is clearly specified in the swagger docs.

Last iteration it needed network robustness, exponential backoff etc. and a more visual feedback.

It’s cost about $15 in tokens, which idk, I kinda expected it to have been < $10 AUD, going to be more < $20 ($USD 13). Either way it is pretty cheap - I’ll be using this weekly if not daily.

Excalisave fork https://github.com/bdargan/excalisave.

2026 Week 21 - AI agent flows

2026W21

TLDR;

  1. Compare and contrast Matt Pocock AI workflow, particularly around the use of skills /grill-with-docs different types of job types of Human In Loop vs. Away From Keyboard with Allium language and approach.

  2. Try Matt Pocock skills, compare the improve codebase architecture skill with modularity tools from - GitHub - vladikk/modularity: Claude Code plugin for designing modular systems from functional requirements and reviewing existing codebases for modularity problems with actionable improvement recommendations. Based on the Balanced Coupling model. · GitHub and GitHub - JuliusBrussee/caveman: 🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman · GitHub.

  3. Compare results with a varion Kit approach. Been a slow month on prof. dev but I’ve come back to catch up on AI agent flows and particularly about a good approach and scaffolding to achieve good outcomes for AI adoption. While tooling is necessary, I want practical heuristics that can be applied generally.

Matt Pocock has done a decent job explaining his flows and how he focuses on skills to define the job to be done / prd and then how to get the issues/stories into vertical slices/tracer bullet (for pragprog) to guide towards modules with deep interfaces (Jonh Ouster)

I’ve got a growing list of skills to go back to.

2026 Week 16

Try Spec Kit, need to try again.

2026W14-5

Bit under-whelming, vs. general vibe results. I probably need to give it a generally well known problem to remix and regurgitate.

2026 Week 13 - Agent comparisons - AgentOS, BMAD, SpecKit

2026W13

tbh, the bottom up and faster tools of Spec Kit and Open Spec I’ll probably lean towards.

But I’ll still need to try out BMAD and AgentOS for 1st hand experience.

2026 Week 07 - Deno sandboxes

2026W07

Q: Have an untrusted code from your LLM?

Deno sandboxes might do the trick, or atleast show you how to.

2026 Week 06 - Search and mixture of models

2026W06

Trying out Opencode with direct xAI provider.

Interesting paper on search / retrieval

Superlink bm25 and mixture of models.

GitHub - parthsarthi03/raptor: The official implementation of RAPTOR: Recursive Abstractive Processing for Tree-Organized Retrieval Airbnb Search Benchmarking - Comparison of retrieval techniques | VectorHub by Superlinked

Way back we used Elasticsearch for hotel search at Wotif.com, interesting this approach with mixing of models.

On Local-First

Watched an intewview with jamsocket creator in my local-first readings, plane is super interesting.

RAG from scratch

Safety