Posts

Showing posts from August, 2026

Case Study: The Ghosting Reality—Turning Silent Rejections into Actionable Signals

Image
A recent USA Today analysis highlighted a frustrating trend in today’s job market: the overwhelming number of applications that simply go into a black hole. WORKS Commons data tells the exact same story. To manage this without manual overhead, WOKS Commons now includes an automated, event-driven pipeline: Automated Time-Decay: A daily background process flags applications with no employer response after 30 days. Event-Driven Processing: The system emits a rejection event, which an event processor dequeues and passes via an asynchronous channel to a background reader. LLM Gap Analysis: The reader sends the job description alongside my targeted profile to an LLM, generating structured diagnostic signals analyzing potential skill gaps or alignment issues. The user can view the analysis result when viewing the declined application. As the data shows, nearly half of all applications simply decay without a response. This is the rejection pipeline. The user can decline manually after receivin...

Nugget 20: Git Alias to Remove a local, and Remote Branch and checkout the "Main" branch

Image
I have been using this alias successfully. It removes the local and remote branch and checks out main (formerly "master") branch.  Assume you have a branch named  event-processing-pipeline, the change request has been completed and merged to main; the branch is no longer needed . You can run your custom alias, on your computer, like this: git destroy-branch event-processing-pipeline Use it with caution. Do a little test first.  Create a test-branch and push it to remote.   git checkout -b test-branch                                                                             git push -u origin test-branch                                              ...

The Semantic Sink: How AI and the Collapse of "Conduct" Threaten Civil Society — An Essay

Image
We are living through the dawn of a new Gutenberg era. Large Language Models (LLMs) and Retrieval-Augmented Generation (RAG) represent a massive leap forward for humanity—they are, quite literally, the printing press of our times. The printing press democratized the written word; AI is democratizing the synthesis of human though t. But just as the printing press could bind both holy scripture and Mein Kampf , AI possesses a neutral capacity to amplify whatever data it is fed. Today, we are facing a subtle, systemic danger at the intersection of AI technology and human culture: the weaponization of ideological compliance, and the erosion of basic human decency disguised as modern consensus. The RAG "Black Hole" and Consensus Creep When humans ask AI to analyze highly charged political or social events—such as a business refusing service to a public official over their political alignment—the system relies on a mathematical process called vector retrieval. Words and concepts ar...

Nugget 19: Distill Before You Distribute

Image
Problem While building WORKS Commons, I found myself looking at Docker, Kubernetes, microservices, and Domain-Driven Design (DDD). After spending years maintaining a large enterprise monolith, I wondered whether my architecture was falling behind modern practices. The temptation was obvious: "I have BackgroundServices . Maybe they should become microservices." At first glance, the idea sounded reasonable. Modern systems often advertise: Kubernetes Microservices Event-Driven Architecture Distributed Systems However, something felt forced. Observation Most of WORKS Commons consists of tightly related business workflows: Job Applications ↓ Interview ↓ Evaluation ↓ Training These components share concepts, state, and business rules. Separating them simply because container technology exists would increase complexity without providing meaningful benefits. The real issue was not deployment. The real issue was architectural distillation. The project currently contains: ...