Written by: Hunter Malm (Owner) Last Updated: October 8, 2026
TLDR: Vortex, Docuriser, and node.you were largely AI-written during a vibe-coding period in 2026, and I'm reworking them by hand. Since Layers 3.0, I write my code by hand and use AI for advising, review, and debugging.
AI is a rapidly developing technology, and I'm still learning how to properly adapt it into my workflow, so the opinions reflected in this document may change as the tools do.
Layers and the UI design that became Vortex date back to 2018 (source control since 2021), so their core ideas were in development well before AI tooling. I didn't start using AI until late 2023, when I wanted help pivoting the Layers project from a Qt desktop project into a cross-platform UI-agnostic theme framework, which eventually led to the decoupling of the UI and the declarative data language I was creating along the way (although I didn't know how to define it at the time).
I originally used AI only as an adviser. That changed in April 2025 with the initial development of Docuriser, where I decided to see what AI was capable of at the time. I still did the GUI-side work, since that was my domain, but I used AI to do most of the LLVM/libclang work for parsing C++ headers. I was impressed, and for the rest of the year, I continued using AI to solve some of the higher-level problems that previously stumped me with Layers and Vortex.
I used AI for learning hardware development for the Fetch totes around August 2025 after coming up with the idea while working grocery pickup. I already knew Blender, so I didn't use AI at all for the design of the tote model or its electronics housing. And I obviously didn't use AI to build the physical 3D-printed prototypes. For Fetch, I used AI to learn how power can be shared between devices by forming a rail between each connector (one with power incoming, and one outgoing) and branching to the device's MCU. I also used AI to understand how UART works to transfer data from TX to RX pins.
In January 2026, I leaned into vibe-coding with my new node.you project (node.you won't be released until further review). I used AI to develop the API, and eventually developed separate Vortex-Android and Vortex-Web ports for node.you's front-end. Unfortunately, those Vortex platform-specific ports began to drift and became difficult to maintain. Plus, requiring separate codebases meant that Vortex wasn't cross-platform, it was portable, which wasn't as appealing. In June 2026, I used AI to refactor those ports into the current cross-platform Vortex project with preventing drift as a real constraint. While creating the refactor, I used AI to rewrite Docuriser and the node.you client apps which helped drive the Vortex refactor.
With my Layers 3.0 development in August 2026, I decided to return to hand-written development, writing the new lexer, parser, loader, and associated engine changes entirely by hand, and using AI for advice and review. I also wrote the new spec, guides, and API reference documentation. Going forward, I will apply the same standard to my other projects.
I currently use AI for advising, review, and debugging complex issues. I occasionally take suggested code snippets from AI, but I reshape them to better fit my context and style. I do not plan to accept any more vibe-coding with my projects.
Contributors can use AI tools in the same manner described above: for advising, review, and debugging. If it is clear that your contribution was vibe-coded, I'll ask you to rework it.
For questions, contact us at:
Huntr Software LLC
8735 Dunwoody Place, STE N
Atlanta, GA 30350
Email: support@huntrsoftware.com