🤖 Integrating AI into Development Workflows
Artificial Intelligence has become one of the most polarizing technologies of the modern era. For some, it represents a powerful productivity tool. For others, it represents a flood of low-effort content, automation, and misinformation.
Much of this divide comes from the fact that “AI” is often discussed as if it were a single thing. In reality, there is a significant difference between generative AI and assistive AI.
Generative AI is often used to create large volumes of content with minimal human involvement. This is where concerns about “AI slop” originate—automatically generated articles, videos, images, and social media content that prioritize quantity over quality.
Assistive AI is different.
Rather than replacing human thought, assistive AI helps organize information, accelerate workflows, reduce repetitive tasks, and make complex projects more manageable.
This site uses AI in the second sense.
AI is not used as a replacement for judgment, creativity, research, organization, or decision-making. Instead, it serves as a development partner that helps transform ideas into systems more efficiently than would otherwise be possible.
🖼️ AI on the Main Site vs AI on the Dev Site
An important distinction exists between the main site and the development site.
The primary site is not built around AI-generated content.
In fact, much of the content exists through curation, selection, organization, and contextual relationships between sources rather than original essays or generated material.
The site consists largely of:
- Song lyrics
- Quotes
- Excerpts
- References
- Images
- Books
- Films
- Concepts
- Narrative structures
The creative process is often less about generating content and more about selecting, arranging, connecting, and contextualizing information.
While I may write more original content in the future, the core purpose of the site remains rooted in organization, interpretation, and relationship mapping rather than AI-generated writing.
The development site serves a different purpose.
Here, AI is frequently used to assist with:
- Documentation
- Project planning
- Architecture discussions
- Technical problem solving
- Development logs
- Workflow organization
- Code reviews
- Refactoring discussions
Even in these cases, AI is used as a collaborative tool rather than an automated author.
The goal is not to eliminate thinking.
The goal is to improve it.
🛠️ AI as a Development Partner
One of the biggest misconceptions about AI-assisted development is the idea that AI simply writes software for people who do not understand technology.
That has not been my experience.
Long before AI became part of this project, I had already spent years working with:
- Computers
- Operating systems
- Linux environments
- Networking
- Security concepts
- Troubleshooting
- Technical documentation
- Information systems
Those experiences created the foundation that allows AI to be useful in the first place.
AI did not suddenly make complex development possible.
Instead, it removed many of the barriers that traditionally separate ideas from implementation.
The largest of these barriers is often syntax.
Historically, implementing an idea required:
- Research
- Documentation
- Forums
- Trial and error
- Language-specific syntax knowledge
- Repeated debugging
AI dramatically shortens that process.
This allows more time to be spent on:
- Architecture
- Planning
- Organization
- System design
- Documentation
- Testing
- Refinement
For a project of this scale, that shift has been transformative.
🧠 Why Tools Matter
Throughout the history of computing, new tools have consistently changed how people build things.
Compilers removed the need to write everything in machine code.
Frameworks removed the need to build every component from scratch.
Content management systems removed the need to manually create every page.
AI represents another step in that progression.
Using a tool does not eliminate skill.
It changes where skill is applied.
The challenge shifts from memorizing syntax to understanding systems.
From writing every line manually to designing architectures that solve real problems.
The value increasingly comes from judgment, organization, planning, and the ability to understand how individual components fit into a larger whole.
🚀 A Platform That Would Not Exist in Its Current Form Without AI
Perhaps the most significant impact AI has had on this project is not coding.
It is scale.
This site originally began as a simple WordPress installation containing standard posts and pages.
The original goal was straightforward:
Collect and organize interesting content that would otherwise be difficult to explain repeatedly.
Over time, however, recurring patterns began to emerge.
The same artists appeared repeatedly.
The same lyrics appeared repeatedly.
The same concepts appeared repeatedly.
The same references appeared repeatedly.
Eventually, a new question emerged:
“What kind of thing is this information?”
That question fundamentally changed the direction of the project.
The challenge was no longer publishing content.
The challenge became organizing knowledge.
As the platform evolved, new systems appeared:
- Custom Post Types
- Custom taxonomies
- Relationship structures
- Reference systems
- Footnotes
- Content models
- Shared templates
- Reusable components
- Navigation systems
- Portal architecture
The project gradually transformed from a website into a structured knowledge platform.
While none of these systems were created automatically by AI, AI significantly accelerated the process of planning, testing, documenting, refining, and implementing them.
The result is a platform that would have taken substantially longer to build through traditional self-study alone.
🏗️ From Content Management to Information Architecture
One of the most unexpected lessons from this project has been the difference between managing content and managing knowledge.
At the beginning, the site consisted largely of content entries.
Over time, the focus shifted toward relationships.
Questions became increasingly architectural:
- How should concepts connect to references?
- How should songs connect to artists?
- How should themes connect to narratives?
- How should information be discovered?
- How should knowledge be organized?
The platform began evolving into something much larger than a traditional blog.
It became an ongoing exercise in:
- Information architecture
- Knowledge organization
- Content modeling
- Documentation
- Long-term maintenance
- System design
AI played an important role in helping explore these questions, test ideas, and evaluate alternative approaches.
📚 Toward a Dynamic Knowledge Framework
One of the long-term goals of the platform is the creation of increasingly dynamic and interconnected content systems.
Using technologies such as:
- Advanced Custom Fields Pro
- Custom Post Types
- Taxonomies
- Relationship fields
- Shared templates
- Custom queries
the platform can generate meaningful connections between different forms of content.
Examples include:
- Philosophers
- Authors
- Artists
- Books
- Films
- Lyrics
- Quotes
- Concepts
- Themes
- References
These systems are not intended to generate content automatically.
Instead, they create pathways through existing knowledge.
The goal is not automation for its own sake.
The goal is discovery.
🗺️ Documenting the Platform
As the platform has grown, another challenge has emerged:
Understanding the architecture itself.
Many of the site’s systems were developed over the past year through experimentation, iteration, refactoring, and continuous improvement.
Because of this, a new documentation initiative is currently underway.
The purpose of this initiative is to document how a standard WordPress installation evolved into a structured knowledge platform through:
- Custom development
- Information architecture
- Content modeling
- Automation
- AI-assisted planning
- Long-term iteration
Future documentation will explore topics such as:
- WordPress foundations
- Theme architecture
- Parent themes versus child themes
- Custom Post Type design
- ACF relationships
- Shared templates
- Helper functions
- Portal systems
- Footnotes
- Taxonomies
- Development workflows
- Git integration
- AI-assisted development
A major focus of this effort will be the creation of visual architecture diagrams that explain both the physical structure of the codebase and the logical structure of the knowledge systems built on top of it.
The goal is not simply to document code.
The goal is to document the thinking process behind the platform.
🔭 Looking Ahead
The project continues to evolve.
New content systems, relationship structures, navigation methods, portal designs, and documentation initiatives are constantly being explored.
AI will remain part of that process.
Not as a replacement for human judgment, but as a tool that helps accelerate experimentation, organization, and implementation.
Ultimately, the most important lesson from this project is that AI is not most valuable when it generates finished products.
It is most valuable when it helps people build things that would otherwise be too large, too complex, or too time-consuming to create alone.
For this platform, AI has not replaced creativity, architecture, or development.
It has amplified them.