AI Is My Workforce, Not My Replacement

In his pursuit of progress, the developer acknowledges the need to incorporate AI into their workforce rather than relying solely on their own abilities. With a multitude of projects to build, including KiwiEngine, Blackwater Sound, music software, artist platforms, and more, the creator recognizes that dedicating all 24 hours of a day to individual implementation is impractical. Instead, they opt to leverage AI tools to accelerate progress and bring their ideas to life.

The developer emphasizes that while there is merit in learning tools and mastering a specialty, it is not a one-size-fits-all approach to professional development. Some individuals choose to specialize deeply in an engineering field, work for established companies, or become language and framework experts. However, the developer's primary goal is to build, extend beyond software development, and use software as a tool to turn their vision into reality.

One of the key lessons the creator has learned is that they are a big thinker, capable of seeing systems, connections, and potential synergies between various projects. They can envision how a music business, software platform, storefront, and electronics workshop could operate together and have been successful in implementing their ideas for KiwiEngine.

However, the limitation lies in their inability to personally execute every idea at the pace they envision it. With only a limited number of hours in a day and no large engineering department to assist, the developer sees AI as a means to extend their capacity.

The essential distinction they draw is between AI's role in helping implement established patterns and AI's authority to make decisions independently. The developer maintains clear boundaries, ensuring AI does not commit code, alter architectural direction, or make decisions on their behalf. Instead, AI assists with implementation, repetitive work, documentation, tests, and other time-consuming tasks while the developer retains ultimate responsibility for the project's direction and outcome.

The creator also emphasizes that not every programming task demands equal levels of creative investment. Repetitive implementation work, such as writing adapters, creating tests, updating documentation, or implementing common patterns, should be delegated to AI, freeing up the developer's time to focus on more intellectually stimulating aspects of the project.

By doing so, they avoid the pitfalls of avoiding engineering work by using AI as a crutch and ensure that AI does not become a means to circumvent the need for understanding code.

Ultimately, the developer is not striving to win a coding endurance competition. Rather, they seek to move faster, enhance their work, and minimize the accumulation of problems through the judicious use of AI. AI should be a tool to complement their skills, rather than a replacement for their expertise.