2026-01-14 - Current State Audit for Freelance Transition

Timeline

00:54 (Context) primary first focus(es) for the day:

define humain+ai dual-layered-content, and what implications this has for the website/content and changes that will need to be made = definition only.
finalize COMING VERY SOON for NEWSLETTER page on website + perform finalization of substack.
create first posts for X / Reddit - drafts only for now, inside blog_uploader_app.
consider changes to make to initial language context menu manager folders. it may be more suitable to create specific elements of the newsletter to target dual-layer-ingestion as a primary means of exploring the concept - discuss with claude the nature of this development, and whether full site/newsletter transformation is really necessary.
re-organise day around these revelations.
don’t forget to rock’n’roll.

10:01 (Context) # Dev Diary: Kickstarting TheWriteView

Date: January 14, 2026 Topic: Building a Private AI Writing Assistant for Windows

Today marked the official start and MVP completion of TheWriteView, a new desktop application designed to bring AI-powered editing to a local, privacy-focused environment.

The Goal

We wanted a tool that offers “editor-style” assistance (grammar, flow, style) without sending keystrokes to the cloud. The solution? A Flutter-based desktop app leveraging a local Ollama installation.

Implementation Highlights

1. The Stack

We chose Flutter for its ability to create a polished, native-feeling Windows application quickly. For the intelligence layer, we integrated directly with the local Ollama API (running Llama 3), ensuring all processing happens offline.

2. Core Features

We successfully built the following features in our first sprint:

Split-Screen Editor: A clean interface comparing original text with AI suggestions side-by-side.
Smart Prompts: Three distinct levels of editing—Low (Fixes), Intermediate (Flow), and Advanced (Style).
Transparency: A toggle to request “Text Only” or “Text + Explanation” from the AI, giving users insight into why changes were made.
File Management: Built-in export to .txt and .md.

3. Workflow Integration

To make the tool a seamless part of the daily grind, we integrated it into our terminal workflows:

write: Instantly launches the app from anywhere.
work: Added to our daily startup script, launching alongside our other core tools.

What’s Next?

With the foundation solid, the next steps involve refining the UI themes and exploring support for larger context windows and custom model fine-tuning.

Built with Flutter, Dart, and Ollama.

20:40 (Context) new dev-diary template created for AI to use to generate dev-diary entries relating to specific tasks they have completed.
20:40 (Context) new right-click-context tool developed. allows easy addition and removal of right-click-context menu windows 11: add/remove programs to the list of options when right clicking context menu manager folders.
20:40 (Context) - Needed a beginner-safe way to add/remove right-click items without manual registry editing.
Windows 11 primary menu is complex; focused on reliable “classic” registry verbs/handlers first.
Prioritized reversibility (disable/move + restore) and backups before changes.
20:40 (Action) - Built context menu manager files entrypoint with GUI + CLI mode and target-path parsing for prefill.
Implemented registry operations in context menu manager files (verbs/handlers enumeration, add, disable/move, enable/restore, delete).
Added backups via reg.exe export and state tracking in context menu manager files.
Added WinForms UI with tabs: Add Item, Manage Existing, Restore, Tool Launcher.
Added one-click launcher installation that passes %1 and %V parameters automatically and hides the PowerShell window.
Added “Everywhere” creation that writes the same verb to all supported scopes, plus Desktop background support.
Added UI settings persistence for Manage Existing column order/width and filters in context menu manager files.
Added core scripts and test files for end-to-end verification.
20:40 (Observation) - Running .ps1 directly from Explorer is unreliable; wrapping via PowerShell with execution-policy bypass is necessary for a smooth UX.
Docking order can hide tab headers; a TableLayoutPanel makes the layout deterministic across scaling settings.
Showing “what the menu entry actually runs” (script/exe path) is crucial; internal key names aren’t meaningful to users.
20:40 (Open Thread) - Add optional packaging (signed exe) for smoother distribution and fewer execution-policy prompts.
Consider an explicit “installed launchers” status view (detect which scopes currently have the launcher).
Evaluate support for Windows 11 primary (modern) context menu commands (advanced/optional).
01:50 (Context) - 00:30 Seeking freelance opportunities to supplement main income, available 15-20 hours/week for paid work.
00:30 Currently spending 12 hours daily on building/learning with zero paid work or client relationships.
00:45 Operating from hermetic lifestyle with wife and two children (ages 8, 10), homeschooling integrated into daily workflow.
01:00 Technical foundation: BAIBE_CORE, ADDEG, WebDev browser, TheWriteView, blog uploader, DEMMEW—all personal tools, none shared publicly yet.
01:15 Spiritual foundation: Former Ordained Kung Fu Warrior Monk (age 19), 20 years exploring meditation/enlightenment, Mystic Society podcast co-host.
01:30 Work pattern: 9am-2am daily (with family time interspersed), most alive at night, drained by extended social interaction.
02:00 Website infrastructure complete at bigfatdevelopments.com, ready for content generation and newsletter launch.
02:00 Zero platform presence (no Upwork, Fiverr, LinkedIn, Discord, social media activity).
02:00 Zero network, testimonials, or client relationships.
02:15 Age 38, only 2 years traditional employment experience, remainder spent in self-directed learning and monastic/hermetic environments.
01:50 (Action) - 00:45 Shared “Builder-Monk” identity article with Claude for analysis.
01:00 Provided full dev-diary snapshot using DEMMEW tool for comprehensive context.
01:15 Shared 19 Mystic Society podcast transcripts revealing teaching voice and philosophical depth.
01:30 Explored question: “Should I lead with spiritual dimension or keep it subtle in freelance positioning?”
01:45 Acknowledged pattern of attempting “pure depth” (unsustainable financially) vs “pure shallow” (spiritually suffocating).
02:00 Completed detailed Current State Audit across all six categories.
02:15 Identified three major operational patterns: perfectionism/completion anxiety, eternal-beta creative exploration, reluctance toward shallow work.
02:30 Requested dev diary entry creation for this session.
01:50 (Observation) - 01:30 Claude identified core tension: majority of freelance work exists in “shallows” while my heart lives in “the deep.”
01:45 Three-layer strategy resonates: shallow work funds deep work, deep work informs shallow work, with permeable boundaries.
02:00 Current reality: completely hermetic, zero market presence, all tools are personal scaffolds not public products.
02:15 Recognized that 20-year journey from monastery to technical mastery has finally matured into readiness for sustainable livelihood.
02:15 “Nothing feels hard right now” regarding execution—only bridging gap between daily exploration and income generation.
02:30 Most valuable aid: genuine connection with peers who have walked this path, real-lived-energy-wisdom of successful transitions.
01:50 (Open Thread) - 02:30 What are the immediate next actions for this week to begin earning Layer 1 income?
02:30 How to rapidly establish minimal viable presence on freelance platforms without perfectionism paralysis?
02:30 What templates/scripts/positioning language will enable quick client acquisition?
02:30 How to structure dual-purpose content (human + AI audience) for newsletter launch?
02:30 What’s the 30-day roadmap for transitioning from zero presence to first paid clients?
02:30 How to leverage existing tools (BAIBE_CORE, ADDEG, WebDev) as portfolio demonstrations without needing to “productize” them first?
02:30 What’s Claude’s strategic response to this “edge case” scenario?

Context

00:54 primary first focus(es) for the day:

define humain+ai dual-layered-content, and what implications this has for the website/content and changes that will need to be made = definition only.
finalize COMING VERY SOON for NEWSLETTER page on website + perform finalization of substack.
create first posts for X / Reddit - drafts only for now, inside blog_uploader_app.
consider changes to make to initial language context menu manager folders. it may be more suitable to create specific elements of the newsletter to target dual-layer-ingestion as a primary means of exploring the concept - discuss with claude the nature of this development, and whether full site/newsletter transformation is really necessary.
re-organise day around these revelations.
don’t forget to rock’n’roll.

10:01 # Dev Diary: Kickstarting TheWriteView