Craft

This is the story behind the plugins you're using. 

Blueprint first. That's how I learned the engine. Didn't want to dive into the C abysses and get the raptures of the deep - just nodes and tweaks to get what I wanted my way. 

Stopped several times due to life's call and started anew. But I always reached the same realization: to manage data correctly, things were really missing. I decided to delve into the depths of the Blueprints to stay sound to my initial vows. I built a Blueprint plugin that was doing miracles. All that was in 5.0 a couple of months ago. Then came new functionalities I wanted to incorporate but that meant upgrading to 5.5. I went this road and saw my great performances metrics just fall apart. Couldn't believe it was happening - it was hell - because I was going into a dead-end road. The plugin would have worked great in 5.0 but failed miserably in further releases. 

Don't know why but I dived into the blue. Down into the dark and cold water of the engine. 

Nine months later with the help of several AIs and my knowledge of the trade, several plugins are in the pipeline. 

So now a couple of words about the red AI pill. At first I cross-checked all the code that was generated. That was fine but along the way I realized that using several AIs did that job better than I could. I hence decided to switch my dev cap for the hat of the artist, the designer, the architect and the engineer. And I have worn many other hats these last months.

Be aware that not scrutinizing the whole code doesn't mean I skip this task but rather that I have put in place rigorous processes to thoroughly test what I ship.

I might finally have swallowed this pill. 

You're not buying code written by an AI. You're buying decisions made by someone who dived deep, learned the hard way, and built systems to ensure what ships actually works.

Will you go for the red or the blue ?