<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by 3rdSon on Medium]]></title>
        <description><![CDATA[Stories by 3rdSon on Medium]]></description>
        <link>https://medium.com/@3rdSon?source=rss-5608602a6c5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r1YSkDYKIXGQlhooZ15HSg.jpeg</url>
            <title>Stories by 3rdSon on Medium</title>
            <link>https://medium.com/@3rdSon?source=rss-5608602a6c5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 20 May 2026 06:21:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@3rdSon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Training AI to Predict Clinical Trial Outcomes: A 30% Improvement in 3 Hours]]></title>
            <link>https://pub.towardsai.net/training-ai-to-predict-clinical-trial-outcomes-a-30-improvement-in-3-hours-8326e78f5adc?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8326e78f5adc</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 10:29:55 GMT</pubDate>
            <atom:updated>2026-02-22T09:09:07.335Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgvHsTnu-t8Q4jSIS-Nj8w.jpeg" /></figure><p>Predicting whether a clinical trial will succeed or fail is notoriously difficult. Even experienced pharmaceutical analysts struggle with accuracy rates much better than a coin flip. But what if we could train an AI model to learn from thousands of past trials and improve its predictions?</p><p>I recently built a dataset of 1,366 clinical trial predictions and fine-tuned an 8B parameter language model to predict trial outcomes. This resulted to in a jump from 56% accuracy (barely better than guessing) to 73% accuracy, a 30% relative improvement. Here’s how I did it, what I learned, and why this matters for anyone working with prediction tasks.</p><h3>The Challenge: Making Predictions from Historical Data</h3><p>The pharmaceutical industry runs on uncertainty. When Eli Lilly announces a Phase 3 trial for a new obesity drug, analysts, investors, and competitors all ask the same question: <em>Will it succeed?</em></p><p>Traditionally, answering this question requires:</p><ol><li>Deep domain expertise in pharmacology</li><li>Knowledge of the company’s track record</li><li>Understanding of regulatory pathways</li><li>Access to clinical trial databases</li><li>Lots of time to research each case</li></ol><p>Even then, human experts achieve modest accuracy. The question I wanted to answer is, could an AI model learn these patterns automatically from historical data?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SoPnf6bHICvHPTmEY7hUKg.jpeg" /><figcaption><strong>Comparison chart — Baseline 56.3% vs Fine-tuned 73.3%</strong></figcaption></figure><h3>The Data Problem: Labels Are Expensive</h3><p>The biggest hurdle in building prediction models is getting labeled training data. Hiring medical experts to label thousands of clinical trial outcomes would cost tens of thousands of dollars and take months.</p><p>This is where I discovered <a href="https://www.lightningrod.ai/"><strong>Lightning Rod’s</strong> </a>approach to data generation. Instead of manual labelling, their SDK uses what they call the <strong>“Future-as-Label”</strong> methodology. This approach makes the future outcome of a historical event its label.</p><p>Here’s how it works:</p><ol><li><strong>Find old news:</strong> Articles from 2023 about clinical trials starting</li><li><strong>Generate questions:</strong> “Will Novo Nordisk’s Phase 3 trial meet endpoints by Q4 2024?”</li><li><strong>Auto-label outcomes:</strong> Search recent news (late 2024/2025) to find what actually happened</li><li><strong>Build dataset:</strong> Pair questions with verified outcomes</li></ol><p>It does this without the need for human labellers. The <a href="https://github.com/lightning-rod-labs/lightningrod-python-sdk"><strong>Lightning Rod Python SDK</strong></a> automatically finds the answers by searching for what happened later.</p><h3>Building the Dataset: 1,366 samples in 2 Minutes</h3><p>Using Lightning Rod’s Python SDK, I generated the dataset with a simple pipeline:</p><pre>from lightningrod import QuestionPipeline, NewsSeedGenerator, WebSearchLabeler<br>pipeline = QuestionPipeline(<br>    seed_generator=NewsSeedGenerator(<br>        start_date=datetime(2023, 1, 1),<br>        end_date=datetime(2024, 12, 31),<br>        search_query=[&quot;clinical trial Phase 3&quot;, &quot;FDA approval&quot;]<br>    ),<br>    question_generator=ForwardLookingQuestionGenerator(<br>        instructions=&quot;Generate binary questions about trial outcomes&quot;,<br>        examples=[<br>            &quot;Will Eli Lilly&#39;s obesity drug trial meet endpoints by Q4 2024?&quot;,<br>            &quot;Will the FDA approve Drug X by June 2024?&quot;<br>        ]<br>    ),<br>    labeler=WebSearchLabeler(confidence_threshold=0.7)<br>)<br>dataset = lr.transforms.run(pipeline, max_questions=2000)</pre><p>The SDK pulled news articles about clinical trials, generated forward-looking questions, and then searched for later outcomes. In about 10 minutes of compute time, I had 1,882 questions, with 72.6% successfully labeled, giving me 1,366 high-quality training examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ou_Z9ejPNV9C5MGLnj8sHg.png" /><figcaption><strong>Screenshot of sample dataset rows showing question, answer, confidence, etc, generated using Lightning Rod Python SDK</strong></figcaption></figure><p>Each example looked like this:</p><pre>Question: &quot;Will Novo Nordisk&#39;s CagriSema Phase 3 trial meet its <br>primary endpoints by December 31, 2024?&quot;<br>Answer: YES (1)<br>Confidence: 0.98</pre><p>The labels weren’t guesses; they were verified facts from published trial results and FDA announcements.</p><h3>The Experiment: Baseline vs Fine-Tuned Model</h3><p>I split the data into training (85%) and test (15%) sets, then ran two experiments:</p><h3>1. Baseline: Zero-Shot Prediction</h3><p>First, I tested <strong><em>Llama-3–8B</em></strong> without any training. I gave each question and asked it to predict 0 (failure) or 1 (success).</p><p><strong>Result: 56.3% Accuracy</strong></p><p>The model was essentially guessing, with a slight optimistic bias (it predicted “success” too often). I wasn’t surprised because the base model has no special knowledge of pharmaceutical industry patterns.</p><h3>2. Fine-Tuning: Teaching the Patterns</h3><p>Next, I fine-tuned the model using <strong><em>LoRA (Low-Rank Adaptation)</em></strong> on the training data. LoRA is a parameter-efficient method that adds small adapter layers instead of retraining the entire model.</p><p>The setup I used:</p><ul><li><strong>Model:</strong> Llama-3–8B with 4-bit quantization</li><li><strong>Method:</strong> LoRA fine-tuning via the Unsloth library</li><li><strong>Hardware:</strong> Free Google Colab T4 GPU</li><li><strong>Training time:</strong> ~21 minutes (3 epochs)</li><li><strong>Trainable parameters:</strong> Only 16M (0.2% of the model)</li></ul><p><strong>Result: 73.3% Accuracy</strong></p><p>The fine-tuned model correctly answered <strong>151 out of 206</strong> test questions, achieving <strong>73.3% accuracy</strong>. This represents a <strong>17-percentage-point improvement</strong> over the baseline, a <strong>30% relative performance gain </strong>achieved in just <strong>21 minutes of training</strong>. Notably, this was done using only <strong>0.2% of the model’s parameters</strong> over <strong>3 training epochs</strong>, demonstrating highly efficient improvement with minimal compute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ygWWkJZvchIiNIQjQwdoTw.png" /><figcaption><strong>Confusion Matrix Comparison of the Baseline Model and Fine-Tuned Model</strong></figcaption></figure><h3>What Did the Model Learn?</h3><p>The most interesting part wasn’t just the numbers; it was understanding <em>what patterns</em> the model discovered in the data.</p><h4>Pattern 1: Company Track Records Matter</h4><p>The model learned that pharmaceutical companies have different success rates. Questions mentioning Eli Lilly, Novo Nordisk, or Merck were more likely to be “YES” (success), while smaller biotech startups showed higher failure rates.</p><p>This makes sense because established companies have more resources, experience, and proven track records. The model picked this up automatically from the data.</p><h4>Pattern 2: Therapeutic Areas Have Different Success Rates</h4><p>Obesity and diabetes drugs showed ~68% success rates in the training data, while oncology trials succeeded only ~48% of the time. The model learned these differences without being explicitly told.</p><p>Cancer is harder to treat. Metabolic diseases have clearer biomarkers. The model internalized these domain patterns solely from examples.</p><h4>Pattern 3: Timeline Realism</h4><p>One surprising discovery is that the model learned to spot unrealistic timelines.</p><p>Example questions the model <em>corrected</em>:</p><ul><li>“Will <em>[Small Biotech]</em> complete Phase 3 in 6 months?” → Predicted NO (correctly)</li><li>“Will <em>[Unproven Drug]</em> get FDA approval in 3 months?” → Predicted NO (correctly)</li></ul><p>The baseline model didn’t know that Phase 3 trials typically take 18–24 months. The fine-tuned version learned this pattern from the data.</p><h4>Pattern 4: Better at Predicting Failures</h4><p>The baseline model showed an optimistic bias, predicting “success” 63% of the time. The fine-tuned model was better calibrated at 52%, closer to the actual distribution.</p><p>More importantly, it learned to identify red flags like:</p><ul><li>Aggressive timelines</li><li>Unproven mechanisms</li><li>Companies with poor track records</li><li>Challenging therapeutic areas</li></ul><p>All five examples of “most improved” predictions involved the baseline incorrectly predicting success, while the fine-tuned model correctly predicted failure.</p><h3>Why This Matters Beyond Clinical Trials</h3><p>While this experiment focused on pharmaceutical trial outcomes, the real contribution goes beyond healthcare. It demonstrates a <strong>practical, repeatable workflow for building specialized prediction models from real-world data</strong>.</p><p>At its core, the approach is straightforward:</p><ol><li><strong>Identify a prediction task</strong> with historical data</li><li><strong>Use temporal structure</strong> (what happened later becomes your label)</li><li><strong>Generate datasets automatically</strong> instead of manual labeling</li><li><strong>Fine-tune efficiently</strong> with LoRA on free GPUs</li><li><strong>Achieve meaningful improvements</strong> in hours, not months</li></ol><p>This same approach could work for:</p><ul><li><strong>Product launch predictions:</strong> “Will Company X release Product Y by Date Z?”</li><li><strong>Policy outcomes:</strong> “Will Bill ABC pass by Q2 2026?”</li><li><strong>Market events:</strong> “Will Stock X reach price Y by month Z?”</li><li><strong>Sports forecasting:</strong> “Will Team X make the playoffs this season?”</li></ul><p>Any domain with historical news or announcements, clear and verifiable outcomes, and sufficient examples can benefit from Lightning Rod’s <strong>Future-as-Label</strong> methodology.</p><p>It’s not limited to clinical trials; it serves as a scalable template for temporal prediction tasks across industries.</p><h3><strong>Technical Implementation Details</strong></h3><p>For developers interested in reproducing this:</p><h4><strong>Dataset Generation:</strong></h4><ul><li>Source: News articles via Lightning Rod SDK</li><li>Questions: 1,882 generated, 1,366 valid (72.6%)</li><li>Label confidence: Average 0.998, minimum 0.85</li><li>Time: ~3 minutes</li></ul><h4><strong>Model Training:</strong></h4><ul><li>Base model: Llama-3–8B</li><li>Method: LoRA (rank=16, alpha=16)</li><li>Quantization: 4-bit for memory efficiency</li><li>Epochs: 3</li><li>Batch size: 2 (effective 8 with gradient accumulation)</li><li>Hardware: Google Colab free tier (T4 GPU)</li><li>Time: ~21 minutes</li></ul><h4><strong>Evaluation:</strong></h4><ul><li>Test set: 206 questions (15% holdout)</li><li>Metric: Binary accuracy</li><li>Baseline: 56.3% (116/206)</li><li>Fine-tuned: 73.3% (151/206)</li><li>Improvement: +17.0 percentage points</li></ul><p>The full code and dataset are available on <a href="https://github.com/3rd-Son/clinical-trial-prediction-lora"><strong>GitHub</strong></a>, and the dataset is published on <a href="https://huggingface.co/datasets/3rdSon/clinical-trial-outcomes-predictions"><strong>Hugging Face</strong></a> for anyone who wants to reproduce or build on this work.</p><h3>Limitations and Future Work</h3><p>This isn’t a perfect crystal ball. The model still struggles with:</p><ol><li>Novel drug mechanisms not seen in training</li><li>Rare diseases with limited examples</li><li>External factors (regulatory changes, manufacturing issues)</li><li>Very recent trials without outcome data yet</li></ol><p>The 73% accuracy is a meaningful improvement over guessing, but it’s not prophecy. Think of it as moving from “coin flip” to “informed probability estimate.” For context, even experienced pharmaceutical analysts struggle to achieve accuracy above 65–70% in predicting trial outcomes.</p><p><strong>Future improvements could include:</strong></p><ul><li>Larger datasets (5,000+ examples)</li><li>Additional features (company financials, prior trial data)</li><li>Ensemble methods combining multiple models</li><li>Continuous updating as new outcomes emerge</li></ul><h3>Key Takeaways</h3><p>Three lessons from this project:</p><p><strong>1. Automated labeling scales:</strong> Manually labeling 1,366 examples would have taken weeks and cost thousands. Lightning Rod’s Future-as-Label approach did it in 3 minutes.</p><p><strong>2. Small models can specialize:</strong> You don’t need GPT-4 or Claude for domain-specific tasks. An 8B model, fine-tuned on focused data, achieved 73% accuracy on a challenging prediction problem.</p><p><strong>3. Historical data contains learnable patterns:</strong> Company track records, therapeutic area success rates, and timeline realism all emerged naturally from the training data. The model discovered what experts know from experience.</p><h3>Try It Yourself</h3><p>The tools I used are all publicly available:</p><ul><li><a href="https://github.com/lightning-rod-labs/lightningrod-python-sdk"><strong>Lightning Rod SDK</strong></a><strong>:</strong> Open-source Python library for dataset generation</li><li>Pre-trained Model: Skip training, use the fine-tuned model directly via <a href="https://huggingface.co/3rdSon/clinical-trial-lora-llama3-8b"><strong>Hugging Face</strong></a></li><li><strong>Unsloth:</strong> Free library for efficient LoRA fine-tuning</li><li><strong>Google Colab:</strong> Free GPU access for training</li><li><strong>Hugging Face:</strong> Free dataset and model hosting</li></ul><p>The barrier to entry for specialized AI models has never been lower. If you have a prediction task with historical data, you can build a custom model in a weekend.</p><p>The future of AI isn’t just giant general-purpose models; it’s also specialized models trained on focused, high-quality datasets for specific domains. This experiment is one example of what becomes possible when you combine automated data generation with efficient fine-tuning.</p><p>What prediction task would you build a model for?</p><p>The dataset is available on <a href="https://huggingface.co/datasets/3rdSon/clinical-trial-outcomes-predictions">Hugging Face</a>, and all code is on <a href="https://github.com/3rd-Son/clinical-trial-prediction-lora">GitHub</a>. Special thanks to <a href="https://www.lightningrod.ai/">Lightning Rod Labs</a> for their SDK that made this project possible.</p><p><strong>Resources:</strong></p><ul><li>🤖 <a href="https://huggingface.co/3rdSon/clinical-trial-lora-llama3-8b"><strong>Fine-tuned Model</strong></a></li><li>📊 <a href="https://huggingface.co/datasets/3rdSon/clinical-trial-outcomes-predictions"><strong>Dataset</strong></a></li><li>💻 <a href="https://github.com/3rd-Son/clinical-trial-prediction-lora"><strong>Code</strong></a></li></ul><p><em>Interested in building prediction datasets? Check out </em><a href="https://www.lightningrod.ai/"><em>Lightning Rod</em></a><em> or explore their </em><a href="https://huggingface.co/LightningRodLabs/datasets"><em>examples on Hugging Face</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8326e78f5adc" width="1" height="1" alt=""><hr><p><a href="https://pub.towardsai.net/training-ai-to-predict-clinical-trial-outcomes-a-30-improvement-in-3-hours-8326e78f5adc">Training AI to Predict Clinical Trial Outcomes: A 30% Improvement in 3 Hours</a> was originally published in <a href="https://pub.towardsai.net">Towards AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Practical AGI: Why 80% of Jobs in Key Industries Are at Risk and How to Prepare]]></title>
            <link>https://medium.com/@3rdSon/practical-agi-why-80-of-jobs-in-key-industries-are-at-risk-and-how-to-prepare-b061b98ab570?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b061b98ab570</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[agi]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 14:00:51 GMT</pubDate>
            <atom:updated>2026-01-30T14:00:51.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eN7trrDR1iSWTs0QPlfoXw.png" /></figure><p>In February 2025, a profound shift began rippling through corporate boardrooms worldwide. IBM laid off 8,000 employees, Microsoft eliminated 6,000 positions, and hundreds of smaller companies followed suit. This is not due to economic recession, but because artificial intelligence systems can now perform their jobs. This isn’t a distant dystopian future; it’s happening now. As we stand at the threshold of Artificial General Intelligence (AGI), we face an unprecedented transformation that will fundamentally reshape how humans work, earn, and contribute to the economy. The impact of AGI is not a matter of if, but when, and we must prepare for this inevitable disruption.</p><p>Artificial General Intelligence (AGI), also known as human-level AI, is a type of artificial intelligence that would match or surpass human cognitive abilities across any domain. It represents a quantum leap beyond today’s narrow AI systems because they would possess reasoning, problem-solving, and adaptability comparable to human intelligence. Rather than viewing AGI as a threat, we can see it as a tool with the potential to enhance our capabilities and lead to a more efficient, productive future.</p><p>We are all aware of the remarkable capabilities of AI systems such as ChatGPT and Claude in tasks like writing essays, analyzing data, and generating creative ideas. Now picture a future where ChatGPT can not only write for you but also manage your calendar, plan your meetings, and book your flights. You plug it into your vehicle, and it drives you safely to your destination. You take it into the kitchen, and it prepares any dish you want, learning new recipes instantly from the internet and adjusting them for your personal taste. That is what Artificial General Intelligence (AGI) represents: not just an assistant that follows commands, but a system that can understand context, make decisions, and autonomously perform any intellectual or physical task a human can.</p><p>Industry leaders confirm AGI’s imminent arrival. OpenAI CEO Sam Altman predicts 2025 as the year “AI agents join the workforce and materially change the output of companies.” Anthropic’s CEO forecasts that within five years, AI could eliminate 50% of entry-level white-collar jobs and spike unemployment by 10–20%.</p><p>This essay argues that AGI will soon replace approximately 80% of jobs in specific industries due to its superior performance in speed, accuracy, cost-efficiency, and 24/7 availability. Industries involving repetitive cognitive tasks, data processing, and predictable decision-making face the most significant risk. We will examine which sectors and jobs are most vulnerable, analyze the economic ramifications, and propose actionable strategies for individuals, companies, and governments to navigate this seismic transition.</p><h3><strong>Industries First Impacted by AGI</strong></h3><p>The initial wave of AGI disruption will not strike randomly across the economy. Specific industries have structural characteristics that make them especially vulnerable to automation: high volumes of repetitive tasks, rule-based decision-making processes, heavy reliance on data analysis, and standardised workflows. These industries are already experiencing significant AI adoption, making them the proving grounds for AGI’s transformative power.</p><h4><strong>Industry 1: Customer Service</strong></h4><p>The shift to AI-powered customer service is accelerating, driven by powerful data. A Tidio study projects that up to<a href="https://www.tidio.com/blog/ai-customer-service-statistics/?utm_source=chatgpt.com"> 95% of customer interactions could be handled by AI by 2025</a>, and their research also shows that <a href="https://www.tidio.com/blog/ai-customer-service-statistics/?utm_source=chatgpt.com">3 out of every four companies that introduce AI see sales increase by over 10%</a>. This aligns with Octonomy’s findings, which report that <a href="https://www.octonomy.ai/en/uncategorized/the-state-of-ai-in-customer-service-2025-the-ultimate-guide-for-it-decision-makers/?utm_source=chatgpt.com">55% of companies already deploy AI in customer service</a>. The economic incentive is undeniable, as Desk365 highlights, noting that <a href="https://www.desk365.io/blog/ai-customer-service-statistics/?utm_source=chatgpt.com">labour cost savings of up to 90% are possible when AI automates routine tasks</a>. You can also attest that most of the websites and products you use today use AI for customer service and refer you to a human only when needed. The economics are irresistible for companies because AI never gets tired, never takes breaks, scales instantly, and costs a fraction of what human labor does. While high-touch customer relationships that require empathy and complex problem-solving may remain human-centred, the vast majority of customer interactions follow predictable patterns that AGI handles more efficiently.</p><h4><strong>Industry 2: Manufacturing and Logistics</strong></h4><p>This industry has long been a target for automation, but AGI will take mechanization to an entirely new level. Industrial robots now account for <a href="https://thunderbit.com/blog/automation-statistics-industry-data-insights">44% of repetitive manufacturing tasks worldwide</a>, but AGI-powered systems will go beyond physical automation. They will optimise entire supply chains in real time, predict equipment failures before they occur, coordinate autonomous vehicles and drones, and make complex quality-control decisions that previously required human judgment.</p><p>Unlike previous waves of automation that required extensive reprogramming for new tasks, AGI systems are presumed to adapt to changing production requirements, handle exceptions, and continuously optimize processes once the purview of human supervisors.</p><h4><strong>Industry 3: Financial Services and Banking</strong></h4><p>Financial Services and Banking are experiencing a seismic shift as AGI algorithms handle transaction processing, fraud detection, risk assessment, and investment management with superhuman speed and accuracy. As of 2027, AI is expected to manage over $1.2 trillion in banking assets. Approximately one-third of transaction-handling roles in financial institutions have already been automated. Robo-advisors automatically adjust investment portfolios based on market conditions and client preferences, often outperforming manual fund managers in retail banking. Natural language interfaces are taking over front-desk roles in digital banking, assisting customers with account queries and product discovery. The financial sector is expected to automate 70% of basic operations by 2027, with significant job cuts on Wall Street as algorithms prove more reliable than traders at parsing market signals and executing strategies.</p><h4><strong>Industry 4: Healthcare Administration and Back-Office Operations</strong></h4><p>Healthcare Administration and Back-Office Operations represent another vulnerable sector. While doctors and nurses perform irreplaceable human-centered care, the administrative machinery of healthcare is ripe for automation. Medical transcription is expected to reach 99% automation, with 40% of medical coding automated by 2025. Insurance claim processing, appointment scheduling, billing reconciliation, and patient record management tasks that currently employ millions of people can be performed more accurately and more quickly by AGI systems. The result is a bifurcated healthcare workforce: hands-on caregivers remain essential, while administrative staff face widespread displacement.</p><h3><strong>Jobs at Highest Risk of AGI Automation</strong></h3><p>The displacement effect of AGI operates at the task level, not just the job level, but certain occupations face near-complete automation within the next five years. Understanding which jobs are most vulnerable and why is crucial for workforce planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wLMDTOdoYgJM33pKzCkL3g.png" /></figure><h4><strong>Why does AGI outperform humans in these roles? The advantages are multifaceted and decisive:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ubT79QaE97Rosdtoy6-glw.png" /></figure><p>Not all jobs are equally at risk of automation. Positions that require human judgment, creativity, and emotional intelligence, such as healthcare providers, skilled tradespeople, and creative professionals, are relatively safe because of their complexity. However, these roles will still evolve as professionals adopt AGI for tasks such as diagnostics and strategic analysis. The future involves collaboration between humans and machines, which may render some jobs redundant.</p><h3><strong>ECONOMIC IMPACT OF AGI</strong></h3><h4><strong>Short-Term Impacts (2025–2030): The Disruption Phase</strong></h4><p>The immediate economic effects will be painful and destabilizing. Research from the<a href="https://www.weforum.org/press/2020/10/recession-and-automation-changes-our-future-of-work-but-there-are-jobs-coming-report-says-52c5162fce/"> World Economic Forum predicts </a>that 85 million jobs will be displaced globally by 2025 and beyond, a staggering figure that signals turmoil across entire industries. In the United States, projections suggest that 30% of current jobs could be fully automated by 2030, while 60% will undergo significant task-level changes. These aren’t gradual shifts allowing smooth transitions; they’re rapid displacements concentrated in specific sectors.</p><p>Entry-level employment faces particularly acute pressure. Anthropic’s CEO predicts AI could eliminate 50% of entry-level white-collar jobs within five years, creating a “missing generation” problem in which young workers can’t gain the foundational experience that traditionally leads to senior positions. This hollowing out of entry-level roles threatens the entire career pipeline: if companies automate away junior positions, where do future managers and executives come from?</p><p>Unemployment will spike, but not uniformly. Projections suggest U.S. unemployment could peak in the high single digits among active labour market participants, with continental Europe potentially reaching the low double digits. Workers aged 18–24 are 129% more likely than those over 65 to worry that AI will make their jobs obsolete, and with good reason: entry-level positions face the highest automation rates. Women also face disproportionate risk, with 58.87 million women in the U.S. workforce in occupations highly exposed to AI automation compared to 48.62 million men.</p><p>Income inequality will likely widen dramatically in the short term. The wage gap between highly educated workers and others could explode as AI-literate professionals commanding premium salaries work alongside displaced workers competing for shrinking opportunities in low-skill service roles. One scenario envisions incomes for workers at the 90th percentile increasing by 15%, median wages staying flat, and bottom-quartile wages decreasing. This exacerbates existing wealth concentration, with capital owners who control AGI systems capturing disproportionate gains while labor’s share of national income declines.</p><h4><strong>Long-Term Impacts (2030–2050): The Transformation Phase</strong></h4><p>If we successfully navigate the transition, the long-term economic picture brightens considerably.<a href="https://www.goldmansachs.com/insights/articles/generative-ai-could-raise-global-gdp-by-7-percent"> Goldman Sachs projects that full AI adoption could boost U.S. labor productivity by 15% and global GDP by 7%</a>, a permanent increase in economic output equivalent to adding trillions of dollars to the global economy each year. More optimistic projections suggest AI could add $19.9 trillion to the global economy by 2030, with compound effects raising GDP by 1.5% by 2035, nearly 3% by 2055, and 3.7% by 2075.</p><p>This productivity revolution operates through multiple channels: AGI eliminates wasteful inefficiencies, optimizes resource allocation, accelerates innovation through AI-assisted research and development, and enables entirely new products and services that would be impossible without machine intelligence. Banks could increase pretax profits by 12–17% by 2027, totaling $180 billion. Industries exposed to AI experienced productivity growth, jumping from 7% to 27% between 2018 and 2024.</p><p>Crucially, the<a href="https://www.weforum.org/press/2020/10/recession-and-automation-changes-our-future-of-work-but-there-are-jobs-coming-report-says-52c5162fce/"> World Economic Forum predicts that while 85 million jobs will disappear by 2025, 97 million new roles will emerge</a>, a net gain of 12 million positions globally. These new jobs cluster in areas such as AI development and maintenance, AI ethics and governance, human-AI interaction design, data curation and management, and complex problem-solving that require human creativity and judgment. The question is whether displaced workers can transition to these new roles, which often require advanced education and technical skills.</p><h4><strong>Winners and Losers: The Distribution Challenge</strong></h4><p>The economic gains from AGI won’t be distributed evenly. Advanced economies with strong education systems, technological infrastructure, and adaptive institutions are positioned to capture disproportionate benefits. Developing nations risk being left behind if they lack the resources to implement AI or retrain their workforces. Within countries, geographic disparities will emerge: tech hubs like Silicon Valley, Boston, and Seattle will thrive as AI centers while regions dependent on automatable industries face decline.</p><p>Age-based divides will intensify. Older workers approaching retirement may ride out the transition, while young workers face careers requiring continuous reinvention. Gender disparities could widen given women’s concentration in administrative and clerical roles, facing high automation risk. Educational attainment becomes increasingly determinant of economic outcomes: 77% of AI-related jobs require master’s degrees and 18% require doctoral degrees, locking out workers without access to advanced education.</p><p>The central economic question is whether AGI leads to broadly shared prosperity or extreme concentration of wealth and power. Without intervention, market dynamics favor the latter: capital owners and highly skilled workers capture gains while everyone else faces declining opportunities. However, with appropriate policies, progressive taxation of AI profits, funded retraining programs, strengthened social safety nets, and a universal basic income, the productivity gains could be distributed more equitably.</p><p>Historical precedents provide mixed guidance. Previous technological revolutions, such as steam power, electricity, and computers, ultimately dramatically increased living standards, but the transitions involved decades of disruption, with winners and losers. AGI differs in speed (measured in years, not decades) and scope (affecting cognitive work, not just physical labor). The question is whether society can manage an exponentially faster transition with exponentially higher stakes.</p><h3>Preparation Strategies</h3><p>The AGI transformation is not a distant threat to be addressed eventually. It’s an immediate challenge requiring urgent action from individuals, companies, and governments. Those who adapt proactively will thrive, but those who delay face obsolescence.</p><h4>Individual Strategies: Future-Proofing Your Career</h4><h4><strong>1. Embrace Continuous Learning as a Lifestyle</strong></h4><p>The half-life of professional skills is shrinking rapidly. What you learned in college five years ago is increasingly irrelevant; what you’ll need five years from now doesn’t exist yet. Adopt a lifelong learning mindset and set aside time each week for skill development. This doesn’t necessarily mean returning to formal education. Micro-learning platforms like Coursera, LinkedIn Learning, and Google Career Certificates offer targeted, credential-bearing programs that take months, not years. The World Economic Forum projects that over 40% of workers will require significant upskilling by 2030; being in the vanguard of that transition provides a competitive advantage.</p><h4><strong>2. Develop AI Literacy Immediately</strong></h4><p>You don’t need to become a programmer, but you must understand how AI works, what it can and cannot do, and how to leverage it in your work. Familiarise yourself with tools such as ChatGPT, Claude, GitHub Copilot, and industry-specific AI applications. The workers who remain valuable aren’t those competing against AI, but those who use AI better than others. As one executive observed, “We’re not replacing workers with AI; we’re replacing workers who don’t use AI with workers who do.”</p><h4><strong>3. Build Skills Portfolios, Not Career Ladders</strong></h4><p>The traditional model, which climbs a hierarchical ladder within one company or industry, is obsolete. Instead, develop a portfolio of complementary skills allowing lateral moves across functions and industries. Employers increasingly hire based on demonstrated capabilities rather than years of experience or specific degree credentials. Leverage digital credentials, maintain an updated portfolio showcasing projects, and cultivate a professional network providing access to opportunities.</p><h4><strong>4. Consider Strategic Career Pivoting</strong></h4><p>If your current role faces a high risk of automation, begin planning a transition now rather than waiting for displacement. Identify adjacent roles that require similar foundational skills but pose lower automation risk. For example, data entry clerks might pivot to data quality management or customer success roles, and retail cashiers might transition to personal shopping advisory or e-commerce coordination. Employers and community colleges increasingly offer reskilling programs, so take advantage while you’re still employed.</p><h3>Company Strategies: Responsible AI Adoption</h3><h4><strong>1. Invest in Comprehensive Reskilling Programs</strong></h4><p>Companies that view employees as disposable costs to be automated away face long-term disadvantages because institutional knowledge evaporates, employer brands suffer, and social license erodes. Forward-thinking organizations invest substantial resources in workforce development. Amazon’s $700 million “Upskilling 2025” program aims to provide advanced skill training for more than 100,000 employees. IBM’s “New Collar” initiative focuses on skills-based hiring and internal mobility. These investments pay dividends through higher retention, greater employee engagement, smoother transitions to AI-augmented workflows, and preservation of institutional knowledge.</p><h4><strong>2. Redesign Work Around Human-AI Collaboration</strong></h4><p>Rather than simply replacing humans with machines, reimagine workflows that leverage the comparative advantages of both. AGI handles routine data processing, pattern recognition, and optimization while humans focus on strategic decision-making, relationship management, creative problem-solving, and ethical oversight. Create new roles like AI oversight managers, prompt engineers, and explainability specialists who bridge human and machine capabilities. This approach augments your workforce rather than eliminating it while achieving productivity gains.</p><h4><strong>3. Adopt AI Ethically and Transparently</strong></h4><p>Companies deploying AI without consideration for employee welfare and social impact face reputational risks, regulatory challenges, and employee resistance. Implement AI gradually with stakeholder input; provide clear communication about automation plans and support for affected workers; ensure AI systems are transparent and auditable; and establish ethics review boards to evaluate AI deployments. Responsible AI adoption builds trust and facilitates smoother transitions.</p><h4><strong>4. Cultivate a Culture of Adaptability</strong></h4><p>Organizations must become learning institutions where change is expected, skills development is prioritized, and experimentation is encouraged. This requires leadership commitment, demonstrated through resource allocation and role modelling; psychological safety that allows people to fail and learn; incentive systems that reward adaptability and learning; and continuous feedback mechanisms that enable rapid iteration. Companies with adaptive cultures weather technological disruption far better than rigid hierarchies.</p><h3>Government Strategies: Managing the Transition</h3><h4><strong>1. Reform Education Systems for the AI Era</strong></h4><p>Education systems for the industrial economy are outdated. Governments should overhaul curricula to focus on critical thinking, digital literacy, interdisciplinary problem-solving, and soft skills like communication, collaboration, creativity, and emotional intelligence. Countries like Singapore, Germany, and Canada are modernising their education systems; the U.S. needs similar reforms.</p><h4><strong>2. Establish Robust Retraining Infrastructure</strong></h4><p>The shift to an AGI economy needs massive investment in adult education and reskilling. Governments should fund accessible, subsidized training for high-risk workers, partner with colleges to develop relevant curricula, offer income support, and create digital skills passports. The Infrastructure Investment and CHIPS Acts allocate billions, but more is required.</p><h4><strong>3. Strengthen Social Safety Nets</strong></h4><p>During the transition phase, unemployment will spike and income inequality will widen without interventions. Governments must expand unemployment benefits with longer durations and higher payments, implement portable benefits not tied to specific employers, explore universal basic income pilots providing basic economic security, and strengthen progressive taxation to fund these programs. The Nordic countries offer models for comprehensive social insurance systems that cushion workers during transitions.</p><h4><strong>4. Regulate AI Development and Deployment</strong></h4><p>Unconstrained AI development risks racing toward AGI without adequate safety measures or societal preparation. Governments should establish AI safety standards and auditing requirements, mandate impact assessments for automation decisions that affect large workforces, protect workers’ rights to understand and contest AI decisions that affect them, and fund research on AI safety, alignment, and ethics. The <a href="https://page.bsigroup.com/eu-ai-act-meets-mdr-whitepaper?creative=766726693643&amp;keyword=eu%20ai%20act%20mdr&amp;matchtype=b&amp;network=g&amp;device=c&amp;utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=gl-rs-ai-lg-health-dt-mpd-mp-mdrwhitepaper-0025&amp;utm_content=766726693643&amp;utm_term=eu%20ai%20act%20mdr&amp;adposition=&amp;adgroup=183365388139&amp;gad_source=1&amp;gad_campaignid=22848730780&amp;gbraid=0AAAAA-IiRvYgUNx-wisse7dHUG_fMgHbc&amp;gclid=CjwKCAiAoNbIBhB5EiwAZFbYGPtj5cmTvikZapoIjNO6Pjya4P3QY_IZgwnH8vVeMcRPdUS6JgtLVBoC0-YQAvD_BwE">EU’s AI Act</a> provides a framework that other jurisdictions should adapt.</p><h4><strong>5. Promote Equitable Distribution of AI Benefits</strong></h4><p>Without intervention, AGI’s gains accrue primarily to capital owners. Governments can reshape these dynamics through progressive taxation of AI profits, funding social programs, equity ownership models that give workers a stake in AI-driven productivity, data sovereignty laws that ensure individuals control the data used to train AI systems, and antitrust enforcement to prevent AI monopolies. The goal is to ensure AGI benefits broad populations rather than further concentrating wealth.</p><h3>Conclusion</h3><p>We stand at an inflection point in human history. Artificial General Intelligence promises to be the most transformative technology of our era. The displacement of jobs in vulnerable industries, such as customer service, manufacturing, financial services, transportation, and healthcare, isn’t fear-mongering; it’s a likely outcome over the next decade. Entry-level positions face particular vulnerability, creating a “missing generation” problem, while economically, AGI presents both tremendous opportunity and serious risks. Without intervention, it risks exacerbating inequality to unprecedented levels.</p><p>The imperative for action is urgent. Individuals must embrace continuous learning and develop AI literacy. Companies must invest in workforce development and adopt AI responsibly. Governments must reform education, establish retraining infrastructure, and ensure equitable distribution of benefits. The choices we make now will determine whether AGI creates broadly shared prosperity or deepens societal divisions.</p><p>Like every disruptive innovation throughout history, AGI will displace some while enriching others. The mobile phone displaced call booths and telegrams, but it also revolutionized global communication. The automobile displaced horse-drawn carriages but transformed transportation and commerce. The internet displaced traditional retail but created unprecedented access to information and opportunity. In the same way, when managed wisely, AGI will displace many current roles while undoubtedly improving productivity, innovation, and the quality of life. The question is: are you ready, or are you working toward the right direction to avoid obsolescence and position yourself for opportunity? I leave that to you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b061b98ab570" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Choose the Right AI Framework for Your Use Case: A Practical Guide for Business Leaders]]></title>
            <link>https://medium.com/@3rdSon/how-to-choose-the-right-ai-framework-for-your-use-case-a-practical-guide-for-business-leaders-c8ff4a729e61?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8ff4a729e61</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai-automation]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 09:45:04 GMT</pubDate>
            <atom:updated>2026-02-12T12:40:30.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rJiAtNrfxp_Mjg0gb9_mNQ.png" /></figure><p>As a business leader, you’ve probably heard a lot about AI agents, autonomous systems designed to enhance customer support, streamline workflows, analyse data, and support your teams. The benefits are enticing: improved efficiency, lower costs, and enhanced customer experiences.</p><p>However, there’s a catch: not every AI framework is suitable for every situation. Choosing the wrong one can waste your budget, delay your projects, and frustrate your team. With new frameworks emerging regularly, navigating this complex landscape can feel overwhelming.</p><p>In this guide, we’ll cut through the noise and help you make informed decisions about building AI agents for your business. We’ll focus on what matters most: your team’s capabilities, your budget constraints, and your actual business needs, not just the technical hype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JPTRfqWoZ2i5K9dJ.png" /></figure><h3>The Real Questions Business Leaders Need to Ask</h3><p>Before diving into specific frameworks or tools, you need clarity on three fundamental questions:</p><p>1. Do we have the technical talent in-house, or will we need to hire?</p><p>2. What’s our realistic budget, not just for software, but for people and infrastructure?</p><p>3. What business problem are we actually solving?</p><p>Let’s break down how to answer these questions systematically.</p><h3>1. Assess Your Team’s Technical Capability</h3><p>The most critical decision you’ll make is whether to go with a no-code platform or a code-based framework. This isn’t about what sounds more impressive; it’s about matching your team’s actual capabilities to the tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/0*nse0xMaKFGK7hBNT.png" /></figure><h3>Do You Have Developers on Your Team?</h3><p><strong>If No: Go with No-Code Platforms</strong></p><p>If your team includes business analysts, operations managers, marketers, or other non-technical professionals, don’t require them to learn programming. Modern no-code tools are powerful enough to build sophisticated agents without writing code.</p><p><strong>Popular no-code options:</strong> n8n, Zapier, Copilot Studio, Voiceflow, Botpress, ChatFuel</p><p><strong>What this means for you as a leader:</strong></p><ul><li>Faster time to market (days or weeks, not months)</li><li>Lower upfront costs (no need to hire expensive AI developers immediately)</li><li>More ownership by business teams (they can iterate without waiting for IT)</li><li>Trade-off: Less customisation and flexibility as you scale</li></ul><p><strong>If Yes → Explore Code-Based Frameworks.</strong></p><p>If you already have developers, especially Python, JavaScript, or Java developers, you can leverage code-based frameworks that give you complete control and customisation.</p><p><strong>Popular coding frameworks:</strong> LangChain, CrewAI, LangGraph, AutoGen, Semantic Kernel, LlamaIndex</p><p><strong>What this means for you as a leader:</strong></p><ul><li>Higher upfront investment in developer time</li><li>Greater flexibility to customise agents to your exact needs</li><li>Ability to integrate deeply with existing systems and databases</li><li>Trade-off: Longer development cycles and higher maintenance overhead</li></ul><h3>2. Calculate the True Cost of Building AI Agents</h3><p>Budget conversations about AI agents often focus only on software licensing, and that’s a mistake. You need to account for the full cost of ownership.</p><h3>No-Code Platforms: Subscription + Scale Costs</h3><p>No-code platforms typically operate on freemium or subscription models. Here’s what to watch for:</p><ol><li><strong>Free tiers:</strong> Tools like n8n and Pipedream offer free or open-source versions, which are great for prototyping. However, as you scale, you’ll hit limits on executions, integrations, or team seats.</li><li><strong>Paid tiers:</strong> Platforms such as Zapier, Copilot Studio, and Voiceflow charge monthly fees that scale with usage. For example, Zapier charges $20–$ 2,000 per month, depending on the number of tasks and premium features. Copilot Studio starts at $200 per tenant per month, while Voiceflow ranges from $50 to $625+ per tenant per month, depending on team size and selected features.</li></ol><p>You should also watch out for some hidden fees. Fees like integration fees, data storage, API calls to LLMs (like OpenAI or Anthropic), and support packages can add up quickly, so you have to also watch out for these.</p><h3>Code-Based Frameworks: Developer Time + Infrastructure</h3><p>Code-based frameworks are usually free and open-source (LangChain, CrewAI, AutoGen), but your real costs are in people and infrastructure:</p><ol><li><strong>Developer salaries:</strong> AI-focused developers command premium rates. Expect $100K–$200K+ annually for experienced talent in major markets. If you’re hiring contractors, rates range from $75 to $250/hour.</li><li><strong>Development time:</strong> Building a production-ready agent can take 2–6 months, depending on complexity. That’s salary cost multiplied by timeline.</li><li><strong>Infrastructure costs:</strong> Once built, you’ll need hosting (AWS, Azure, GCP), monitoring tools, and database storage. For a moderately complex agent handling thousands of requests daily, expect $500–$5,000+/month in infrastructure.</li><li><strong>Ongoing maintenance:</strong> AI agents aren’t “set it and forget it.” They require monitoring, updates, and optimisation as your business needs evolve.</li></ol><p>As a business leader, here is what you have to ask yourself:</p><ul><li>Can we afford 3–6 months of developer time upfront, or do we need something running in weeks?</li><li>Are we prepared for ongoing costs, or do we need predictable monthly pricing?</li><li>Do we have internal resources to manage infrastructure, or should a platform handle that?</li></ul><p>These answers will help you decide whether to invest in no-code agility or code-based control.</p><h3>3. Match Your Use Case to the Right Tool</h3><p>Not every framework is built for every job. Some excel at conversational AI, others at data analysis, and still others at workflow automation. Choosing the wrong tool for your use case is like using a screwdriver to hammer a nail; it might work, but it’ll be painful. Below, we will outline where each of the tools we mentioned earlier fits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xud4Bazu9bbzBuhr.png" /></figure><h3>4. Evaluate Team Size and Governance Needs</h3><p>Your organisation’s size and structure should influence your framework choice, and here is how</p><ul><li><strong>Small Business or Startup (1–20 people): </strong>As a small business or startup, your primary focus should be on speed, low cost, and the flexibility to pivot quickly. At this stage, it’s more important to validate ideas than to build complex, fully custom systems. Your best approach is to use no-code platforms or lightweight code frameworks such as Zapier, n8n, or simple LangChain implementations. These tools allow you to build and test ideas rapidly without needing a dedicated AI development team. Since governance overhead can slow progress, keep it minimal: focus on delivering a functional solution, collect user feedback, and iterate.</li><li><strong>Mid-Market Company (20–500 people): </strong>For mid-sized companies, the focus shifts to scalability, system integration, and moderate customisation. You likely have some technical expertise on your team, but resources remain limited compared to those of large enterprises. The best approach is a hybrid model: use no-code platforms for simpler use cases, such as workflow automation or basic chatbots, and code-based frameworks for more complex, high-value projects, such as advanced data analysis or multi-system integration. Governance should be moderate, establish clear rules for who can build agents, how they are tested, and when they’re deployed to production, ensuring consistency without stifling innovation.</li><li><strong>Enterprise (500+ people): </strong>For large enterprises, priorities centre on security, compliance, scalability, and governance. The best approach is to adopt code-based frameworks with enterprise support, such as Semantic Kernel, SpringAI, LangChain4j, Google ADK, or AWS Strands. These frameworks provide the control, auditability, and integration capabilities required for large-scale, secure operations within enterprise infrastructure. Given the complexity and risk involved, governance must be robust, with formal approval processes, security reviews, compliance checks, and centralised monitoring in place to ensure AI systems align with corporate policies, data protection standards, and long-term strategic goals.</li></ul><h3>5. Consider Your Existing Tech Stack</h3><p>Don’t choose an AI framework in isolation. Consider what your team already uses and select a framework. The table below should help you make the right decision based on your existing tech stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PFfI35hAvNaXyPfK.png" /></figure><p>It’s best always to choose tools that leverage your existing investments rather than forcing your team to learn entirely new platforms.</p><h3>6. Prototype Fast, Then Scale Smart</h3><p>Here’s the approach that works for most business leaders:</p><p><strong>Phase 1: Validate with Prototypes (2–4 weeks)</strong></p><ul><li>Choose a small, well-defined use case</li><li>Build a lightweight prototype using the simplest tool that fits</li><li>Test with real users (internal team or select customers)</li><li>Measure concrete outcomes: time saved, tickets deflected, revenue impacted</li></ul><p><strong>Phase 2: Evaluate and Benchmark (1–2 weeks)</strong></p><ul><li>Assess: Did it actually solve the problem?</li><li>Measure: Speed, accuracy, cost per interaction, user satisfaction</li><li>Compare: Would a different tool/framework have worked better?</li></ul><p><strong>Phase 3: Scale or Pivot (Ongoing)</strong></p><ul><li>If successful: Invest in making it production-ready (better error handling, monitoring, security)</li><li>If unsuccessful: Quickly pivot to a different approach without having wasted months</li></ul><p><strong>Business leader tip:</strong> Don’t get caught in “analysis paralysis.” Select something reasonable based on the criteria above, test it quickly, and be prepared to adjust if needed.</p><h3>Your Decision Roadmap: A Quick Framework</h3><p>Now that we’ve covered all the key considerations, let’s consolidate them into a simple, actionable plan. Below is a decision architecture we’ve created to help you make your choice more quickly and easily. Think of this as your visual roadmap. Start at the top and follow the path that best matches your situation to narrow down your options systematically.</p><p>This flowchart consolidates all the information we’ve discussed into a single decision tree. Instead of juggling all the factors in your head, you can follow the branches that apply to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-EhGNoYS9bp-yiCI.png" /></figure><h3>Common Pitfalls Business Leaders Should Avoid</h3><p><strong>1. Choosing based on hype, not fit.</strong> Just because everyone’s talking about a framework doesn’t mean it’s right for your use case. Evaluate based on your specific needs.</p><p><strong>2. Underestimating maintenance,</strong> AI agents aren’t “set and forget.” Budget for ongoing monitoring, updates, and optimisation.</p><p><strong>3. Skipping the prototype phase.</strong> Going straight to a large-scale implementation without testing is risky. Start small, prove value, then scale.</p><p><strong>4. Ignoring change management.</strong> Even the best AI agent will fail if your team doesn’t adopt it. Invest in training and communication.</p><p><strong>5. Over-engineering early. </strong>Don’t build for every possible future scenario on day one. Build for today’s problem, then iterate.</p><h3>Wrap-Up</h3><p>Choosing the proper AI framework isn’t about finding the “best” tool in the abstract. It’s about finding the right fit for your business: your team’s capabilities, budget constraints, use case, and timeline.</p><p>The businesses that thrive with AI agents are those that progress thoughtfully yet swiftly, experimenting, learning, and adjusting rather than attempting perfection from the outset.</p><p>If you found this helpful, share your experiences and challenges. What framework are you considering, and what’s holding you back?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8ff4a729e61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Pivoted to DevRel and Technical Writing After 2 Years as an AI Engineer]]></title>
            <link>https://medium.com/@3rdSon/why-i-pivoted-to-devrel-and-technical-writing-after-2-years-as-an-ai-engineer-bc33ec6f1947?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc33ec6f1947</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ai-engineering]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[career-transitions]]></category>
            <category><![CDATA[technical-writing]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 00:51:12 GMT</pubDate>
            <atom:updated>2026-04-23T02:20:20.769Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Why I Pivoted to DevRel and Technical Writing After 3 Years as an AI Engineer</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLd0m2ihu1nSS3aN9jE65w.png" /></figure><p>Hi there,<br>Just a quick one today 🤗</p><p>After 3 years as an <strong>AI Engineer</strong>, I’ve built and deployed machine learning models, created agentic workflows, and worked across various Gen AI projects. And while I’ve genuinely enjoyed building, one thing became increasingly clear to me:</p><blockquote><em>I love writing about AI and explaining how things work just as much — if not more — than building them.</em></blockquote><p>That realisation led me down a new path — a full <strong>pivot into Developer Relations and Technical Writing</strong>, still within the AI space.</p><h3>The Pivot I Needed 🎯</h3><p>Although I still enjoy the engineering side of things, I’ve found deep fulfilment in <strong>communicating technical ideas</strong>, creating content, and helping other developers learn and build.</p><p>Over the past 10 months, I’ve worked as a <strong>Technical Writer at </strong><a href="https://app.readytensor.ai/"><strong>Ready Tensor</strong></a> — a pioneering media platform for AI and data science innovation.<br>There, I:</p><ul><li>Wrote articles on trending AI and ML topics</li><li>Engaged with the developer community</li><li><strong>Led the Agentic AI Developer Certification Program, </strong>a hands-on learning experience for over 500 learners</li></ul><p>This experience confirmed what I’d already felt: <strong>writing, community building, and teaching are not just skills I enjoy, they’re where I thrive.</strong></p><h3>What’s Next?</h3><p>I’m fully embracing my new path <strong>as a Technical Writer and DevRel Engineer</strong>, and I’m excited for what’s ahead.</p><p>From here on out, I’ll be writing more consistently about:</p><ul><li>AI, ML, and Generative AI</li><li>Data and Python</li><li>My career journey and lessons learned</li></ul><p>📩 <strong>Follow me here on Medium</strong> and hit the <strong>Subscribe</strong> button if you’d like to stay updated on my posts.<br>I’d love to bring you along as I grow and contribute in this new direction.</p><p>I won’t stop building though 🚀</p><p>Thanks for reading ✌️<br> — Victory Nnaji</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc33ec6f1947" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Add Memory to RAG Applications and AI Agents]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://python.plainenglish.io/how-to-add-memory-to-rag-applications-and-ai-agents-0066fe068755?source=rss-5608602a6c5a------2"><img src="https://cdn-images-1.medium.com/max/1273/1*q_iRk7WVjE4o6-2DpHtcMg.png" width="1273"></a></p><p class="medium-feed-snippet">Sometime in the last 5 months, I built a RAG application, and after building this RAG application, I realised there was a need to add&#x2026;</p><p class="medium-feed-link"><a href="https://python.plainenglish.io/how-to-add-memory-to-rag-applications-and-ai-agents-0066fe068755?source=rss-5608602a6c5a------2">Continue reading on Python in Plain English »</a></p></div>]]></description>
            <link>https://python.plainenglish.io/how-to-add-memory-to-rag-applications-and-ai-agents-0066fe068755?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0066fe068755</guid>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Sun, 27 Oct 2024 09:04:23 GMT</pubDate>
            <atom:updated>2026-02-19T22:16:29.115Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Generative AI Engineering; An Overview]]></title>
            <link>https://medium.com/@3rdSon/generative-ai-engineering-an-overview-6b63dbc4ebbb?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b63dbc4ebbb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[generatve-ai]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Sat, 13 Jul 2024 17:53:39 GMT</pubDate>
            <atom:updated>2025-07-25T00:38:43.163Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there,</p><p>A quick one today 🤗</p><p>I’ve been working as a Gen AI Engineer for over 1 and a half years now, and I’ve come to some realisations:</p><blockquote>The first one is that AI Engineering isn’t a well-defined field yet and the requirements or tasks vary based on the needs of the company/project at hand.</blockquote><blockquote>Secondly, An AI Engineer is a blend of a data scientist, machine learning engineer, and software engineer, particularly in backend development.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_GSXnX-U4alPZCG_" /></figure><h3>Why do I say so?</h3><ol><li>As an AI Engineer, you either use pre-built APIs or train your models, thus taking on the role of a <em>machine learning engineer</em>.</li><li>As an AI Engineer, you’ll handle large datasets — cleaning, transforming, or otherwise manipulating them — tasks typically done by a <em>data scientist or analyst.</em></li><li>You’ll also develop APIs, manage backend tasks, and uphold software engineering principles, akin to a <em>software engineer</em>. This involves making API calls, integrating various APIs, processing data at the backend, and working with databases before exposing results to the frontend.</li></ol><p>So, if you’re building AI systems, be ready to wear multiple hats. You’ll tackle various exciting challenges and make them work. Remember, you’re a blend of an ML engineer, a data scientist, and a software engineer.</p><blockquote>Thanks for reading ✌️</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b63dbc4ebbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build RAG applications with Pinecone serverless, OpenAI, Langchain and Python]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@3rdSon/how-to-build-rag-applications-with-pinecone-serverless-openai-langchain-and-python-d4eb263424f1?source=rss-5608602a6c5a------2"><img src="https://cdn-images-1.medium.com/max/1600/1*WhN3E2yqDVIxJkxmptfmSQ.png" width="1600"></a></p><p class="medium-feed-snippet">I wrote this article so that by following my steps and my code samples, you&#x2019;ll be able to build RAG apps with Pinecone, python and OpenAI</p><p class="medium-feed-link"><a href="https://medium.com/@3rdSon/how-to-build-rag-applications-with-pinecone-serverless-openai-langchain-and-python-d4eb263424f1?source=rss-5608602a6c5a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@3rdSon/how-to-build-rag-applications-with-pinecone-serverless-openai-langchain-and-python-d4eb263424f1?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4eb263424f1</guid>
            <category><![CDATA[pinecone]]></category>
            <category><![CDATA[langchain]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Wed, 08 May 2024 00:22:33 GMT</pubDate>
            <atom:updated>2026-02-19T22:18:11.424Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Learn Python in 2024?]]></title>
            <link>https://medium.com/@3rdSon/why-learn-python-in-2024-0cfb30c2def0?source=rss-5608602a6c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0cfb30c2def0</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[2024]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[python-programming]]></category>
            <dc:creator><![CDATA[3rdSon]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 23:00:14 GMT</pubDate>
            <atom:updated>2023-12-18T23:00:14.392Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MWwGHjDwn4pgqso3xo05DA.jpeg" /></figure><p>Python is a high-level, general-purpose <em>programming language</em> known for its readability, simplicity, popularity and versatility.</p><h3>Let’s break it down</h3><p>If you haven’t heard of Python before, I would want you to picture Python as a toolbox containing various tools that can be used for various works.</p><p>If you’ve ever seen a toolbox, you know it houses various tools. There are the cutting tools like scissors, measuring tools like rulers and tape, fastening tools like screws, and many others. These tools are utilised as needed, each serving different purposes. Whether you’re a DIY enthusiast, a mechanic, or anyone else, these tools cater to a range of tasks and roles.</p><h3>Over to Python</h3><p>Python, as a programming language, provides a variety of tools, commonly referred to as methods, functions, libraries, or frameworks. Similar to a regular toolbox where you decide what task you want to accomplish and then choose the appropriate tool, Python operates similarly. You need to comprehend your objective and select the specific framework, library, method, or function that can assist you in achieving it. Use that chosen tool to execute the task.</p><h3>So why should I learn Python in 2024?</h3><p>Beyond its widespread popularity, Python is extensively utilized in numerous companies, making it a valuable skill in various tech fields. If you’re looking to enter the tech industry and are uncertain about the advantages of learning Python, consider the following tech fields where Python knowledge can be advantageous. I will be listing but a few of them.</p><ol><li><strong>Data Science:</strong> Data science is the field of extracting insights and knowledge from data using scientific methods, statistics, and algorithms to make informed decisions and predictions. Python, along with libraries such as <strong>Pandas, NumPy, and Scikit-learn</strong>, is extensively used for data analysis, machine learning, and artificial intelligence.</li><li><strong>Web Development</strong>: Web development is the process of creating and maintaining websites or web applications, involving tasks such as designing, coding, and organizing content for online platforms. Popular frameworks like <strong>Django and Flask</strong> make Python a go-to choice for building web applications.</li><li><strong>Cybersecurity</strong>: This is the practice of protecting computer systems, networks, and data from theft, damage, or unauthorized access. Python is employed for ethical hacking, penetration testing, and developing security tools.</li><li><strong>Machine Learning and AI:</strong> AI is the broader concept of creating machines or software that mimic human intelligence. Machine Learning is a subset of AI, focusing on developing algorithms that enable machines to learn from data and improve their performance over time. Libraries like TensorFlow and PyTorch leverage Python for developing and implementing machine learning models.</li><li><strong>Data Engineering: </strong>Data Engineering is the process of designing and building systems to handle and organize large amounts of data effectively. Python is employed in data engineering tasks, including data pipeline development and ETL (Extract, Transform, Load) processes.</li><li><strong>DevOps</strong>: DevOps is a collaborative approach that combines development (Dev) and operations (Ops) to streamline and automate the software development and delivery process, fostering quicker and more reliable releases. Python scripts are commonly used in DevOps for automation, infrastructure as code, and configuration management.</li></ol><p>In conclusion, learning Python in 2024 is a strategic move given its widespread popularity and demand across various tech fields. The language’s versatility positions aspiring techies for success, making Python a valuable asset for those aiming to thrive in technology. Python’s user-friendly syntax makes it an ideal choice for beginners, providing an accessible entry point for those new to the world of programming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0cfb30c2def0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>