AI is not an architect (yet)
AI tools are part of our daily workflow. They help us move faster, explore ideas, and reduce friction.
But there is an important line they don't cross.
Without a programmer, Viper would not exist.
Architecture is responsibility, not generation
AI can generate code. It can suggest patterns. It can explain concepts.
What it cannot do is take responsibility for a system.
Architecture is about:
- understanding constraints
- predicting failure modes
- choosing trade-offs
- living with the consequences
Those decisions don't live in prompts. They live in production.
While building Viper, we faced problems that look small on the surface — but become critical in real-world conditions.
For example:
Reliable messaging at "1 bar" connectivity
- unstable connections
- partial packet loss
- delayed acknowledgements
- duplicated or out-of-order messages
There is no "AI answer" to this. You have to design, test, break, and redesign.
Incoming and outgoing message guarantees
- delivery confirmation
- retry logic
- idempotency
- consistency between local and remote state
AI can describe these concepts. It cannot decide how much reliability is enough without killing UX.
Offline mode
Offline is not a feature. It's a separate system state.
You need to think about:
- queues
- conflict resolution
- local persistence
- recovery after reconnect
No prompt tells you where your system will break.
Chat UI issues
This was one of the most painful areas:
- scroll jumps
- message prepending
- restoring visual position
- async layout updates
On paper — trivial. In practice — weeks of work.
Where AI actually helped
To be clear — AI was useful:
- generating boilerplate
- exploring alternatives
- sanity-checking ideas
- speeding up iterations
But every critical decision:
- protocol behavior
- message flow
- architecture in general
…was made by a human.
Conclusion
AI accelerates engineers. It does not replace them.
Especially when systems:
- operate under poor networks
- must work offline
- need predictable behavior
AI is not an architect — yet.
First published December 19, 2025 on the old Viper Foundation blog; moved here November 19, 2026. All posts