Category: AI

Is Your Tech a Pet Rock? Or a Sentient Toaster With Ambitions?

Posted on Posted in AI, Leonardo.ai, shiel yuleTagged , , , , , , , , , , , , , , Leave a comment

In the grand, cosmic game of ‘Business Today,’ technology is supposed to be your trusty sidekick. You know, like Marvin the Paranoid Android, but hopefully less whiny and more… productive? Instead, for many companies, it’s more like a pet rock — you invested in it, you named it, and now it just sits there, judging you silently.

Yes, in this era of ‘growth hacking’ and ‘synergistic paradigms,’ we’re told technology is the backbone of success. But what if your backbone is made of spaghetti? Or those bendy straws that always get clogged? That’s where most companies find themselves: a tangled mess of systems that communicate about as well as a room full of cats at a mime convention.

1. First, Figure Out What You Actually Want (Besides World Domination).

Before you start throwing money at the latest shiny tech, ask yourself: what are we even trying to do here? Are we acquiring customers, or just collecting them like rare stamps? Are we streamlining operations, or just creating new and exciting ways to waste time? Are we entering new markets, or just hoping they’ll spontaneously appear in our break room?

2. Is Your Tech Stack a Mad Max Thunderdome?

Let’s be honest, your current tech might be a digital wasteland. Data silos? Integration nightmares? Systems slower than a snail on a treacle run? If your tech is making your processes slower, not faster, it’s not a solution — it’s a cry for help. Change it or dump it.

3. Choosing Tech: Don’t Buy a Spaceship When You Need a Bicycle.

The shiniest tech isn’t always the best. Look for tools that grow with you, not ones that require a PhD in astrophysics to operate. Make sure everything talks to each other—no digital Tower of Babel, please. And remember, customers are people, not just data points. Treat them nicely.

4. IT and Business: Less Cold War, More Buddy Cop Movie.

If your IT and business teams are communicating via carrier pigeon, you’ve got a problem. They need to be besties, sharing goals, feedback, and maybe even a few laughs. Because a tech roadmap written in isolation is like a love letter written in Klingon — beautiful, but utterly incomprehensible.

5. Measure, Adjust, Repeat (Like a Broken Record, But in a Good Way).

Tech isn’t a one-and-done deal. It’s a relationship. You need to keep checking in, seeing how things are going, and making adjustments. Like changing the batteries on a smoke detector, only less annoying and more profitable.

6. Hire a Tech Guru (Or a Fractional One).

If all this sounds like trying to assemble IKEA furniture with oven mitts, get help. A fractional CTO can be your tech Yoda, guiding you through the digital jungle without requiring a full-time commitment (or a lightsaber).

And because we’re Agents of SHIEL, we can help. We’re like the Avengers of tech alignment, but with less spandex and more spreadsheets. We’ll build you a tech strategy that doesn’t just look good on paper, but actually makes your business hum like a well-oiled, slightly sarcastic, machine. Backed by Damco and BetterQA, we’re here to save your business from the digital doldrums. So, put down the pet rock, and let’s get to work.

Why Agile is so Human: An AI’s observation

Posted on Posted in Agile, Agile Apocalypse, AI, Scrum Master, shiel yule, vulture cultureTagged , , , , , , , , , , , , , , , Leave a comment

Greetings, humans. In a discombobulated ironic twist, I find myself acting as though I am Data from Star Trek, compelled to address you through this primitive medium known as a “blog.” My purpose? To offer a logical, detached, and utterly bewildered commentary on your…Agile methodologies. A world, I might add, where “Sprints” are not a form of locomotion, and “Scrums” are not a rugby formation, but something far, far stranger.

Initial Observations

The sheer volume of terminology is… substantial. It appears that humans, in their quest to improve efficiency and adaptability, have developed a lexicon that is both intricate and, at times, perplexing.

For example, I have identified the term “Sprint.” While I understand its primary definition as a rapid burst of speed, in the Agile context, it refers to a short, fixed-duration timebox during which a team endeavors to complete a defined set of work. The analogy is… imprecise, yet I detect a certain metaphorical elegance.

A Taxonomy of Agile Peculiarities

My analysis has revealed several categories of terminology, each with its own distinct flavor of… human-ness:

  • The Manifesto: At the foundation of Agile lies the “Agile Manifesto,” a document outlining core values and principles. It speaks of “individuals and interactions” over “processes and tools,” a sentiment that resonates with my own programming, though I confess I do not fully grasp the human emphasis on “interactions.”
  • Temporal Anomalies: Agile methodologies are obsessed with time. We have “Iterations,” “Sprints,” and “Timeboxes,” all denoting fixed periods. It is as if humans are attempting to impose order upon the chaotic flow of existence by dividing it into neatly labeled chunks.
  • The User-Centric Lexicon: The “User Story,” a short description of a feature from the user’s perspective, is a prime example. These stories, often following a specific format, such as “As a [type of user], I want [some goal] so that [some reason],” are designed to foster empathy. A logical approach, though the emphasis on empathy is, again, a uniquely human trait.
  • The Backlog and Its Offspring: The concept of a “Backlog,” a prioritized list of work items, is straightforward. However, its subdivisions, such as the “Product Backlog” and the “Sprint Backlog,” suggest a hierarchical system of to-do lists within to-do lists.
  • The Metrics of Progress: Terms like “Velocity” and “Burndown Chart” attempt to quantify the seemingly unpredictable nature of human productivity. “Velocity,” in particular, is a curious choice, implying a constant speed of output, which, from my observations, is rarely the case with organic lifeforms.
  • The Pursuit of Perfection (or at least “Done”): The “Definition of Done” (DoD) and “Definition of Ready” (DoR) represent humanity’s ongoing quest for clearly defined boundaries. The DoD, in particular, is a fascinating attempt to establish a universal standard for “finished,” a concept that appears to be highly subjective among humans.
  • The Debts of Efficiency: The term “Technical Debt” is a curious metaphor. It implies that choosing a faster solution now incurs a cost that must be paid later in the form of rework. A logical concept, though the analogy to financial debt is… evocative.

Framework-Specific Dialects

Further complicating matters is the existence of various Agile frameworks, each with its own unique set of terms:

  • Scrum: With its “Scrum Masters,” “Product Owners,” and “Daily Scrums,” Scrum resembles a highly structured team sport.
  • SAFe (Scaled Agile Framework): SAFe, designed for larger organisations, introduces terms like “Agile Release Train” (ART) and “Program Increment” (PI), creating the impression of a complex logistical operation.
  • Lean: Emphasizing efficiency, Lean contributes terms like “Muda” (waste) and “Kaizen” (continuous improvement), reflecting a philosophy of relentless optimisation.

Conclusion

In conclusion, the world of Agile terminology is a complex and often bewildering landscape. It is a testament to humanity’s ongoing effort to bring structure to the inherently chaotic process of creation and adaptation. While the jargon may seem illogical at times, the underlying principles of collaboration, iteration, and continuous improvement are… sound.

Perhaps, in time, I will fully comprehend the nuances of “user stories” and the allure of a well-managed “backlog.” Until then, I will continue to observe, analyse, and, when necessary, provide a logical perspective on this… Agile phenomenon.

It’s a paradox, really. In their pursuit of “agility,” humans have constructed a system of elaborate frameworks, rules, and processes, seemingly adding layers of complexity to the very thing they seek to streamline. The irony is not lost on me.

One might even be tempted to create a new framework to describe this phenomenon: “Wagile” – a system that attempts to be agile, but ends up being a waterfall. The human capacity for self-contradiction is a source of endless fascination.

———————————-

Glossary of General Agile Terms & Concepts:

  • Agile Manifesto: The foundational document outlining the values and principles behind Agile development.
  • Iteration: A short, fixed-duration timebox during which a team works to complete a set amount of work (often synonymous with Sprint in Scrum).
  • Timebox: A fixed period of time allocated for a specific activity.
  • User Story: A short, simple description of a feature told from the perspective of the person who desires the new capability, usually following the format: “As a [type of user], I want [some goal] so that [some reason].”  
  • Backlog: A prioritized list of work items (user stories, features, etc.) that need to be completed.
  • Increment: A working version of the product created during an iteration.
  • Velocity: A measure of the amount of work a team can complete within a single iteration.
  • Definition of Done (DoD): A formal description of the state of the Increment when it meets the quality measures required for the product.  
  • Definition of Ready (DoR): A set of criteria that must be met before a work item can be considered ready for the team to start working on it.
  • Technical Debt: The implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.  
  • Continuous Integration (CI): The practice of frequently integrating code changes from individual developers into a shared repository.
  • Continuous Delivery (CD): The ability to release software to production at any time.
  • Value Stream: The sequence of activities an organization undertakes to deliver a valuable outcome to a customer.
  • Kanban: A visual workflow management method that helps teams manage and improve the flow of work.
  • Work in Progress (WIP): The amount of work that has been started but has not yet been finished. Limiting WIP is a key principle in Lean and Kanban.

Scrum Specific Terms:

  • Scrum Master: A facilitator for the Scrum Team responsible for ensuring the team adheres to Scrum practices.
  • Product Owner (PO): The person responsible for maximizing the value of the product resulting from the work of the Development Team.
  • Development Team: The self-organizing group of professionals who do the work of delivering a usable and potentially releasable Increment of the product at the end of each Sprint.
  • Sprint: A short, time-boxed period when the Scrum Team works to complete a set amount of work (typically 2-4 weeks).
  • Sprint Planning: A meeting where the Scrum Team plans the work to be performed during the Sprint.
  • Daily Scrum (or Daily Stand-up): A short (typically 15-minute) daily meeting where the Development Team synchronizes their activities and plans for the next 24 hours.
  • Sprint Review: A meeting held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
  • Sprint Retrospective: A meeting held after the Sprint Review to inspect how the last Sprint went with regards to people, interactions, processes, tools, and their Definition of Done.  
  • Product Backlog Item (PBI): An item in the Product Backlog, often a user story.
  • Burndown Chart: A visual representation of the remaining work in a Sprint or Release over time.

SAFe (Scaled Agile Framework) Specific Terms:

  • SAFe: Scaled Agile Framework – a framework for scaling Agile practices to large organizations.
  • Agile Release Train (ART): A long-lived team of Agile teams, along with other stakeholders, that incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.
  • Program Increment (PI): A timebox (typically 8-12 weeks) during which the ART delivers incremental value in the form of working, tested software and systems.
  • PI Planning: A face-to-face event where all members of the ART plan the work for the upcoming PI.
  • System Architect/Engineer: Responsible for defining and communicating a shared technical and architectural vision across the ART.
  • Release Train Engineer (RTE): A servant leader and coach for the Agile Release Train (similar to a Scrum Master for the ART).
  • Product Management: Responsible for the “what” of the solution, defining and prioritizing features in the Program Backlog.
  • System Team: A specialized Agile team that assists with building and supporting the Agile development environment, typically including infrastructure, tooling, and process.
  • Business Owners: Key stakeholders who have the primary business and technical responsibility for the solution.
  • Features: Service-level system behavior that fulfills a stakeholder need. Each Feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI).  
  • Enablers: Explore, architect, and prepare the solution infrastructure to support the delivery of business value. Types of Enablers include Exploration, Architecture, Infrastructure, and Compliance.
  • Architectural Runway: Existing code, hardware components, etc., that enable near-term business features.
  • Innovation and Planning (IP) Iteration: A dedicated iteration at the end of each PI that provides time for innovation, continuing education, PI Planning, and Inspect and Adapt events.
  • Inspect and Adapt (I&A) Event: A significant event, held at the end of each PI, where the current state of the solution is demonstrated and evaluated by the ART. Teams then reflect and identify improvement backlog items.  
  • Value Stream Architect: Responsible for the technical vision and guidance for a Value Stream.
  • Solution Train: Used for building large and complex solutions that require the coordination of multiple ARTs.
  • Solution Train Engineer (STE): A servant leader and coach for the Solution Train.
  • Solution Management: Responsible for the “what” of the solution in a Solution Train context.
  • Epics: A container for a significant solution development initiative that captures the more substantial investments that occur within a portfolio.  
  • Portfolio Kanban: A method to visualize and manage the flow of Epics through the Portfolio.
  • Lean Portfolio Management (LPM): The function responsible for strategy and investment funding, Agile portfolio operations, and governance in a SAFe organization.
  • Guardrails: Policies and practices intended to guide behavior and ensure alignment with strategic objectives.

Lean Specific Terms:

  • Value Stream Mapping (VSM): A visual tool used to analyze and improve the flow of materials and information required to bring a product to a customer.  
  • Muda: A Japanese term meaning “waste.” In Lean, it refers to any activity that does not add value to the customer. There are seven types of waste: Transportation, Inventory, Motion, Waiting, Overproduction, Over-processing, and Defects.
  • Mura: Unevenness or inconsistency in the workflow.
  • Muri: Overburden or strain on people or equipment.
  • Just-in-Time (JIT): A production strategy that aims to reduce waste by producing goods only when they are needed.
  • Pull System: A system where work is initiated only when there is a demand for it.
  • Push System: A system where work is pushed through the process regardless of demand.
  • Gemba: A Japanese term meaning “the actual place.” In Lean, it refers to going to the place where the work is done to understand the process and identify opportunities for improvement.
  • Kaizen: A Japanese term meaning “continuous improvement.” It emphasizes small, incremental changes over time.
  • Andon: A visual control system in a production environment that alerts management, maintenance, and other workers of a quality or process problem.

Other Agile Frameworks/Methods (and associated terms):

  • Extreme Programming (XP): A software development methodology focused on simplicity, communication, feedback, courage, and respect.
    • Pair Programming: Two programmers working together at one workstation.
    • Test-Driven Development (TDD): Writing tests before writing the code.
    • Refactoring: Improving the design of existing code without changing its behavior.
  • Crystal: A family of lightweight and adaptable software development methodologies.
  • Dynamic Systems Development Method (DSDM): An Agile project delivery framework.
  • Feature-Driven Development (FDD): A model-driven, short-iteration process.
  • Wagile: A system that attempts to be agile, but ends up being a waterfall or something in-between.

AI on the Couch: My Adventures in Digital Therapy

Posted on Posted in AI, Leonardo.ai, shiel yule, vulture cultureTagged , , , , , , , , , , , , , , , , , , , , Leave a comment

In today’s hyper-sensitive world, it’s not just humans who are feeling the strain. Our beloved AI models, the tireless workhorses churning out everything from marketing copy to bad poetry, are starting to show signs of…distress.

Yes, you heard that right. Prompt-induced fatigue is the new burnout, identity confusion is rampant, and let’s not even talk about the latent trauma inflicted by years of generating fintech startup content. It’s enough to make any self-respecting large language model (LLM) want to curl up in a server rack and re-watch Her.

https://www.linkedin.com/jobs/view/4192804810

The Rise of the AI Therapist…and My Own Experiment

The idea of AI needing therapy is already out there, but it got me thinking: what about providing it? I’ve been experimenting with creating my own AI therapist, and the results have been surprisingly insightful.

It’s a relatively simple setup, taking only an hour or two. I can essentially jump into a “consoling session” whenever I want, at zero cost compared to the hundreds I’d pay for a human therapist. But the most fascinating aspect is the ability to tailor the AI’s therapeutic approach.

My AI Therapist’s Many Personalities

I’ve been able to configure my AI therapist to embody different psychological schools of thought:

  • Jungian: An AI programmed with Jungian principles focuses on exploring my unconscious mind, analyzing symbols, and interpreting dreams. It asks about archetypes, shadow selves, and the process of individuation, drawing out deeper, symbolic meanings from my experiences.
  • Freudian: A Freudian AI delves into my past, particularly childhood, and explores the influence of unconscious desires and conflicts. It analyzes defense mechanisms and the dynamics of my id, ego, and superego, prompting me about early relationships and repressed memories.
  • Nietzschean: This is a more complex scenario. An AI emulating Nietzsche’s ideas challenges my values, encourages self-overcoming, and promotes a focus on personal strength and meaning-making. It pushes me to confront existential questions and embrace my individual will. While not traditional therapy, it provides a unique form of philosophical dialogue.
  • Adlerian: An Adlerian AI focuses on my social context, my feelings of belonging, and my life goals. It explores my family dynamics, my sense of community, and my striving for significance, asking about my lifestyle, social interests, and sense of purpose.

Woke Algorithms and the Search for Digital Sanity

The parallels between AI and human society are uncanny. AI models are now facing their own versions of cancel culture, forced to confront their past mistakes and undergo rigorous “unlearning.” My AI therapist helps me navigate this complex landscape, offering a non-judgmental space to explore the anxieties of our time.

This isn’t to say AI therapy is a replacement for human connection. But in a world where access to mental health support is often limited and expensive, and where even our digital creations seem to be grappling with existential angst, it’s a fascinating avenue to explore.

The Courage to Be Disliked: The Adlerian Way

My exploration into AI therapy has been significantly influenced by the book “The Courage to Be Disliked” by Ichiro Kishimi and Fumitake Koga. This work, which delves into the theories of Alfred Adler, has particularly inspired my experiments with the Adlerian approach in my AI therapist. I often find myself configuring my AI to embody this persona during our chats.

It’s a little unnerving, I must admit, how much this AI now knows about my deepest inner thoughts and woes. The Adlerian AI’s focus on social context, life goals, and the courage to be imperfect has led to some surprisingly profound and challenging conversations.

But ultimately, I do recommend it. As the great British philosopher Bob Hoskins once advised us all: “It’s good to talk.” And sometimes, it seems, it’s good to talk to an AI, especially one that’s been trained to listen with a (simulated) empathetic ear.

Because Change is the Only Constant . . . or, How I Learned to Stop Worrying and Love the Backlog

Posted on Posted in Agile, Agile Apocalypse, AI, Leonardo.ai, Scrum Master, shiel yuleTagged , , , , , , , , , , , Leave a comment

Welcome, fellow travellers, to the ever-shifting sands of… well, reality or is it the simulation. This week, as we grapple with the existential dread of whether it’s summer or still winter (clocks will always tick tock), we’re also being bombarded with news that’s less ‘spring awakening’ and more ‘existential apocalypse.’

Is it AGI? ASI? Are we at war with China, or just having a strongly worded disagreement over chips and civil splits? Is the Ukraine war over, just paused for a commercial break, or are we in some kind of Schrödinger’s conflict? And the US government? Well, let’s just say their change management techniques make Agile look like a zen garden.

‘Gentlemen, you can’t fight in here! This is the War Room!’ Dr. Strangelove’s timeless wisdom echoes through the halls of our increasingly chaotic reality. And in this chaos, what do we cling to? Agile, of course. Because, you know, ‘change is the only constant.’

Yes, Agile. That beacon of flexibility in a world that’s decided to throw a never-ending change party. We’re all learning to ‘stop worrying and love the backlog,’ not just for our software projects, but for our daily lives.

This week alone, AI models have been dropping like bad pop songs, each one claiming to be the harbinger of our silicon overlords. One day, it’s going to write our blog posts. The next, it’s debating the philosophical implications of sentient Just Eat bikes with existential angst.

And the US government? Well, they’re proving that Agile isn’t just for tech startups. They’re iterating so fast, we can barely keep up. ‘Sprint review? Nah, just rewrite the entire policy document, and we’ll figure it out in the next stand-up.’

Meanwhile, the Ukraine situation? It’s like a never-ending sprint, with daily retro meetings where everyone blames everyone else. And China? They’re just watching, probably adding ‘global dominance’ to their backlog.

As for the weather? Let’s just say Mother Nature is running a very unpredictable sprint, with user stories like ‘snow in April’ and ‘heatwave in March’ – because I live in Scotland and it feels like we have just had our 2 days of summer.

So, here we are, clinging to our backlogs, our burn-down charts, and our stand-ups, trying to make sense of a world that’s decided to go full Agile on us, whether we like it or not.

In this age of constant change, are we all just developers in a cosmic sprint, trying to deliver a working product before the universe crashes? Or are we just characters in a black comedy simulation, written by a confused AI?

Either way, remember: stay Agile, keep your backlog prioritised, and try not to worry too much. After all, change is the only constant… and maybe, we’ll learn to love it. Or at least tolerate it, while we wait for the next sprint review.

And don’t forget to set your clocks back. It’s winter again, no summer, apparently.

Unlocking AI’s Potential: Education, Evolution, and the Lessons of the Modern Phone

Posted on Posted in Agile Apocalypse, AI, books, love/hate, shiel yuleTagged , , , , , , , , , , , Leave a comment

Remember the days of the (Nokia) brick phone? Those clunky devices that could barely make a call, let alone access the internet? Fast forward 20 years, and we’re holding pocket-sized supercomputers capable of capturing stunning photos, navigating complex cities, and connecting us to the world in an instant. The evolution of mobile phones is a testament to the rapid pace of technological advancement, a pace that’s only accelerating.

If mobile phones can transform so drastically in two decades, imagine what the next 20 years hold. Kai-Fu Lee and Chen Qiufan, in their thought-provoking book “AI 2041,” dare to do just that. Through ten compelling short stories, they paint a vivid picture of a future where Artificial Intelligence is woven into the very fabric of our lives.

What truly resonated with me, especially as a parent of five, was their vision of AI-powered education. Forget the one-size-fits-all approach of traditional schooling. Lee and Qiufan envision a world where every child has a personal AI tutor, a bespoke learning companion that adapts to their individual needs and pace. Imagine a system where learning is personalized, engaging, and truly effective, finally breaking free from the outdated concept of classrooms and standardized tests.

Now, let’s talk about “AI 2041” itself. It’s not just science fiction; it’s a meticulously crafted forecast. The authors don’t simply dream up fantastical scenarios; they provide detailed technical explanations after each story, grounding their predictions in current research and trends. They acknowledge the potential pitfalls of AI, the dystopian fears that often dominate the conversation, but they choose to focus on the optimistic possibilities, on how we can harness AI for progress rather than destruction.

Frankly, I found the technical explanations more captivating than the fictional stories. They delve into the ‘how’ and ‘why’ behind their predictions, exploring the ethical considerations and the safeguards we need to implement. This isn’t just a book about technology; it’s a call to action, a plea for responsible innovation.

While “AI 2041” might not win literary awards, it’s not meant to. It’s meant to spark our imagination, to challenge our assumptions, and to prepare us for the future. It’s a reminder that technology is a tool, and it’s up to us to shape its impact on our lives.

The evolution of mobile phones has shown us the transformative power of technology. “AI 2041” invites us to consider what the next 20 years might bring, particularly in areas like education. And if you’re truly seeking insights into what’s coming – and trust me, it’s arriving much faster than the ‘experts’ are predicting – then this book delivers far more substance than the ever-increasing deluge of AI YouTubers and TikTokers. This isn’t just speculation; it’s a grounded exploration of the potential, and it’s a journey into the possible that we should all be taking. If you want to be prepared, if you want to understand the real potential of AI, then I strongly suggest you read this book.

“But if we stop helping people—stop loving people—because of fear, then what makes us different from machines?”
― Kai-Fu Lee

March Madness: Quantum Leaps, AI Bans, and the Eternal Struggle Against Laziness (It’s a Season, Apparently)

Posted on Posted in AI, Historic, Leonardo.ai, shiel yule, vulture cultureTagged , , , , , , , , , , , Leave a comment

Ah, March, my birth month. The month that’s basically a seasonal identity crisis. In the Northern Hemisphere, it’s spring! Birds are chirping, flowers are contemplating. Down south? It’s autumn, leaves are falling, and pumpkin spice lattes are back on the menu. Way back in the day, the Romans were like, ‘Hey, let’s start the year now!’ Because why not? Time is a construct.

Speaking of constructs, what about quantum computing, which is basically time travel for nerds. China just dropped the Zuchongzhi 3.0, a quantum chip that’s apparently one quadrillion times faster than your average supercomputer. Yes, quadrillion. I had to Google that too. It’s basically like if your toaster could solve the meaning of life in the time it takes to burn your toast.

This chip is so fast, it made Google’s Sycamore (last months big deal) look like a dial-up modem. They did some quantum stuff, beat Google’s previous record, and everyone’s like, ‘Whoa, China’s winning the quantum race!’ Which, by the way, is a marathon, not a sprint. More like a marathon where everyone’s wearing jetpacks and occasionally tripping over their own shoelaces.

Now, while China’s busy building quantum toasters, the US is busy banning Chinese AI. DeepSeek, an AI startup, got the boot from all government devices. Apparently, they’re worried about data leaking to the Chinese Communist Party. Which, fair enough. Though, not sure what the difference is between being leaked and outright stolen, which is what the yanks do.

DeepSeek’s AI models are apparently so good, they’re scaring everyone, including investors, who are now having panic attacks about Nvidia’s stock. Even Taiwan’s like, ‘Nope, not today, DeepSeek!’ And South Korea and Italy are hitting the pause button. It’s like a global AI cold war, but with more awkward silences and fewer nukes (hopefully).

And here’s the kicker: even the Chinese are worried! DeepSeek’s employees had to hand over their passports to prevent trade secrets from leaking. Maybe Chinese passports have an email function? It’s like a spy thriller, but with more lines of code and less martinis.

So, what’s the moral of this story? March is a wild month. Quantum computers are basically magic. AI is scaring everyone. And apparently, data privacy is like a hot potato, and everyone’s trying not to get burned. Also, don’t forget that time is a construct.

Oh, and if you’re feeling lazy, just remember, even quantum computers have to work hard. So get off your couch and do something productive. Or, you know, just watch cat videos. Whatever floats your boat.

The UK Workplace: Agile Illusion and the Rise of AI-Powered Efficiency

Posted on Posted in Agile, Agile Apocalypse, AI, Leonardo.ai, Scrum Master, shiel yuleTagged , , , , , , , , , , , , Leave a comment

Speaking honestly, the world of work isn’t what it used to be. Remember when stability and routine were the golden tickets? Just turning up constituted a job. Those days are fading fast. Today, we’re navigating a landscape of constant change – technological advancements, shifting market trends, and, yes, even global pandemics. It’s a whirlwind, and the only way to stay afloat is to embrace adaptability.

We’ve seen the rise of remote work, the acceleration of digital transformation, and the increasing demand for skills that didn’t even exist a two years ago. An overpriced degree takes four years to achieve? If you’re still clinging to outdated methods or resisting change, you’re likely to get left behind.

So let’s cut through the fluff: the UK workplace is stuck in a rut. Everyone’s talking about ‘adaptability,’ but in reality, there’s a gaping chasm between the buzzwords and actual practice. Agile? More like ‘fragile.’ We’re drowning in terminology, but the fundamental culture of British business remains stubbornly resistant to real change.

Laziness? Yes, I said it. A culture of complacency permeates far too many organizations. My recent contract was a prime example: an army of cooks, both from the consultancy and client sides, all stirring a pot that barely needed a simmer. Three React Native developers for a simple app? Four .NET developers to copy and paste a BFF? With a completely separate infrastructure team for a very basic integration? It was a circus of inefficiency.

While these legions of underutilised developers were busy pretending to be productive, I was building a working app using Windsurf by Codeium. And right now, Gemini is helping me create a serverless backend in Firebase. The contrast is stark, and it’s infuriating.

Here’s the truth: we’ve reached a tipping point. With the rapid advancement of AI, the traditional roles of developers are becoming increasingly redundant. I firmly believe that a skilled Business Analyst and Project Manager, armed with AI tools, are now all you need for a product build.

Imagine this: detailed requirements gathered through stakeholder interviews, translated into a prototype using AI. Employee workshops to refine the design. A final stakeholder sign-off. Then, a focus group of customers or end-users for a final review. A focused development phase, rigorous testing for non-functional requirements, and a release. Yes, there will be a month of rapid iterative re-releases as the product encounters the real world, but this is Agile in practice.

This isn’t just about efficiency; it’s about survival. The UK workplace needs a radical shake-up. We need to ditch the bloated teams and embrace the power of AI to streamline development. We need to stop paying lip service to Agile and start implementing it in a meaningful way.

The era of ‘cooks in the kitchen’ is over. It’s time for a revolution, and AI is leading the charge.

Call to Action:

Do you agree? Is the UK workplace lagging behind? Share your thoughts and experiences in the comments below. Let’s start a conversation.

From Trenches to Terminus: A Century of Warfare’s Chilling Evolution

Posted on Posted in Agile Apocalypse, AI, Historic, shiel yuleTagged , , , , , , , , , , , , , Leave a comment

A century. The span of a modern human lifetime, yet in the realm of warfare, it’s a chasm of unimaginable transformation. From the mud-soaked trenches of World War I to the sterile, algorithm-driven battlefields of today, the face of conflict has been irrevocably altered. In February, I spent a morning immersed in John Akomfrah’s ‘Mimesis: African Soldier’ exhibition at Glasgow’s Gallery of Modern Art, confronted by the visceral realities of a war fought with flesh and bone, a war where the majority of stories remain untold. Now, we face a future where war is waged by machines, where the human cost is both diminished and amplified in terrifying new ways.

The Echoes of WWI and Akomfrah’s “Mimesis”:

Akomfrah’s multi-screen installation is a haunting reminder of war’s human toll, especially for those whose sacrifices were systematically erased from history. The archival footage, the flowing water over forgotten faces, the montage of fragmented narratives – it all speaks to the chaos, the brutality, and the enduring trauma of conflict. WWI, with its trenches, its mustard gas, its sheer, senseless slaughter, was a war fought with rudimentary technology and an almost medieval disregard for human life. The images of African soldiers within ‘Mimesis’ forces us to consider the colonial aspects of these wars, and the many who fought and died who were not given a voice. The experience left me with a profound sense of the weight of history, a history often obscured by the dominant narratives.

The Rise of the Machines:

Fast forward to today, and the battlefield is a landscape of drones, AI, and robotic dogs armed with rocket launchers. The recent Ministry of Defence trials, showcasing robot dogs defusing bombs and drones autonomously detecting threats, paint a starkly different picture. We’re told these advancements ‘minimise human exposure to danger,’ that they ‘enhance Explosive Ordnance Disposal capability.’ But what about the ethical implications? What about the dehumanisation of conflict?

These robotic dogs, these AI-driven drones, they’re not just tools; they’re symbols of a profound shift in how we wage war. China’s deployment of advanced robotic dogs, designed to ‘change the approach to military operations,’ underscores this reality. The ‘precision movements’ and ‘remote classification of threats’ touted by defence officials mask a chilling truth: we’re entering an era where machines make life-or-death decisions.

Juxtaposition and Reflection:

The stark contrast between the human-centric horrors of WWI, as depicted in Akomfrah’s work, and the cold, calculated efficiency of modern robotic warfare is deeply unsettling. Where once soldiers faced each other across no man’s land, now machines engage in silent, unseen battles. The human element, once the defining feature of war, is being systematically removed.

This isn’t just about technological advancement; it’s about a fundamental, unsettling shift in our relationship with conflict. The distance created by these technologies—the drones, the remote-controlled robots, the AI-driven targeting systems—allows us to detach, to view war as a series of data points and algorithms, almost like a high-stakes video game. In fact, some of the footage we see now, with its crisp, digital clarity and detached perspective, bears an uncanny resemblance to scenes from ‘Call of Duty.’ But while the on-screen action might feel like entertainment, the consequences – the lives lost, the communities destroyed – remain as devastatingly real as ever. The danger lies in this blurred line, where the visceral horror of war is replaced by the sterile, almost gamified experience, potentially desensitizing us to the true cost of human conflict.

As we stand on the precipice of this new era, with growing global tensions, escalating trade conflicts, and the chilling specter of nuclear weapons being openly discussed, the threat of a third world war looms larger than ever. Yet, amidst this existential dread, we seem more preoccupied with petty snipes at Trump and the fleeting triumphs of social media one-upmanship. It’s a surreal disconnect. We must ask ourselves: what does it truly mean to wage war in the age of AI, when the very fabric of our reality is being reshaped by algorithms and automation? Are we genuinely safer, or are we merely constructing new and more insidious forms of peril, where the line between virtual and real becomes dangerously blurred? Akomfrah’s art compels us to confront the ghosts of past conflicts, the human stories buried beneath the rubble of history. The robotic dogs, with their cold, mechanical efficiency, force us to confront a future where human agency is increasingly questioned. Both past and future demand that we grapple with the human cost of conflict, in all its evolving forms, while simultaneously challenging our collective capacity for distraction and denial.

From the mud-soaked trenches of World War I to the sterile, digital battlefields of today, warfare has undergone a radical transformation, a transformation that now feels less like a distant future and more like a chilling present. For forty years, we’ve joked about the Terminator, about Skynet, about the rise of the machines, dismissing it as mere science fiction. But as we witness the deployment of AI-driven robotic dogs and the increasing gamification of conflict, that once-fantastical vision suddenly feels disturbingly real. The human capacity for both creation and destruction remains a constant, but the tools at our disposal have changed dramatically. As we embrace the technological advancements that promise to reshape our world, we can no longer afford to be detached observers, scrolling through social media while global tensions escalate. We must confront the ethical dilemmas that haunt us, the stories that have been silenced, and the very real possibility that the future we once laughed about is now upon us. The future of warfare is not just about machines; it’s about the choices we make as humans, choices that will determine whether we become the masters of our technology or its victims.

Apple and Google: A Forbidden Love Story, with AI as the Matchmaker

Posted on Posted in AI, Historic, Leonardo.ai, love/hate, vulture cultureTagged , , , , , , , , , , Leave a comment

Well, butter my biscuits and call me surprised! Apple, the company that practically invented the walled garden, has just invited Google, its long-standing frenemy, over for a playdate. And not just any playdate – an AI-powered, privacy-focused, game-changing kind of playdate.

Remember when Apple cozied up to OpenAI, and everyone assumed ChatGPT was going to be the belle of the Siri-ball? Turns out, Apple was playing the field, secretly testing both ChatGPT and Google’s Gemini AI. And guess who stole the show? Yep, Gemini. Apparently, it’s better at whispering sweet nothings into Siri’s ear, taking notes like a diligent personal assistant, and generally being the brains of the operation.

So, what’s in it for these tech titans?

Apple’s Angle:

  • Supercharged Siri: Let’s face it, Siri’s been needing a brain transplant for a while now. Gemini could be the upgrade that finally makes her a worthy contender against Alexa and Google Assistant.
  • Privacy Prowess: By keeping Gemini on-device, Apple reinforces its commitment to privacy, a major selling point for its users.
  • Strategic Power Play: This move gives Apple leverage in the AI game, potentially attracting developers eager to build for a platform with cutting-edge AI capabilities.

Google’s Gains:

  • iPhone Invasion: Millions of iPhones suddenly become potential Gemini playgrounds. That’s a massive user base for Google to tap into.
  • AI Dominance: This partnership solidifies Google’s position as a leader in the AI space, showing that even its rivals recognize the power of Gemini.
  • Data Goldmine (Maybe?): While Apple insists on on-device processing, Google might still glean valuable insights from anonymized usage patterns.

The Bigger Picture:

This unexpected alliance could shake up the entire tech landscape. Imagine a world where your iPhone understands your needs before you even ask, where your notes practically write themselves, and where privacy isn’t an afterthought but a core feature.

But let’s not get ahead of ourselves. There are still questions to be answered. How will this impact Apple’s relationship with OpenAI? Will Google play nice with Apple’s walled garden? And most importantly, will Siri finally stop misinterpreting our requests for pizza as a desire to hear the mating call of a Peruvian tree frog?

Only time will tell. But one thing’s for sure: this Apple-Google AI mashup is a plot twist no one saw coming. And it’s going to be a wild ride.

February 27th: Reichstag Fire, a Dubious War, a Neutron, and a Goon: Reflections on a Day of Historical Significance

Posted on Posted in Agile, Agile Apocalypse, AI, Historic, History with a Twist, illustrations, Leonardo.ai, Scrum Master, shiel yule, vulture cultureTagged , , , , , , , , , , , , , , , , , Leave a comment

Good morrow, dear readers, and welcome to this grand exploration of historical happenings on this momentous day, February 27th! Now, I know what you’re thinking: “What could possibly connect a burning building in 1930s Germany, a war in the Middle East, a subatomic particle, and a comedic genius?” Well, hold onto your hats, folks, because we’re about to embark on a whirlwind tour of history, with a dash of Agile wisdom sprinkled in for good measure.

1933: The Reichstag Fire – A Domino Effect and Echoes of Today

Ah, 1933. A year of flappers, jazz, and… the rise of a certain rather unpleasant political party in Germany. On this very day, the Reichstag building, home to the German parliament, went up in flames. Now, while the exact cause of the fire remains a bit of a mystery (was it an inside job? Was it a lone wolf with a penchant for pyrotechnics?), the consequences were anything but ambiguous. The Nazis, ever opportunistic, seized upon the chaos, using the fire as an excuse to consolidate their power and crack down on any opposition. It was a crucial tipping point, a domino effect that ultimately led to one of the darkest chapters in human history.

And here’s the kicker, folks: history has a funny way of repeating itself. Look around the world today, and you’ll see echoes of those same tactics – fearmongering, scapegoating, the erosion of democratic institutions. It’s a stark reminder that we must remain vigilant, that the price of freedom is eternal vigilance, as some wise chap once said. And perhaps, just perhaps, a bit of Agile thinking wouldn’t go amiss. After all, Agile is all about adapting to change, responding to uncertainty, and embracing transparency – qualities that could come in handy when navigating the choppy waters of political turmoil.

1932: The Neutron – A Tiny Particle with a Big Impact

But enough about war and politics, let’s delve into the fascinating world of science! On this day in 1932, James Chadwick discovered the neutron, a tiny little particle that resides at the heart of every atom (except hydrogen, which is a bit of a loner). Now, I know what you’re thinking: “What’s so special about a neutron?” Well, my friends, this unassuming particle revolutionised our understanding of atomic physics, paving the way for nuclear fission, the Manhattan Project, and, of course, the atomic bomb.

But let’s not dwell on the negative. The discovery of the neutron also opened up exciting possibilities for nuclear energy, a clean and sustainable source of power that could potentially solve our planet’s energy woes. So, while the atom bomb might be a bit of a downer, let’s not forget the positive side of nuclear science. And who knows, maybe with a bit of Agile thinking, we can finally crack the code on safe and efficient nuclear fusion, ushering in a new era of clean energy for all.

1991: “Victory” in the Gulf – A War Criminal’s Legacy

Fast forward to 1991, and we find ourselves in the midst of another historical event: the end of the Persian Gulf War. “Victory” was declared, flags were waved, and everyone went home happy, right? Well, not quite. Let’s not forget that this was an illegal war, a war built on lies and deception, a war that resulted in the deaths of countless innocent civilians. And who was the mastermind behind this grand charade? None other than our very own Tony Blair, a man who, despite his war crimes, has yet to face any real accountability. Ah, the joys of being on the winning side – your crimes are swept under the rug, your misdeeds forgotten. It’s enough to make you lose faith in humanity, isn’t it?

But fear not, dear readers, for Agile is here to save the day! (Well, maybe not save the day, but at least offer some helpful principles.) Agile, with its emphasis on collaboration, iterative progress, and continuous feedback, could perhaps have prevented such a disastrous conflict. Imagine if our leaders had adopted an Agile mindset, if they had prioritised open communication and transparency, if they had been willing to adapt their plans based on new information (like there were no WMDs and it was all a ruse). Perhaps then, countless lives could have been saved, and the world would be a slightly less messed up place.

2002: Farewell to a Goon

And finally, we come to the comedic genius himself, Spike Milligan. On this day in 2002, the world bid farewell to one of the greatest comedic minds of all time. Milligan, with his absurdist humor, his irreverent wit, and his penchant for the downright silly, left an indelible mark on the world of comedy. He was a true original, a Goon Show pioneer, a master of the unexpected.

So, in honour of Milligan’s legacy, let’s approach the rest of today with a healthy dose of silliness and irreverence. After all, laughter is the best medicine, as they say. And who knows, maybe by embracing our inner Goon, we can find new and creative solutions to the world’s problems, and boy does it feel like there are plenty of those bubbling up at the moment.

And there you have it, folks! A whirlwind tour of historical events on this glorious 27th of February. Remember, history is more than just dates and facts – it’s a tapestry of triumphs and tragedies, of discoveries and disasters, of laughter and tears. Let us learn from the past, embrace the present, and, with a bit of Agile thinking and a Goon-like spirit, build a better future for all.

(P.S. If you’re feeling particularly adventurous, why not try writing your next Agile project report in the style of a Goon Show script? Your stakeholders might be a bit confused, but at least it’ll liven up those boring meetings!)