DEV Community: Tunmise Timothy Olayemi

My thought

Tunmise Timothy Olayemi — Fri, 13 Mar 2026 10:39:44 +0000

Tunmise Timothy Olayemi

Mar 13

I Think Generative AI Is Another Tool in the Economic Arms Race, Not a True Equalizer

Comments

2 min read

I Think Generative AI Is Another Tool in the Economic Arms Race, Not a True Equalizer

Tunmise Timothy Olayemi — Fri, 13 Mar 2026 10:38:24 +0000

Everyone is celebrating generative AI as the great equalizer. The headlines scream, “Now anyone can create like a pro.” But the quiet truth lives somewhere in the margins, where most people do not look.

Imagine two creators. One has access to every premium AI tool with unlimited runs, priority features, and polished outputs at their fingertips. The other uses only free tiers with watermarked outputs and slow processing that barely keeps up with their ideas. Both have talent. Both have vision. But only one can iterate, experiment, and scale their work consistently.

This is not about skill. It is about execution power, who can afford time, experimentation, and infrastructure. Generative AI has not leveled the playing field. It has shifted the race to a different track and some are already ahead before the starting gun even fires.

Generative AI is not a magic equalizer. It is a tool that amplifies existing advantages. Professionals with subscriptions and resources will always have a head start. Emerging creators, no matter how talented, are quietly disadvantaged and most people will not admit it.

So what can creators do? Tools like Stable Diffusion or RunDiffusion can substitute premium tiers if you learn how to chain them effectively. Limitless outputs are tempting but thoughtful, intentional iterations often beat sheer volume. Communities can be a force multiplier. Sharing credits, co-creating, and exchanging techniques allows emerging creators to level the playing field in ways one person alone rarely can. Understanding how the tools work, how outputs scale, and how to combine multiple free tools strategically gives you an advantage even when you cannot pay for the top-tier subscriptions.

Generative AI is an arms race. But like every race, strategy, creativity, and persistence can give you a fighting chance even if you start with less.

The truth is uncomfortable but it is worth facing. The AI revolution is not automatically fair. Tools amplify existing advantages. What separates creators is how deeply they understand the system, how creatively they work within limitations, and how boldly they use what they have.

If you are an emerging creator struggling to keep pace, do not just chase the hype. Think, experiment, collaborate, and iterate smarter than the system expects. That is where real opportunity lives.

Securing and Managing Cloud Storage for Private and Public Data with High Availability

Tunmise Timothy Olayemi — Thu, 03 Oct 2024 03:32:02 +0000

As companies grow, managing storage across offices and departments becomes increasingly important. Ensuring that sensitive company data is kept private, while still being accessible to authorized partners, is crucial. Additionally, backing up public-facing content ensures that websites remain secure and operational.

In this article, we’ll walk through creating a cloud storage architecture that provides high availability, secures private corporate data, allows controlled external access, and automates data tiering to reduce costs. We'll also explore how to back up public website data to ensure redundancy.
Assuming The company needs storage for their offices and departments. This content is private to the company and shouldn’t be shared without consent. This storage requires high availability if there’s a regional outage. The company wants to use this storage to back up the public website.

Skilling tasks
Create a storage account for the company private documents.
Configure redundancy for the storage account.
Configure a shared access signature so partners have restricted access to a file.
Back up the public website storage.
Implement lifecycle management to move content to the cool tier.
Exercise instructions
Note: These instruction require you to have completed Lab 02a, Provide storage for internal documents.

Create a storage account and configure high availability.
Create a storage account for the internal private company documents.
In the portal, search for and select Storage accounts.
Select + Create.
Select the Resource group created in the previous lab.
Set the Storage account name to private. Add an identifier to the name to ensure the name is unique.
Select Review, and then Create the storage account.

Wait for the storage account to deploy, and then select Go to resource.
This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy.

In the storage account, in the Data management section, select the Redundancy blade.
Ensure Geo-redundant storage (GRS) is selected.

Refresh the page.
Review the primary and secondary location information.
Save your changes.
Create a storage container, upload a file, and restrict access to the file.
Create a private storage container for the corporate data.

In the storage account, in the Data storage section, select the Containers blade.
Select + Container.
Ensure the Name of the container is private.

Ensure the Public access level is Private (no anonymous access).
As you have time, review the Advanced settings, but take the defaults.
Select Create.

For testing, upload a file to the private container. he type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publically accessible.

Select the container.
Select Upload.
Browse to files and select a file.
Upload the file.

Select the uploaded file.
On the Overview tab, copy the URL.

Paste the URL into a new browser tab.
Verify the file doesn’t display and you receive an error.
An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS). Learn more about Shared Access Signatures.

Select your uploaded blob file and move to the Generate SAS tab.
In the Permissions drop-down, ensure the partner has only Read permissions.
Verify the Start and expiry date/time is for the next 24 hours.
Select Generate SAS token and URL.

Copy the Blob SAS URL to a new browser tab.
Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded.
Configure storage access tiers and content replication.
To save on costs, after 30 days, move blobs from the hot tier to the cool tier. Learn more how manage the Azure Blob storage lifecycle.

Return to the storage account.
In the Overview section, notice the Default access tier is set to Hot.

In the Data management section, select the Lifecycle management blade.
Select Add rule.

Set the Rule name to movetocool.
Set the Rule scope to Apply rule to all blobs in the storage account.
Select Next.

Ensure Last modified is selected.
Set More than (days ago) to 30.
In the Then drop-down select Move to cool storage.
As you have time, review other lifecycle options in the drop-down.
Add the rule.

The public website files need to be backed up to another storage account.[Learn more about object replication.

In your storage account, create a new container called backup. Use the default values. Refer back to Lab 02a if you need detailed instructions.

Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.
In the Data management section, select the Object replication blade.
Select Create replication rules.
Set the Destination storage account to the private storage account.
Set the Source container to public and the Destination container to backup.
Create the replication rule.

Optionally, as you have time, upload a file to the public container. Return to the private storage account and refresh the backup container. Within a few minutes your public website file will appear in the backup folder.

Building a Secure and High-Performance File Sharing System for Distributed Corporate Offices Using Azure Files

Tunmise Timothy Olayemi — Thu, 03 Oct 2024 03:19:11 +0000

In today's globalized business environment, organizations with geographically dispersed offices need reliable and secure ways to share files across departments. One such organization requirement is the Finance department’s need to share cost information for auditing and compliance purposes. The file sharing solution must ensure fast access to files, limit access to select virtual networks for security, and provide safeguards such as snapshots for file recovery.

In this article, we'll walk through setting up an Azure Files storage account that caters to the corporate office's needs, including file shares, directory structures, access control using virtual networks, and snapshot capabilities for data recovery.

The company is geographically dispersed with offices in different locations. These offices need a way to share files and disseminate information. For example, the Finance department needs to confirm cost information for auditing and compliance. This file shares should be easy to access and load without delay. Some content should only be accessed from selected corporate virtual networks.
Create and configure a storage account for Azure Files.
Create a storage account for the finance department’s shared files.
Learn more about storage accounts for Azure Files deployments.

In the portal, search for and select Storage accounts.
Select + Create.
For Resource group select Create new. Give your resource group a name and select OK to save your changes.
Provide a Storage account name. Ensure the name meets the naming requirements.
Set the Performance to Premium.
Set the Premium account type to File shares.
Set the Redundancy to Zone-redundant storage.
Select Review and then Create the storage account.
Wait for the resource to deploy.

Select Go to resource.
Create and configure a file share with directory.
Create a file share for the corporate office. Learn more about Azure File tiers.

In the storage account, in the Data storage section, select the File shares blade.
Select + File share and provide a Name.

Review the other options, but take the defaults.
Select Create
Add a directory to the file share for the finance department. For future testing, upload a file.

Select your file share and select + Add directory.
Name the new directory finance.

Select Browse and then select the finance directory.
Notice you can Add directory to further organize your file share.
Upload a file of your choosing.

Configure and test snapshots.
Similar to blob storage, you need to protect against accidental deletion of files. You decide to use snapshots. Learn more about file snapshots.

Select your file share.
In the Operations section, select the Snapshots blade.
Select + Add snapshot. The comment is optional. Select OK.

Select your snapshot and verify your file directory and uploaded file are included.
Practice using snapshots to restore a file.

Return to your file share.
Browse to your file directory.
Locate your uploaded file and in the Properties pane select Delete. Select Yes to confirm the deletion.
Select the Snapshots blade and then select your snapshot.
Navigate to the file you want to restore,
Select the file and the select Restore.
Provide a Restored file name.
Verify your file directory has the restored file.

Configure restricting storage access to selected virtual networks.
This tasks in this section require a virtual network with subnet. In a production environment these resources would already be created.
Search for and select Virtual networks.
Select Create. Select your resource group. and give the virtual network a name.
Take the defaults for other parameters, select Review + create, and then Create.
Wait for the resource to deploy.
Select Go to resource.
In the Settings section, select the Subnets blade.
Select the default subnet.
In the Service endpoints section choose Microsoft.Storage in the Services drop-down.
Do not make any other changes.
Be sure to Save your changes.

The storage account should only be accessed from the virtual network you just created. Learn more about using private storage endpoints..

Return to your files storage account.
In the Security + networking section, select the Networking blade.
Change the Public network access to Enabled from selected virtual networks and IP addresses.
In the Virtual networks section, select Add existing virtual network.
Select your virtual network and subnet, select Add.
Be sure to Save your changes.

Select the Storage browser and navigate to your file share.
Verify the message not authorized to perform this operation. You are not connecting from the virtual network.

Building a Reliable, High-Availability Storage Solution for Your Public Website

Tunmise Timothy Olayemi — Fri, 20 Sep 2024 15:09:07 +0000

In today’s digital age, managing a growing customer base means providing seamless access to mission-critical content like product images, videos, marketing materials, and customer success stories. For companies with global audiences, ensuring low-latency access and high availability of website resources is vital to keeping customers engaged and satisfied.

At the same time, managing document versions and being able to restore accidentally deleted files is crucial to maintaining smooth operations. This is why creating a high-availability storage solution with proper version control and data recovery options is a must for any modern company.

Here’s why this setup is so important:

**High Availability for Global Demand: **With demand expanding worldwide, your storage solution must guarantee that content remains available even in the event of regional outages. This ensures uninterrupted service and user satisfaction.

**Effortless Content Management: **Your website needs to provide public, anonymous access to resources like images and documents without requiring users to log in, allowing customers to quickly and easily access your content.

**Version Control and Restoration: **Having the ability to track document versions and restore deleted content ensures that even if something goes wrong, your data can be quickly recovered, minimizing downtime and errors

Let Me Show You How
Let’s dive into the step-by-step procedure to set up this robust storage solution on Azure, ensuring high availability, public access, version control, and recovery features.
Problem Statement
The company website supplies product images, videos, marketing literature, and customer success stories. Customers are located worldwide and demand is rapidly expanding. The content is mission-critical and requires low latency load times. It’s important to keep track of the document versions and to quickly restore documents if they’re deleted.

Skilling tasks
Create a storage account with high availability.
Ensure the storage account has anonymous public access.
Create a blob storage container for the website documents.
Enable soft delete so files can be easily restored.
Enable blob versioning.

Exercise instructions
Create a storage account with high availability.

Create a storage account to support the public website.

In the portal, search for and select Storage accounts.
Select + Create.

For resource group select new. Give your resource group a name and select OK.
Set the Storage account name to publicwebsite. Make sure the storage account name is unique by adding an identifier.
Take the defaults for other settings.
Select Review and then Create.

Wait for the storage account to deploy, and then select Go to resource.
This storage requires high availability if there’s a regional outage. Additionally, enable read access to the secondary region, Learn more about storage account redundancy.

In the storage account, in the Data management section, select the Redundancy blade.
Ensure Read-access Geo-redundant storage is selected.

Review the primary and secondary location information.
Information on the public website should be accessible without requiring customers to login.
In the storage account, in the Settings section, select the Configuration blade.
Ensure the Allow blob anonymous access setting is Enabled.
Be sure to Save your changes.

Create a blob storage container with anonymous read access
The public website has various images and documents. Create a blob storage container for the content. Learn more about storage containers.
In your storage account, in the Data storage section, select the Containers blade.
Select + Container.

Ensure the Name of the container is public.
Select Create.

Customers should be able to view the images without being authenticated. Configure anonymous read access for the public container blobs. Learn more about configuring anonymous public access.
Select your public container.
On the Overview blade, select Change access level.

Ensure the Public access level is Blob (anonymous read access for blobs only).
Select OK.

Practice uploading files and testing access.
For testing, upload a file to the public container. The type of file doesn’t matter. A small image or text file is a good choice.
Ensure you are viewing your container.
Select Upload.
Browse to files and select a file. Browse to a file of your choice.
Select Upload.
Close the upload window, Refresh the page and ensure your file was uploaded.
Determine the URL for your uploaded file. Open a browser and test the URL.

Select your uploaded file.
On the Overview tab, copy the URL.
Paste the URL into a new browser tab.
If you have uploaded an image file it will display in the browser. Other file types should be downloaded.
Configure soft delete
It’s important that the website documents can be restored if they’re deleted. Configure blob soft delete for 21 days. Learn more about soft delete for blobs.
Go to the Overview blade of the storage account.
On the Properties page, locate the Blob service section.
Select the Blob soft delete setting.

Ensure the Enable soft delete for blobs is checked.
Change the Keep deleted blobs for (in days setting is 21.
Notice you can also Enable soft delete for containers.

Don’t forget to Save your changes.
If something gets deleted, you need to practice using soft delete to restore the files.
Navigate to your container where you uploaded a file.
Select the file you uploaded and then select Delete.
Select OK to confirm deleting the file.

On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.
Select your deleted file, and use the ellipses on the far right, to Undelete the file.
Refresh the container and confirm the file has been restored.

Configure blob versioning
It’s important to keep track of the different website product document versions. Learn more about blob versioning.
Go to the Overview blade of the storage account.
In the Properties section, locate the Blob service section.
Select the Versioning setting.

Ensure the Enable versioning for blobs checkbox is checked.
Notice your options to keep all versions or delete versions after.
Don’t forget to Save your changes.

As you have time experiment with restoring previous blob versions.
Upload another version of your container file. This overwrites your existing file.
Your previous file version is listed on Show deleted blobs page.

The Necessity of Setting Up Temporary Storage Solutions for IT Department Training and Testing

Tunmise Timothy Olayemi — Fri, 20 Sep 2024 14:04:13 +0000

In today's rapidly evolving technological landscape, IT departments need to stay ahead of the curve by constantly prototyping, testing, and training personnel on new tools and storage configurations. Having a sandbox environment where teams can freely experiment with different storage setups without the concern of backup, data durability, or high availability is essential. This is especially true for training environments where the primary goal is to learn, and any data used or created in the process is not critical for long-term retention.

When prototyping or conducting training, the need for a simple, cost-effective storage configuration becomes apparent. Not only does this help streamline IT operations, but it also ensures that departments can experiment with various storage scenarios without the overhead of implementing more complex solutions.

Here’s why a basic storage setup is crucial for your IT department:

Flexibility in Testing and Training: A dedicated storage space allows IT personnel to simulate real-world storage scenarios and train new team members. This can involve the creation of storage accounts, testing redundancy settings, or configuring security features.
Cost-Effectiveness: Since the data in these environments isn't critical, a low-cost storage configuration without high availability or durability is a smart choice. This allows teams to focus on learning and testing, not worrying about backing up non-essential data.
Customizable and Easy to Configure: With platforms like Microsoft Azure, creating and configuring a storage account for testing and training purposes is simple. You can adjust key settings like security, networking, and redundancy with just a few clicks, giving your team the flexibility they need for different scenarios.
Hands-On Learning: Configuring your own storage setup allows IT personnel to gain hands-on experience with cloud technologies, preparing them for more complex configurations in live production environments.

Let Me Show You How
Now that we understand the necessity of temporary storage setups for IT training and testing, let me walk you through the process of creating and configuring a simple, flexible, and cost-effective storage account on Microsoft Azure:

Skilling tasks

Create a storage account.
Configure basic settings for security and networking. Exercise instructions a. Create a resource group and a storage account. Create and deploy a resource group to hold all your project resources. Learn more about resource groups. In the Azure portal, search for and select Resource groups.
Select + Create. Give your resource group a name. For example, storagerg. Select a region. Use this region throughout the project. Select Review and create to validate the resource group.

Select Create to deploy the resource group.

b. Create and deploy a storage account to support testing and training. Learn more about the types of storage accounts.
In the Azure portal, search for and select Storage accounts.

Select + Create.

On the Basics tab, select your Resource group.

Provide a Storage account name. The storage account name must be unique in Azure.
Set the Performance to Standard.
Select Review, and then Create.

Wait for the storage account to deploy and then Go to resource.

Configure simple settings in the storage account. The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired. Learn more about storage account redundancy. In your storage account, in the Data management section, select the Redundancy blade.

Select Locally-redundant storage (LRS) in the Redundancy drop-down.
Be sure to Save your changes.

Refresh the page and notice the content only exists in the primary location.
The storage account should only accept requests from secure connections. Learn more about requiring secure transfer from secure connections
In the Settings section, select the Configuration blade.

Ensure Secure transfer required is Enabled.

Developers would like the storage account to use at least TLS version 1.2. Learn more about transport layer security (TLS).
In the Settings section, select the Configuration blade.
Ensure the Minimal TLS version is set to Version 1.2.

Until the storage is needed again, disable requests to the storage account. Learn more about disabling shared keys.

In the Settings section, select the Configuration blade.
Ensure Allow storage account key access is Disabled.
Be sure to Save your changes.

Ensure the storage account allows public access from all networks.
In the Security + networking section, select the Networking blade.

Ensure Public network access is set to Enabled from all networks.

Be sure to Save your changes.

Exploring Key Concepts in Cloud Computing: Virtualization, Scalability, Agility, and More

Tunmise Timothy Olayemi — Sat, 14 Sep 2024 11:15:26 +0000

Cloud computing has fundamentally reshaped the way businesses and individuals use technology. From storing data to running applications, everything can now be done over the cloud, with unprecedented flexibility and efficiency. But beneath the surface, cloud computing is built on several core concepts, including virtualization, scalability, agility, high availability, and fault tolerance. These technologies and techniques ensure that cloud infrastructures are scalable, resilient, and globally accessible. This article breaks down these concepts and explains how they impact the performance, flexibility, and availability of cloud systems.

1. Virtualization
Virtualization is at the heart of cloud computing. It’s the process of creating virtual instances of physical hardware, enabling multiple virtual machines (VMs) to run independently on a single physical server. By doing so, virtualization optimizes resource utilization, reduces costs, and provides flexibility in scaling infrastructure.
For example, imagine you have a powerful server with 64GB of RAM and 16 CPU cores. Through virtualization, you can partition this server into multiple virtual machines, each allocated a portion of the server’s total resources. One VM might run a Linux server, while another runs a Windows application — all on the same physical hardware. This allows for much more efficient resource use compared to running a single workload on the server.
In a cloud environment, virtualization allows cloud providers to pool resources from physical hardware across multiple data centers and distribute them to users based on demand. This makes cloud services like Infrastructure as a Service (IaaS) possible, where customers can rent virtual servers on-demand without worrying about the underlying physical infrastructure.

2. Scalability: Growth Without Limits
Scalability is one of the most important features of cloud computing and refers to the ability of a system to grow or shrink its resources to handle increasing (or decreasing) workloads. This concept is crucial for cloud environments where demand can be unpredictable.
**Example: **Imagine an e-commerce site like Amazon. During regular days, a small set of servers may be enough to handle user traffic. But during peak times, such as Black Friday, the site needs to rapidly scale out by adding more servers to avoid performance bottlenecks or downtime.

In cloud platforms like AWS, Google Cloud, or Azure, horizontal scaling is more common since it allows services to handle massive traffic spikes without service degradation. Cloud platforms provide tools like auto-scaling, which automatically adjusts resources based on real-time traffic and demand.

3. Agility: Speed and Adaptability in the Cloud
Agility refers to the ability of a system to quickly adapt to changing requirements or conditions. In cloud computing, agility is often associated with the speed at which new resources can be deployed, applications can be scaled, or new features can be rolled out.
Example: Suppose a startup is launching a new mobile app and is unsure about the exact server requirements. Using cloud infrastructure, the startup can quickly provision resources based on initial estimates. If the app suddenly goes viral and traffic surges, the startup can immediately scale up its cloud infrastructure to meet demand, ensuring that users experience minimal latency or downtime.

Agility also enables rapid iteration and innovation. Developers can easily test new features, roll them out to production, and make adjustments based on user feedback without significant infrastructure overhead. This flexibility makes cloud infrastructure ideal for DevOps and CI/CD (Continuous Integration/Continuous Deployment) practices.

4. High Availability (HA): Minimizing Downtime, Maximizing Uptime
High availability (HA) is about ensuring that a system or service is available and operational for as much time as possible. In cloud environments, this means designing infrastructure with redundancies and failovers, so that if one component fails, another takes over without disrupting service.

To achieve high availability, cloud platforms use techniques like:

Redundancy: Having multiple instances of critical components (like servers or databases) running at the same time. If one component fails, the others continue to function.
Failover: Automatically switching to a backup system when the primary system fails. For example, in a web application, a load balancer might route traffic to healthy servers while unhealthy ones are automatically replaced.
Example: A financial trading platform, where even a few minutes of downtime can cost millions of dollars, would rely on a highly available cloud infrastructure to ensure that services remain accessible even during hardware failures or software bugs.

5. Fault Tolerance: A Step Beyond High Availability
Fault tolerance goes beyond high availability by allowing a system to continue operating even when some of its components fail. In a fault-tolerant system, redundancy is built into every aspect of the infrastructure so that failure of one or more components has no noticeable effect on the system’s overall performance.

Example: In distributed database systems like Amazon DynamoDB or Google Spanner, data is replicated across multiple servers and data centers. If one server fails or a data center goes offline, the system continues operating as if nothing happened because copies of the data are available elsewhere. Fault tolerance ensures zero downtime, even in the case of significant failures.

Fault tolerance is more complex and expensive to implement than high availability, but it is essential for mission-critical applications where downtime is unacceptable.

6. Global Reach: Delivering Services Around the World
Global reach refers to the ability of cloud services to be accessed by users from anywhere in the world. Cloud providers achieve this by distributing their data centers across various geographic regions and using Content Delivery Networks (CDNs) to cache and deliver content from servers closest to the user.

This ensures low-latency access and improves the overall user experience, no matter where the user is located.

Example: A social media platform like Facebook or Twitter must deliver content quickly to users in different parts of the world. By leveraging a global network of data centers and CDNs, these platforms can serve content with minimal latency, ensuring that users get a smooth, fast experience no matter where they are.

Global reach is particularly valuable for businesses looking to expand internationally without the need to invest in physical infrastructure in each new market.

7. Elasticity vs. Scalability: Understanding the Difference
Though often used interchangeably, elasticity and scalability are distinct concepts:

Scalability refers to the ability to add or remove resources to meet long-term growth or demands. It is usually planned, and resources are added in a controlled manner. Scalability ensures that a system can handle increasing workloads over time.

Elasticity is about automatically adjusting resources in real-time based on current workloads. Elastic systems can dynamically scale up or down based on sudden spikes or drops in demand.

Example: During a live-streamed global event, an elastic cloud platform would automatically allocate more resources as millions of users tune in. Once the event ends and demand decreases, the system automatically scales down to avoid paying for unused resources.

Cloud computing is built on a foundation of technologies and concepts that enable greater flexibility, reliability, and scalability than traditional IT infrastructures. Virtualization, scalability, agility, high availability, and fault tolerance all contribute to the ability of cloud platforms to meet the diverse needs of businesses and individuals around the world. Understanding these key principles will help you design, deploy, and manage cloud-based applications that are both robust and responsive to changing demands.