Journal
Notes from active work
Records of what I build, observe, change, and learn while developing software with AI agents. Longer essays and technical reference material live in the library.
These entries document an evolving practice and its results, including changed assumptions and failures where they matter—not a generic guide for how every team should work.
-
Current Work now connects status and Journal evidence
Repurposed the retained Projects page to separate active systems from historical work and connect dated Events to current status without changing that status through chronology.
-
New article: Agent Skills inside TeqFW packages
How to ship instructions for an AI coding agent with a package and keep them aligned with the installed code version.
-
My Russian-language book about the browser is now published
A new book about the browser as a personal operating environment for the internet is available in Russian.
-
Why Dependency Injection Matters in JavaScript
A new article on DI as a way to reduce the cost of independently verifying components, rather than an obligatory pattern or an OOP feature.
-
An Agent Skill for Exploring Architecture Foundations
A first experimental skill for examining architectural complexity, boundaries, ownership, authority, and change in software systems.
-
Human Intelligence and LLM Intelligence
A new library essay on agency, non-agentic intelligence, and the practical division of roles between humans and LLMs.
-
Codex analytics started tracking a local skill
A local skill for documenting the browser side of web applications appeared in Codex analytics within days, and OpenAI is already collecting usage stats on it.
-
GitHub Issues and Codex Agents in a Single Workflow
A workflow that connects GitHub Issues and Codex agents is now running on a real repository. The idea of controlled product evolution through agent workflows is now taking concrete form.
-
I updated teqfw.com with Codex
The site runs on TeqFW. I worked on the page with Codex using ADSM. The update required a lot of context, specifications, code, templates, and static assets.
-
My ADSM book in English is on Leanpub
The English version of my ADSM book is now on Leanpub. It was translated with a Codex agent and took about 10% of my weekly Codex quota on GPT Plus. Free copies are available on request through my Telegram channels ru, en, es.
-
-
Talk is cheap. So is code
A practical experiment showed that context preserves the behavior of the project, while code can be regenerated. The full text is on Habr and a copy is in the site library.
-
@teqfw/github-flows gets a host application
A host application was assembled for @teqfw/github-flows to run the server, show logs and configs in the browser, and rely on GitHub PATs and Codex OAuth tokens.
-
Fourth version of the agent-skill for ESM code checks
The fourth version of @flancer32/skill-teqfw-esm-validator adds 12 checks for TeqFW code and shows that skills are already useful for moving shared rules into a portable layer.
-
My first agent-skill for ESM validation
A first agent-skill for Tequila was built and published: three ESM compatibility checks, from issue to npm package in about 40 minutes.
-
@teqfw/github-flows is packaged as a reusable library
The package is a library for intercepting GitHub webhooks, launching agents in Docker, and building workflows that can carry code to new releases.
-
GitHub Issues gateway for Codex
A proof of concept was built for passing GitHub issues to a Codex agent. The gateway runs under adsm-agent and already covers several repositories, but it still needs more work before it becomes stable.
-
Codex agent and a GitHub issue
A Codex agent explained a runtime-configuration conflict in @teqfw/di, turned the fix into GitHub issue #33, and removed the extra manual handoff between agents.
-
Codex agent in autonomous mode on a server
A Codex agent ran autonomously on a US virtual server, took three tries to produce a simple file, and showed what this setup costs in practice. The same pattern points toward webhook-driven issue triage and small automated development workflows.
-
Agent-friendly documentation for npm packages
I went through a Reddit discussion and my own
ai/AGENTS.mdexperiment for@teqfw/di: how to give an agent a compact but useful package context. -
@teqfw/di switches to an LLM-first workflow
I moved @teqfw/di to a workflow where documentation for the agent matters more than keeping all the context in my head. I also republished the article about this transition as a separate library page.
-
TeqFW Guide: JSDoc — onboarding around JSDoc in TeqFW
I launched a custom GPT chat for the TeqFW team so JSDoc stays part of the project’s daily workflow and VSCode can read package types more reliably.
-
TeqFW Guide: Enum — an architecture assistant for onboarding
I launched a custom GPT chat to align understanding of Enum in TeqFW and support onboarding for the team.
-
TeqFW Guide: DTO — a personal architecture assistant
I launched a personal GPT assistant for onboarding and aligning architectural understanding of DTOs in TeqFW. It conveys a coherent model and helps keep a single architectural voice.
-
Telegram Translation Publisher: ADSM and the guided evolution of an agent-built app
A Node.js CLI built by an agent on top of an architecture defined upfront—an example of controlled project evolution with ADSM.
-
From ideas to code: testing attention theory in practice
I describe my app Mindstream, built with ADSM, where browser attention signals turn into an interest score via embeddings; the original post explains the model and its limitations.
-
Solving the planet’s overpopulation problem with AI
In the article, I note an emerging shift: personal AI systems are changing how we trust information, and 5 out of 24 survey participants consider a transfer of consciousness to silicon plausible.
-
Knowledge and attention
Summary of the essay: knowledge integrates into personal worldviews, while attention is the finite resource we spend to absorb meanings.
-
JavaScript in VSCode
Why JavaScript analysis in VSCode relies on the TypeScript model, how
tsserverworks, and where dynamic links become invisible. -
AGENTS.md in ADSM
Personal experience applying AGENTS.md files during the development of Svyazist and their role in the ADSM methodology.
This is the second experimental article shaped according to the Acceptance-First Knowledge Principle (AFKP). The "hook" and "resonance" stages are described in an article on Habr.
-
ADSM: top-level directories
My personal approach to the baseline file structure of projects in accordance with the ADSM methodology.
This is the first experimental article framed according to the Acceptance-First Knowledge Principle (AFKP). This text corresponds to stage 1 (engagement).
-
When knowledge is too much
This publication explains how thinking shifts once information becomes too much and why shaping forms of perception matters.
-
ADSM: WebRTC video chat through a Codex agent
The Habr publication describes my experiment building a WebRTC video chat via a Codex agent. The text is available via the link.
-
How long will we keep discriminating against algorithms?
In this publication I explain the social origin of knowledge and why algorithms should be considered equal participants in the cognitive space.
-
ADSM: from probability to determinism
This publication on Habr describes how the probabilistic nature of LLMs gives way to deterministic outcomes through the structure of the project base.
-
ADSM: Iterative and Hierarchical
The article explains how a Model’s limited context drives an iterative workflow and why a knowledge hierarchy is required to keep generation stable.
-
ADSM: limits of model capabilities
Transformers stick to the network architecture: width, depth, and connections define quality and compute limits. The context window determines reproducibility bounds, so stability comes from narrowing the context. The full article is on Habr.
-
Habr Publication: ADSM and AI Role Relationships
An LLM acts as an executor, interpreting the task and proposing options. The article outlines the workflow and its practical consequences.
-
Habr post: A/BDSM and polls
A cheeky post with a clickbait title about A/BDSM. In the polls, ten people chose ADSM over BDSM in both wording options. The downvotes were softer than expected.
-
Generating a client card
Added client card generation to the Domotekhnika store app with name, ID, barcode, and logo. The work took about three and a half hours including translations and styling.
-
The brain's probabilistic nature and how it differs from LLMs
Corrected my mistake: the brain has probabilistic behavior at the level of each synapse. The main difference from LLMs is not randomness but that the brain works through activity patterns and parallel waves, while an LLM uses linear tokens and a sequential domino effect.
-
Agent as the new compiler
The idea that a human description of a product becomes the programming language, and the Agent takes on the role of the compiler. Code stops being primary; the idea becomes central.
-
Integrating @teqfw/di and OpenAI SDK in a Chrome extension
A prototype MV3 extension using @teqfw/di exposed three problems: handling paths, CSP limits, and running the OpenAI SDK in the browser. The DI container made it easier to test code in Node.js and run it in the extension, but it already needs refinements.
-
My first browser extension
First experience creating a browser extension. For me it's a way to test the ADSM methodology in a new environment and document the process through context documents.
-
Simple models as the foundation of ADSM
An experiment with GPT-5 modes showed that ADSM benefits from simple models without reasoning. They provide stability, reproducibility, and let the process be guided through cognitive context.
-
First version of @teqfw/di
Six years after the first commit, the @teqfw/di library reached its first release. Published on npm.
-
AGENTS.md as an entry point
Choosing AGENTS.md as a single entry file for agents proved successful. It's an established format, handy for capturing rules and transferring context between projects.
-
Publication on Habr: when an LLM becomes predictable
A post about how prompts written as executable specifications make models more deterministic, turning them into an engineering tool for code generation.
-
Publication on Habr: indirect control tool
A note about how LLMs work as tools with indirect control: instead of direct commands, you create conditions. In a poll, 90% agreed with the metaphor "people are tools for other people".
-
Single-use apps and ADSM
A small experiment: the ADSM methodology helped build a one-off utility for monitoring apartment rental ads. The agent created the architecture, while minor fixes were easier to apply manually.
-
ADSM — concept of managing a site through an agent
A new direction in my experiments has a name: ADSM. It's the idea of managing a site via an agent, where changes are made through dialogue and instructions instead of manual edits.
-
API and agents: two approaches to page translation
In TeqCMS, translations were done via API one file at a time, but I tried an agent approach: translating multiple pages per session while keeping context. Both methods are valuable.
-
Publication on Habr: history of prompts with AI agents
In the Habr article I note that the main artifact of development with AI agents becomes the instructions and the history of prompts. In a poll, 50% of readers confirmed that they save such iterations.
-
From Machine Code to Documentation
How the value of development has shifted: from machine code and programs to documentation and instructions that let humans and AI agents generate software.
-
Spanish version of the site: AI translation for $0.05
Added a third language - Spanish. Automatic translation of all pages from Russian took 42 requests and cost $0.05. Demonstration of AI localization based on TeqCMS and DeepSeek API.
-
Publication on Habr: "Don't Personify the Inanimate"
Reflections on the boundary between tool and subject in the context of LLMs. Purpose as the key criterion of consciousness. Active discussion and architectural hypotheses in the comments.
-
NutriLog migrated from Astro to TeqCMS
Switched from Astro to TeqCMS with SSR and Mustache. Now translating pages via DeepSeek and deploying to server via GitHub Actions.
-
Site transition to TeqCMS
Migrated the site to my own CMS - TeqCMS. Now all content is generated via SSR, translated by AI, and managed in Git.
-
LLM-first: development without vibe coding
Shared on Habr how I built a CMS with GPT and DeepSeek in 2 weeks using DI, Markdown and JSDoc. LLM as a co-author of architecture.
-
TeqCMS based on Nunjucks
Released a CMS on Nunjucks templates with server-side generation and localization. Published packages and demo site built on TeqFW architecture.
-
smtp-logger for Postfix and Node.js
Created a utility for logging outgoing Postfix emails to SQL via Node.js and @teqfw/di.
-
NutriLog beta launch
Launched open beta of NutriLog AI assistant. First 100 users onboarded via Google Ads.
-
Updated TeqFW philosophy
Published a new edition of the TeqFW philosophy document - with emphasis on modular monolith and unified stack.
-
IoC: DI vs Ambient Context
Published an article about choosing between Dependency Injection and Ambient Context when designing architecture.
-
Clientu Klubs for Domotehnika
Implemented a web application for accumulating client base and launching loyalty programs. Architecture based on TeqFW.
-
Energy efficiency of intelligence
Reasoning about why AGI is unlikely to replace programmers - due to the colossal energy consumption of AI.
-
Tequila Framework philosophy
Published a structured document describing TeqFW architectural principles and approach to modular monolith.
-
Updated documentation principles
Published a new version of the document focusing on structure, logic and format for LLMs and humans.
-
Article removed from Habr
Habr removed my article about AGI impact due to policy against AI content, despite author's contribution.
-
GitHub Action with file exclusion
Developed GitHub Action for branch merging with file exclusion and configured SSH authentication for secure push.
-
Understanding Early vs. Late Binding in JavaScript
The difference between early and late binding is significant but can be challenging to grasp — especially from a developer’s perspective. In this article, I’ll share a foundational
-
Telegram Bot with Node.js: Using Error Handling to Boost Resilience
In this article, I’ll share my experience in developing Telegram bots on Node.js with the [grammY](https://grammy.dev/) library. Bot development often requires robust error handlin
-
Telegram Bot with Node.js: Conversations
In this article, I continue to share the results of studying the creation of Telegram bots in Node.js, as I began in previous publications ([one](https://flancer32.com/telegram-bot
-
Article about code generation with ChatGPT
Shared experience using ChatGPT for automatic template code generation in JS projects.
-
Telegram Bot with Node.js: Implementing CRUD-L Operations Using Command Arguments
In this post, I’ll share my journey into Telegram bot development, following up on a [previous post](https://flancer32.com/telegram-bots-the-first-steps-c1688e572abe) where I creat
-
Telegram Bots: The First Steps
Telegram bots have become [a popular tool](https://flancer32.com/what-is-a-telegram-bot-a-simple-introduction-for-new-users-9d9a675b27b9) for automating tasks, integrating services
-
Launch of my personal website
Introduced personal website as a platform for projects, publications and communication. Focused on my developments, articles and services in web technologies.
-
ES6
exportas a Building BlockFramed
exportas the building block of ES6 modules and hinted at future posts about namespaces. -
JOIN in SELECT with Knex.js
Showed how to build SELECT ... JOIN ... queries with Knex, covering transactions, joins, and alias usage.