Good. I see your interest. 😊

Let's do this. 100 fires 🔥 on this post, and I'll run a free mini-course right here on Telegram on how to write Shorts Monster

Let's get started.

We can base our Shorts bot on the Shorts creation technology described by 10x income in this video.

Where should we start when implementing such a task? With decomposing the task into smaller steps.

In our case, the initial decomposition might look like this:

1. Writing the script
2. Dividing the script into scenes
3. Writing prompts to generate images for each scene
4. Generating AI images
5. Downloading video footage from stock
6. Generating voiceovers
7. Generating the video

In the future, these steps could become separate modes of the bot. In the end, we will also create a unified mode that will combine the entire pipeline.

Next, we need to determine what classes will be present in our bot.

Next, we need to define the classes of our bot. Here are a couple of simple rules to help with that.

For this, we need to:

1. Identify the actors
2. Consider the Single Responsibility Principle (SRP)

An actor is an entity that interacts with the system or performs certain actions within the system. For example, Writer, Downloader, Generator, etc.

Let’s take our task decomposition and match each point to the corresponding actor.

1. Writing the script - ScriptWriter
2. Dividing the script into scenes - ScriptDivider
3. Writing prompts to generate images for each scene - PromptsWriter
4. Generating AI images - ImageGenerator
5. Downloading video footage from stock - FootageDownloader
6. Generating voiceovers - VoiceGenerator
7. Generating the video - VideoGenerator

In the next post, we will analyze our potential classes in terms of SRP.

SRP. The first principle of SOLID.

This principle states that a class should perform a specific task and should not be overloaded with other unrelated tasks.

Just as a function should execute only one complete task, this principle applies to classes as well.

However, unlike functions, it’s harder to define the boundary of violating this principle with classes.

So, use common sense and avoid extremes:

1. Don’t create classes that do too much (the God Object anti-pattern).
2. But also, creating a multitude of classes with just one method inside may also not be the best practice.

...

So, let’s take another look at our potential classes and consider their responsibilities.

1. Writing the script - ScriptWriter
2. Dividing the script into scenes - ScriptDivider
3. Writing prompts to generate images for each scene - PromptsWriter
4. Generating AI images - ImageGenerator
5. Downloading video footage from stock - FootageDownloader
6. Generating voiceovers - VoiceGenerator
7. Generating the video - VideoGenerator

We can definitely say that each of the classes — ScriptDivider, ImageGenerator, FootageDownloader, VoiceGenerator, and VideoGenerator — has its own distinct responsibility. Each class performs its specific task, aligning with the SRP principle.

What about the ScriptWriter and PromptsWriter classes? At first glance, it might seem that their responsibilities overlap (writing text), and we could combine these two classes into a single Writer class without violating SRP.

In reality, these classes deal with different aspects of text, and their roles do not overlap. Each has its own distinct task. Therefore, it’s correct to keep these classes separate, which will align with the SRP principle.

Thus, our list of classes looks like this:

1. ScriptWriter
2. ScriptDivider
3. PromptsWriter
4. ImageGenerator
5. FootageDownloader
6. VoiceGenerator
7. VideoGenerator

After our classes are defined, it’s time to:

1. Create the bot’s basis
2. Plan the folder and file structure of the project

100 fires 🔥 on this post, and we’ll continue.

Let's continue.

What characteristics should our bot have?

First of all, it should support multiple projects.

This means its folder structure should look something like this.

Since the process and results of the work of each of our classes depend on the project folder, we see that all our classes have a common element — the project working directory.

In addition to this, different classes may have other common functionality, such as reading or writing data to CSV files or a database.

To avoid code duplication (the DRY principle) and to facilitate project maintenance, let's use inheritance to extract the common elements of our child classes into a separate parent class (base class).

Thus, we introduce an additional class, which we will call BaseGenerator.

We will inherit our classes from this base class, allowing us to access its attributes and methods from the child classes.

Therefore, our inheritance hierarchy looks like this.

⬆️ This architecture will be sufficient for our project.

We could also build the architecture using interfaces, abstract classes, and contracts, but I don't want to overcomplicate things or overload you with information right now.

I can explain this separately in the future, but for now, this will be enough.

Where will we store our classes? We'll create a package called modules, and inside it, we’ll create a .py file for each class.

Additionally, we’ll create a main.py file in the root of the project. This file will serve as the entry point to the application and will contain the logic for launching the different modes of the bot.

We’ll also need a data folder in the bot, where various global project files can be stored, such as the keyfile.json file for integrating the bot with Google Sheets.

Thus, our project structure will look like this.

We created a similar bot structure in lesson 4 of the Pinterest Money course. In that lesson, you’ll also learn how to build a prompt builder, and connect the bot to Google Sheets.

Take note of the module structure above.

For each class corresponding to a separate task, we have created a separate .py file (module).

Don’t think that only one class can be created in a single .py file.

You can also create additional classes in the same file if they are closely related to the task of the main class.

So, the recommendation is:

One file — one task.

This makes the code easier to read and maintain.

At this stage, we have created the structure of our bot and the class hierarchy.

The next step is to create the skeleton of our classes and the bot's launch logic.

Let's start with the base class. In the file base_generator.py, we'll declare the BaseGenerator class and then create the class constructor (the init method).

Earlier, we determined that a common element among our child classes will be the project working folder.

Therefore, in the constructor of the base class, we need to accept a variable containing the project folder name (project_folder) as an argument.

Then, we'll create an instance attribute (self.project_folder) and assign it the path to the project folder, formed using the os module.

Additionally, it would be a good idea to create attributes for the paths to other project folders in the base class and ensure their automatic creation (self.generated_images, self.generated_video).

In this class, we will also create methods for reading and writing CSV files, which will be needed for our child classes.

An example implementation of this class might look like this (image).

Note how we form paths to directories in accordance with the predefined folder structure.

Now let's move on to the child classes.

We'll create a skeleton for ScriptWriter. The structure for the other child classes will be created following the same principle.

In the script_writer.py file, declare the ScriptWriter class and inherit it from the base class BaseGenerator.

Create the class constructor. Since we need to pass the project_folder argument to the BaseGenerator parent class constructor, we must first accept it in the ScriptWriter child class constructor. Let's do that.

To pass project_folder to the parent class, we need to call the parent class constructor. This is done using the super() function.

Call the parent class constructor using super() and pass the project_folder parameter.

* I will provide the code a bit later

Note that instance attributes of the child class ScriptWriter should be created after calling the super() function, as this is related to the initialization order of the base and child classes.

When your child class inherits functionality from a base class, the base class attributes need to be initialized before adding attributes in the child class.

When creating an object (instance) of ScriptWriter, the initialization order will be as follows:

1. The constructor of the ScriptWriter child class is called first.
2. Then, the constructor of the BaseGenerator parent class is called via super(). At this point, all parent class attributes are initialized.
3. Then, the constructor of the child class continues, where the child class attributes are initialized.

Next, after the class constructor, we will declare a method that will trigger the execution of the main task of the class. Let's name it execute and leave it empty for now.

Each of the child classes will have a method with this name, but it will have its own unique implementation for each class.

The creation of the skeleton for our classes is now complete.

Following the same principle, create the structure for the remaining child classes, changing only the class name.

Next, we'll move on to developing the bot's launch logic.

In the main.py file, we will implement the management of different operation modes for the bot.

Here's what we'll do:

1. Import our classes.
2. Add functions to run individual steps, each of which will create an instance of the corresponding class and call its execute method.
3. Add a function to run the full pipeline, which will sequentially execute all the steps.
4. Create a menu to select the bot's operation mode.