At a recent SXSW session, Ian Beacraft, CEO of Signal and Cipher, presented a compelling vision of the future workplace—one that demands continuous learning and adaptability. Central to his message was the idea of the rapidly shrinking half-life of skills. Today, technical skills are estimated to last only 2.5 years before becoming outdated, a stark decrease compared to the past.
The diagram visualizes the shrinking half-life of skills over time, highlighting how rapidly technical competencies become outdated. It contrasts the decreasing lifespan of relevant skills (currently around 2.5 years) with the growing need for continuous, agile learning methods. The visual emphasizes the risk of traditional, slow-paced training methods becoming obsolete and illustrates the necessity for companies to adopt flexible, micro-learning approaches to remain competitive and innovative in the modern workplace.
This concept aligns closely with my previous insights into organizational efficiency and innovation, particularly around the dangers of running teams at 100% utilization. Classical queue theory demonstrates that when utilization approaches full capacity, wait times and bottlenecks increase dramatically. For knowledge work, this manifests as a loss of innovation, adaptability, and essential skills development.
In an environment of near-constant technological evolution, companies that fill every available hour with immediate productivity leave no room for the critical learning and upskilling necessary to stay competitive. The future belongs to organizations that deliberately balance productivity with learning, recognizing that skill development isn’t an extracurricular activity—it’s foundational to future success.
As skills continue to expire faster than ever, running at full utilization isn’t just inefficient; it’s a direct threat to your company’s relevance. To thrive in this new reality, the approach to learning and up-skilling within companies must fundamentally change. Traditional courses with formal diplomas and structured online training from established vendors will increasingly struggle to keep pace with the rapid evolution of skills. Instead, bite-sized, just-in-time learning content available through the web, YouTube, and other micro-learning platforms will become essential.
Ian Beacraft highlighted a striking prediction: the cost of training and upskilling employees will soon eclipse the cost of technology itself. If you have SMEs in your company this is something you have to think hard about solving so that you can manage these costs effectively and maintain competitive edge in an era where skill requirements evolve rapidly.
Recent developments, such as OpenAI’s foundational grants to universities, signal an emerging divide between those with AI access and those without. These grants are not just an academic initiative—they will accelerate disparities in AI capabilities, favoring institutions that can freely explore and integrate AI into research and innovation. The same divide is already forming in the corporate world.
Software engineers today are increasingly evaluating companies based on their AI adoption. When candidates ask in interviews whether an organization provides tools like GitHub Copilot, they are not just inquiring about productivity enhancements—they are assessing whether the company is on the cutting edge of AI adoption. Organizations that restrict AI access risk falling behind, unintentionally categorizing themselves into the “B Team,” making it harder to attract top talent and compete effectively.
Lessons from Past Industrial Revolutions
History provides clear lessons about the importance of accessibility in technological revolutions. Electricity, for example, was initially limited to specific industrial applications before it became a utility that fueled industries, powered homes, and transformed daily life. Similarly, computing evolved from expensive mainframes reserved for large enterprises to personal computers and now cloud computing, making advanced technology available to anyone with an internet connection.
AI should follow the same path.
However, excessive corporate governance could hinder its progress, while governmental governance remains essential to ensure AI is developed and used safely. Just as electricity transformed from an industrial novelty to the foundation of modern society, AI must follow a similar democratization path. Imagine if we had limited electricity to only certified engineers or specific departments—we would have stifled the innovation that brought us everything from household appliances to modern healthcare. Similarly, restricting AI access today could prevent us from discovering its most transformative applications tomorrow.
Governance Should Enable, Not Block
The key is not to abandon governance but to ensure it enables rather than blocks innovation. AI governance should focus on how AI is used, not who gets access to it. Restricting AI tools today is akin to limiting electricity to specialists a century ago—an approach that would have crippled progress.
The most successful AI implementations are those that integrate seamlessly into existing workflows. Tools like GitHub Copilot and Microsoft Copilot demonstrate how AI can enhance productivity when it is embedded within platforms that employees already use. The key is to govern AI responsibly without creating unnecessary friction that prevents widespread adoption.
The Competitive Divide is Already Here
The AI accessibility gap is no longer theoretical—it is already shaping the competitive landscape. Universities that receive OpenAI’s foundational grants will advance more rapidly than those without access. Companies that fully integrate AI into their daily operations will not only boost innovation but also become magnets for top talent. The question organizations must ask themselves is clear: Do we embrace AI as an enabler, or do we risk falling behind?
As history has shown, technology is most transformative when it is available to all. AI should be no different. The organizations that will thrive in the coming decade will be those that balance responsible governance with widespread AI accessibility—empowering their people to innovate rather than restricting them with excessive controls. The question isn’t whether you’ll adopt AI, but whether you’ll do it in a way that creates competitive advantage or competitive disadvantage.
In my post “Four Categories of AI Solutions”, I categorized AI solutions by their level of innovation and complexity. Building on that framework, I’ve been thinking about how AI-assisted programming tools fit into this model—particularly the trade-off between speed and precision in software development.
Mapping Speed and Precision
The diagram below illustrates how tasks can be plotted along axes of speed and precision. As you move towards higher precision (e.g., creating backend services or system programming), speed naturally decreases, as does the immediate value AI tools provide. Conversely, low-precision tasks—like generating boilerplate code for frontend applications—enable high speed and provide quick wins.
Dave Farley in a recent video seems to align with this observation. The speakers noted that AI tools excel at accelerating well-defined and repetitive tasks, like building a simple mobile app or prototyping a frontend interface. These tasks fall into Category 1 of my model: low complexity, high-speed solutions.
However, the further you move into Category 3+4—solutions requiring precision and contextual understanding—the less impactful these tools become. For instance, when my team uses GitHub Copilot for backend development, only about 20% of its suggested code is accepted. The rest lacks the precision or nuanced understanding needed for high-stakes backend systems.
The Speed-Precision Trade-Off
The interview also highlighted a critical concern: AI’s emphasis on generating code quickly can erode the incremental approach central to traditional programming. In precision-driven tasks, small, deliberate steps are essential to ensure reliability and minimize risk. By generating large amounts of code at once, AI tools risk losing this careful craftsmanship.
Yet this trade-off isn’t a flaw—it’s a characteristic of how these tools are designed. AI’s value lies in accelerating the routine and freeing up developers to focus on higher-order problems. For precision tasks, AI becomes an assistant rather than a solution, helping analyze systems, identify bugs, or suggest improvements.
The Four Categories Revisited
This balancing act between speed and precision ties directly into the “Four Categories of AI Solutions”:
Category 1: High-speed, low-precision tasks like prototyping and boilerplate generation. AI tools thrive here.
Category 2: Moderately complex applications, where AI can augment human effort but requires careful validation.
Category 3: High-precision, low-speed systems programming or backend development. AI contributes less here, serving more as an analysis tool.
Category 4: Novel, cutting-edge AI applications requiring custom-built solutions.
As we develop software with AI, understanding where these tools provide the most value—and where their limitations begin—is critical. For now, AI tools may help us write code faster, but when it comes to precision, the human touch remains irreplaceable.
In Software Engineering in Growth Products at Carlsberg, our journey towards modern infrastructure management began with a familiar challenge: as the number of development teams grew, the traditional approach of manually provisioning and managing infrastructure became a significant bottleneck. The DevOps team, tasked with building and maintaining infrastructure for multiple development teams, found themselves overwhelmed by the increasing demand for infrastructure resources.
Each new project required careful setup of networking, permissions, and cloud resources, all of which had to be manually configured by a small DevOps team. As development velocity increased and more teams came onboard, this model proved unsustainable. New projects faced delays waiting for infrastructure provisioning, while the DevOps team struggled to keep pace with mounting requests.
Reimagining Infrastructure Creation
The solution emerged when the DevOps team envisioned a different approach: what if developers could create their own infrastructure while adhering to organizational standards? The challenge was to enable self-service infrastructure without requiring developers to understand the complexities of building secure, scalable, and compliant cloud resources.
This vision led to the creation of Gaia, a platform that automates infrastructure creation while maintaining strict security and compliance standards. Built by the DevOps team, Gaia represents a fundamental shift in how infrastructure is provisioned and managed at Carlsberg.
The Platform Engineering Approach
Infrastructure as Code Evolution
Gaia elevates infrastructure creation beyond basic scripting by providing a comprehensive platform engineering solution. The platform utilizes Terraform for infrastructure provisioning but abstracts its complexity through a higher-level interface. This approach allows developers to focus on their applications while ensuring infrastructure deployments follow organizational best practices.
Standardized Module Library
The platform provides an extensive library of pre-built, production-ready modules covering the complete spectrum of AWS infrastructure components:
Compute Services: EC2, ECS, EKS, Lambda
Data Stores: Aurora, RDS, DynamoDB, DocumentDB, Redis, Elasticsearch
Networking: VPC, Load Balancers, API Gateway, Route53
Security: IAM, ACM, Secrets Manager
Messaging: SQS, Kafka
Monitoring: CloudWatch, Managed Grafana
Each module encapsulates best practices, security controls, and compliance requirements, ensuring consistent infrastructure deployment across the organization.
Developer Experience
Simplified Workflow
Gaia integrates seamlessly with existing development workflows through GitHub. Developers request infrastructure by:
Creating a configuration file with simple key-value pairs
Submitting a pull request
Awaiting automated validation and deployment
Example configuration for a serverless function with a storage layer and an API Gateway:
The API Gateway configuration for the API is very simple:
Once the developer is ready to create the infrastructure a Pull Request is created and a “code owner” (in this case a Platform Engineer Team Member) approves the request and the infrastructure is deployed automatically.
Automated Compliance
The platform automatically enforces organizational standards and security policies. Developers don’t need to worry about:
Network configuration
Security group settings
Access control policies
Compliance requirements
All these aspects are handled automatically by Gaia’s pre-configured modules.
Technical Architecture
Terragrunt Integration
Gaia leverages Terragrunt as a wrapper around Terraform to provide enhanced functionality:
Automatic variable injection based on environment context
Template-based module generation
Configuration reuse across environments
Simplified state management
Monitoring and Observability
The platform includes native integration with monitoring tools:
Automated Datadog dashboard creation
Standardized monitoring configurations
Built-in health checks and alerts
Custom metric collection
Organizational Impact
DevOps Transformation
Reduced manual infrastructure work by approximately 80%
Shifted focus from repetitive tasks to platform improvements
Enabled scaling of development operations without proportional increase in DevOps resources
While currently focused on AWS, Gaia is being extended to support Azure. This expansion presents unique challenges due to fundamental differences in how cloud platforms implement similar services. The team is working to maintain the same simple developer experience while adapting to Azure’s distinct architecture.
Platform Evolution
Planned enhancements include:
Enhanced monitoring capabilities
Expanded multi-cloud support
Deeper integration with development tools
Advanced automation features
Conclusion
Gaia represents a successful transformation from traditional DevOps to platform engineering. By providing developers with self-service infrastructure capabilities while maintaining security and compliance, the platform has eliminated a major organizational bottleneck. The success of this approach demonstrates how well-designed abstractions and automation can make infrastructure management accessible to development teams while maintaining enterprise-grade standards.
The platform has fundamentally transformed how Carlsberg manages cloud infrastructure. As cloud infrastructure continues to evolve, Gaia’s modular architecture and focus on developer experience position it well for future adaptations and enhancements. The platform serves as a testament to how modern platform engineering can effectively bridge the gap between development velocity and operational excellence.
Imagine a highway at 100% capacity. Traffic doesn’t just slow down—it stops completely. A single broken-down car causes massive ripple effects because there’s no buffer space to absorb the variation. This isn’t just an analogy; it’s mathematics. And the same principle explains why running teams at full capacity mathematically guarantees the death of innovation.
The Queue Theory Reality
In 1961, mathematician J.F.C. Kingman proved something remarkable: as utilization approaches 100%, delays grow exponentially. This finding, known as Kingman’s Formula, demonstrates that systems operating at full capacity don’t just slow down linearly—they break down dramatically. Hopp and Spearman’s seminal work “Factory Physics” (2000) further established that optimal system performance occurs at around 80% utilization, giving rise to the “80% Rule” in operations management.
This isn’t opinion or management theory—it’s mathematics. When utilization exceeds 80-85%, systems experience:
Exponentially increasing delays
Inability to handle normal variation
Cascading disruptions from small problems
Deteriorating performance across all metrics
The Human System Connection
Just as a machine’s productivity is limited by its operational capacity, humans too are constrained by cognitive load. People and teams are systems too. When cognitive load research pioneers Sweller and Chandler demonstrated how mental capacity follows similar patterns, they revealed something crucial: minds at 100% capacity lose the ability to process new information effectively. Just as a fully utilized highway can’t absorb a single additional car, a fully utilized mind can’t absorb new ideas or opportunities.
The implications are profound: innovation requires spare capacity. This isn’t about working less—it’s about maintaining the mental and temporal space required for creative thinking and problem-solving. Studies of innovation consistently show that breakthrough ideas emerge when people have the bandwidth to:
Notice unexpected patterns
Explore new connections
Experiment with different approaches
Learn from failures
The Three Horizons Impact
McKinsey’s Three Horizons Framework provides a useful lens for understanding innovation timeframes:
Horizon 1: Improving current business
Horizon 2: Extending into new areas
Horizon 3: Creating transformative opportunities
Here’s where queue theory delivers its killing blow to innovation: At 100% utilization, everything becomes Horizon 1 by mathematical necessity. When a system (human or organizational) operates at full capacity, it can only handle what’s already in the queue. New opportunities, no matter how promising, must wait. Over time, Horizons 2 and 3 don’t just suffer—they become mathematically impossible.
To keep Horizons 2 and 3 viable, companies need to intentionally limit Horizon 1 resource utilization and leave room for creative and exploratory projects.
The Innovation Impossibility
Queue theory proves that running at 100% utilization:
Makes delays inevitable
Eliminates flexibility
Prevents absorption of variation
Blocks capacity for new initiatives
Therefore, organizations face a mathematical certainty: maintain 100% utilization or maintain innovation capability. You cannot have both. This isn’t a management choice or cultural issue—it’s as fundamental as gravity.
The solution isn’t working less—it’s working smarter. Just as highways need buffer capacity to function effectively, organizations need spare capacity to innovate. The 80% rule isn’t about reduced output; it’s about maintaining the space required for sustainable performance and growth.
The choice is clear: accept the mathematical reality that innovation requires spare capacity, or continue pushing for 100% utilization while wondering why transformative innovation never seems to happen.
References:
Kingman, J.F.C. (1961). “The Single Server Queue in Heavy Traffic”
DevOps promised to bridge the gap between development and operations, aiming to deliver infrastructure faster and more efficiently. However, in many organizations, the reality often fell short of this ideal. DevOps frequently became a practice where operations teams learned to script infrastructure without fully embracing key software engineering principles. It became more about scripting than true engineering.
The Need for a Higher Abstraction
As infrastructure needs grew more complex, it became clear that traditional DevOps approaches were not scaling effectively. Tools like Terraform, while powerful, often proved to be terse and not particularly developer-friendly. They got the job done, but they weren’t providing the streamlined experience that developers needed. A new approach was necessary – one that would raise the level of abstraction and make infrastructure more accessible.
The Golden Path as a Product
Enter the concept of the “golden path” – a set of pre-built, standardized infrastructure solutions that developers can easily use and customize. This approach treats infrastructure as a product, designed with the end-user – the developer – in mind.
The golden path isn’t just a set of scripts or configurations; it’s a carefully crafted product that encapsulates best practices, security considerations, and organizational policies. It automates infrastructure creation while maintaining alignment with company standards, allowing developers to provision cloud resources without needing to worry about governance, security, or configuration inconsistencies.
Raising the Abstraction Level
To understand the significance of this shift, consider this analogy: Terraform, while powerful, is often like the assembly language of infrastructure. Platform engineering, and the golden path approach, is about raising that abstraction, creating reusable and maintainable infrastructure solutions that developers can work with seamlessly.
Just as high-level programming languages made software development more accessible and efficient compared to assembly language, the golden path aims to do the same for infrastructure management. By creating higher-level abstractions, we’re making infrastructure more understandable, manageable, and aligned with modern software development practices.
The Role of Full-Stack Platform Engineers
This new approach requires a new kind of professional: the full-stack platform engineer. These engineers think like developers while solving infrastructure challenges. They build scalable, reliable, and developer-friendly infrastructure that empowers teams.
Full-stack platform engineers focus on creating robust, scalable infrastructure solutions that directly support business needs, rather than getting bogged down in low-level configuration details. They apply the same rigor expected in software development to infrastructure design, treating infrastructure truly as code.
Enhancing Developer Experience and Security
The golden path approach significantly enhances the developer experience. By integrating infrastructure provisioning directly into familiar development workflows (like those in GitHub), it allows developers to request and manage infrastructure as part of their normal process, without delays or context switching.
This approach also allows for the seamless integration of security practices. By baking security considerations into the golden path from the start, organizations can shift security left in the development process, addressing vulnerabilities at their source without compromising developer productivity.
A New Era of Infrastructure Management
The rise of full-stack platform engineering and the golden path approach represents a significant evolution in how we think about and manage infrastructure. It’s not just DevOps 2.0; it’s a fundamental shift in mindset that treats infrastructure as a product designed for developer success.
By raising the abstraction level, applying software engineering principles to infrastructure, and focusing on creating reusable, maintainable solutions, this approach promises to make infrastructure more accessible, secure, and aligned with modern development practices. As organizations continue to grapple with increasing complexity, the golden path offers a way forward – empowering developers, enhancing security, and ultimately accelerating innovation.
At Carlsberg, this approach has been embodied in Gaia, our golden path platform built by full-stack platform engineers. Gaia exemplifies how treating infrastructure as a product can transform development processes, making them more efficient and developer-friendly. It stands as a testament to the power of full-stack platform engineering in creating solutions that truly serve the needs of modern development teams.
As more organizations embrace this shift, we can expect to see a new landscape of infrastructure management emerge – one where the golden path, crafted by skilled full-stack platform engineers, leads the way to more innovative, secure, and efficient software development practices.
Artificial intelligence (AI) technologies have caused a dramatic change in software engineering. At the forefront of this revolution are AI-Engineers – the professionals who implement solutions within the ‘Builders’ category of AI adoption, as I outlined in my previous post on Four Categories of AI Solutions. These engineers not only harness the power of AI but also redefine the landscapes of industries.
As I recently discussed in “AI-Engineers: Why People Skills Are Central to AI Success” organizations face a critical talent shortage in AI implementation. McKinsey’s research shows that 60% of companies cite talent shortages as a key risk in their AI adoption plans. This shortage makes understanding the AI Engineer role and its distinct skillset more crucial than ever.
But what is an AI-Engineer?
Core Skills of an AI Engineer
AI-Engineers are skilled software developers who can code in modern languages. They create the frameworks and software solutions that enable AI functionalities and make them work well with existing enterprise applications. While they need basic knowledge of machine learning and AI concepts, their primary focus differs from data engineers. Where data engineers mainly focus on writing and managing data models, AI-Engineers concentrate on building reliable, efficient, and scalable software solutions that integrate AI.
Strategic Business Outcomes
The role of AI-Engineers is crucial in translating technological advancements into strategic advantages. Their ability to navigate the complex landscape of AI tools and tailor solutions to specific business challenges underlines their unique role within the enterprise and software engineering specifically. By embedding AI into core processes, they help streamline operations and foster innovative product development.
Continuous Learning and Adaptability
As I described in “Keeping Up with GenAI: A Full-Time Job?” the AI landscape shifts at a dizzying pace. Just like Loki’s time-slipping adventures, AI-Engineers find themselves constantly jumping between new releases, frameworks, and capabilities – each innovation demanding immediate attention and evaluation.
For AI-Engineers, this isn’t just about staying informed – it’s about rapidly evaluating which technologies can deliver real value. The platforms and communities that facilitate this learning, such as Hugging Face, become essential resources. However, merely keeping up isn’t enough. AI-Engineers must develop a strategic approach to:
Evaluate new technologies against existing solutions
Assess potential business impact before investing time in adoption
Balance innovation with practical implementation
Maintain stable systems while incorporating new capabilities
Real-World Impact
The real value of AI-Engineers becomes clear when we look at concrete implementation data. In my recent analysis of GitHub Copilot usage at Carlsberg (“GitHub Copilot Probably Saves 50% of Time for Developers“), we found fascinating patterns in AI tool adoption. While developers and GitHub claim the tool saves 50% of development time, the actual metrics tell a more nuanced story:
Copilot’s acceptance rate hovers around 20%, meaning developers typically use one-fifth of the suggested code
Even with this selective usage, developers report significant time savings because reviewing and modifying AI suggestions is faster than writing code from scratch
The tool generates substantial code volume, but AI-Engineers must carefully evaluate and adapt these suggestions
This real-world example highlights several key aspects of the AI-Engineer role:
Tool Evaluation: AI-Engineers must look beyond marketing claims to understand actual implementation impact
Integration Strategy: Success requires thoughtful integration of AI tools into existing development workflows
Metric Definition: AI-Engineers need to establish meaningful metrics for measuring AI tool effectiveness
Developer Experience: While pure efficiency gains may be hard to quantify, improvements in developer experience can be significant
These findings demonstrate why AI-Engineers need both technical expertise and practical judgment. They must balance the promise of AI automation with the reality of implementation, ensuring that AI tools enhance rather than complicate development processes.
Conclusion
AI Engineering is undeniably a distinct skill set, one that is becoming increasingly indispensable in AI transformation. As industries increasingly rely on AI to innovate and optimize, the demand for skilled AI Engineers who can both understand and shape this technology continues to grow. Their ability to navigate the rapid pace of change while delivering practical business value makes them essential to successful AI adoption. Most importantly, their role in critically evaluating and effectively implementing AI tools – as demonstrated by our Copilot metrics – shows why this specialized role is crucial for turning AI’s potential into real business value.
In my blog post “Four Categories of AI Solutions” (https://birkholm-buch.dk/2024/04/22/four-categories-of-ai-solutions), I outlined different approaches to building AI solutions, but it’s becoming increasingly clear that the decision on how to approach AI hinges on the talent and capabilities within the organization. As AI continues to evolve at lightning speed, companies everywhere are racing to adopt the latest innovations. Whether it’s generative AI, machine learning, or predictive analytics, organizations see AI as a strategic advantage. But as exciting as these technologies are, they come with a less glamorous reality—people skills are the make-or-break factor in achieving long-term AI success.
The Talent Crunch: A Major Barrier to AI Success
Reports from both McKinsey and Gartner consistently highlight a serious shortage of skilled AI talent. McKinsey’s latest research suggests that AI adoption has plateaued for many companies not due to a lack of use cases, but because they don’t have the talent required to execute their AI strategies effectively. 60% of companies cite talent shortages as a key risk in their AI adoption plans. (McKinsey State of AI 2023: https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai-in-2023-generative-ais-breakout-year).
Given the rapid pace of change in AI tools and techniques, developing an internal team of AI Engineers is one of the most sustainable strategies for companies looking to stay competitive. AI Engineers are those with the expertise to design, build, and maintain custom AI solutions tailored to the specific needs of the organization.
The retention challenge in AI isn’t just about compensation—it’s about providing meaningful work, opportunities for continuous learning, and a sense of ownership over projects. Diverse AI teams are essential for preventing biases in models and creating more robust, well-rounded AI systems. Offering inclusive, supportive environments where AI engineers can grow professionally and personally is essential to keeping top talent engaged (McKinsey AI Tech Talent Survey: https://www.mckinsey.com/capabilities/quantumblack/our-insights/new-mckinsey-survey-reveals-the-ai-tech-talent-landscape).
Companies that prioritize skills development will have a competitive edge. AI is advancing so quickly that organizations can no longer rely solely on external vendors to provide off-the-shelf solutions. Building an internal team of AI Builders—engineers who are continually learning and improving their craft—is essential to staying ahead of the curve. Offering employees opportunities to reskill and upskill is no longer optional; it’s a necessity for retaining talent and remaining competitive in the AI-driven economy.
I believe the role of AI Engineers will continue to grow in importance and complexity. We might see new specializations emerge, such as AI ethics officers ensuring responsible AI use, or AI-human interaction designers creating seamless experiences.
In my view, the most valuable AI Engineers of the future could be those who can not only master the technology but also understand its broader implications for business and society. They might need to navigate complex ethical considerations, adapt to rapidly changing regulatory landscapes, and bridge the gap between technical capabilities and business needs.
Conclusion: Investing in People is Investing in AI Success
The success of any AI initiative rests on the quality and adaptability of the people behind it. For organizations aiming to lead in the AI space, the focus should be on creating a workforce of AI Engineers—skilled professionals who can navigate the ever-changing landscape of AI technologies.
The lesson is clear: to succeed with AI, invest in your people first. The future of AI is not just about algorithms and data—it’s about the humans who will shape and guide its development and application.
As a technologist, it feels like I’m constantly time slipping — like Loki in Season 2 of his show. Every time I’ve finally wrapped my head around one groundbreaking AI technology, another one comes crashing in, pulling me out of my flow. Just like Loki’s painful and disorienting jumps between timelines, I’m yanked from one new release or framework to the next, barely catching my breath before being dropped into the middle of another innovation.
In the last week alone, we’ve had a flood of announcements that make it impossible to stand still for even a second. Here’s just a glimpse:
OpenAI Swarm (October 16, 2024) OpenAI dropped “Swarm,” an open-source framework for managing multiple autonomous AI agents—a move that could redefine how we approach collaborative AI and automation. https://github.com/openai/swarm
WorldCoin Rebrands as World (October 18, 2024) WorldCoin’s new Orb is yet another reminder that biometric and blockchain technology continues to merge in unpredictable ways. With its iris-scanning Orb, it’s trying to push a global financial identity system—a concept that sparks as much excitement as concern, especially around data privacy. https://www.theverge.com/2024/10/18/24273691/world-orb-sam-altman-iris-scan-crypto-token
Anthropic’s New Models & ‘Computer Use’ Feature (October 22, 2024) Anthropic has introduced the latest Claude 3.5 models, including a new ‘computer use’ feature that allows AI to interact directly with applications. This marks a major shift toward AI being able to execute tasks like filling out forms and interacting with user interfaces, making it a significant leap in real-world functionality. https://www.anthropic.com/news/claude-3-5-sonnet
These developments are not isolated. The latest Stanford AI Index Report 2024 provides some staggering numbers that put this onslaught of innovation into perspective:
149 foundation models were released in 2023, more than double the number from 2022, and a whopping 65.7%were open-source. That’s an overwhelming volume of tools, each requiring careful consideration for their potential applications.
The number of AI-related publications has tripled since 2010, reaching over 240,000 by 2022. Staying on top of this research is an almost Sisyphean task, but these papers provide the groundwork for the rapid-fire advancements we’re seeing.
Generative AI investments exploded to $25.2 billion in 2023, nearly eight times the previous year. This boom in funding is driving the constant stream of new AI tools and capabilities, each promising to reshape the landscape.
AI was mentioned in 394 earnings calls across nearly 80% of Fortune 500 companies in 2023, an enormous jump from the 266 mentions in 2022. The sheer presence of AI in corporate strategy highlights how central this technology has become to every industry.
The Technologist’s Dilemma
The rapid pace of AI advancements presents an overwhelming challenge for technologists. Each new tool or framework isn’t just a minor update—it’s potentially transformative, requiring deep understanding and immediate adaptation. For those managing teams and implementing technological advancements, this fast-moving landscape demands constant learning and vigilance.
