The result is "Draft for Consultation." It proves my point: just because you can, doesn't mean you should. It’s terrible. You’re going to love it.

Sorry in advance to anyone who listens to it.

The real work is not typing; the real work is thinking.

#DeepWork #SoftwareEngineering #DevSky #Tech #EngineeringLeadership #SystemDesign #Philosophy

The rush to "build" often means prematurely entangling ideas, leading to accidental complexity that paralyzes future development. You cannot stumble into a robust architecture for high-stakes stochastic systems.

Spend time designing that model before you worry about the execution.

#SoftwareArchitecture #Datomic #DevSky #SystemDesign #Database #Tech #SoftwareEngineering #Data

Their states are assertions and retractions over time. If you don't have a rigorous, temporal model of your execution, you aren't engineering; you're just hoping.

Designing this interplay - where the stochastic meets the deterministic - is the hardest part of the architecture.

#KnowledgeGraph #AI #RAG #SystemDesign #DevSky #Tech #GraphDatabase #SoftwareEngineering

The LLM suggests actions or interpretations, but the KG validates them against established facts and schema. The LLM is a powerful reasoning engine, but the KG is the referee.

Choosing when to impose structure, and when to defer it, is the essence of sound design.

#DataModeling #Datomic #SoftwareEngineering #DevSky #Tech #Database #SystemDesign #Data

We don't force it into a predefined relational structure immediately. Using a database like Datomic allows us to accrete facts about this data later, evolving the schema as our understanding grows. By prioritizing data over structure, we maintain flexibility.

Choosing where the seams are, and what belongs in an interceptor versus the task itself, is not trivial.

#SoftwareArchitecture #DevSky #CleanCode #SoftwareEngineering #Tech #DesignPatterns #Refactoring

If you want a system that can evolve, you must separate these concerns. We use interceptor chains—middleware wrapping the execution of every task. This allows us to inject cross-cutting "plumbing" without polluting the core logic.

Designing the rules for this adaptation requires profound clarity about the problem domain, not just the technology.

#AIAgents #SystemDesign #DevSky #SoftwareEngineering #Tech #AI #Orchestration #Automation

After a task runs, an assessor determines the continuation, potentially rewriting the workflow DAG at runtime. This is how you bridge the gap between predefined orchestration and autonomous behavior.

Designing this ledger is a prerequisite, not an afterthought.

#LLMs #AI #Observability #DevSky #SoftwareEngineering #Datomic #Tech #SystemArchitecture #AIGovernance

This ledger must capture the exact inputs (fingerprinted), the precise function executed, the outputs, and the duration. Datomic gives us this history inherently. If you cannot replay and interrogate every probabilistic decision your system makes, you are flying blind.

This composability allows you to manage complexity and scale without centralized control. Thinking functionally about parallel, probabilistic processes takes significant effort.

#FunctionalProgramming #SoftwareEngineering #SystemArchitecture #DevSky #Tech #Dataflow #Backend

Model workflows functionally: map, reduce, aggregate. We are transforming information, not dictating steps. A reduce operation shouldn't be a monolith; it should dynamically expand into a sequence of dependent reducer tasks at runtime based on the data shape.