Category: shiel yule

The Zen of Stand-Ups (Or How to Look Busy for 15 Minutes)

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

The daily stand-up. That sacred ritual where we gather ’round the task board or dial into a Teams/Zoom/Slack/Hangout, pretending to be busy little bees while secretly plotting our escape to get more coffee. It’s a symphony of “yesterdays,” “todays,” and “blockers,” a chorus of mumbled updates and stifled yawns. But fear not, dear comrades, for I am here to guide you through this Agile labyrinth, to illuminate the path to stand-up enlightenment, or at least help you survive those 15 minutes without losing the will to live.

Now, the Agile Alliance, those wise gurus of the software development world, have defined the daily stand-up as a “vital coordination” meeting where we share “critical knowledge” and achieve “team cohesion.” Sounds rather grand, doesn’t it? Almost like a scene out of a Shakespearean play, with everyone waxing lyrical about their latest coding conquests. But let’s be honest, folks, the reality is often a tad less dramatic. More like a scene from a Monty Python sketch, with people repeating each other’s updates, forgetting what they did yesterday, and desperately hoping the nonsense spouted yesterday doesn’t come back on you as you cannot remember what you said.

But fear not, for I am here to unveil the true Zen of stand-ups, to reveal the secrets hidden beneath the surface of this Agile ceremony. So, without further ado, let us embark on this journey of discovery, this quest for stand-up enlightenment.

Three Questions – A Sacred Chant or a Mind-Numbing Mantra?

The Three Questions to start every day. Those hallowed words that echo through the halls of every Agile team:

  1. What did you do yesterday?
  2. What will you do today?
  3. What’s blocking you?

Sounds simple enough, right? Just a quick update on your progress, a glimpse into your future plans, and a cry for help if you’re stuck in a coding quagmire. But oh, how those questions can morph into a mind-numbing mantra, a repetitive drone that saps the very life force from your soul.

“Yesterday, I… um… Well, I started that thing… you know, the one mentioned in ticket… Oh, what was it called again? Ah, never mind, I’ll figure it out later.”

“Today, I’ll… Well, I’ll try to do some stuff… Maybe finish that thing I was supposed to do yesterday… If I can remember what it was.”

“Blockers? Oh, you know, the usual – meetings, emails, Netflix, YouTube, existential dread…”

And so it goes, day after day, a symphony of vague pronouncements and half-hearted commitments. But fear not, for there is hope! With a bit of Zen-like focus, we can transform those Three Questions into a powerful tool for self-reflection and team alignment. So, let us delve deeper into the mysteries of these Agile inquiries, to discover their true potential and unlock the secrets of stand-up success.

The Timebox – A Race Against the Clock or a Moment of Mindfulness?

The timebox, that relentless tyrant of the stand-up meeting! 15 minutes, they say. A mere quarter of an hour to squeeze in the hopes, dreams, and despairs of 7 to 9 souls. Why, that’s a paltry 2 minutes and 14 seconds per person, at best! (And don’t even get me started on those overachieving teams with 10 or more members – they’d be lucky to get a grunt in edgewise!) It’s enough to make a fellow contemplate the merits of a career change, perhaps to a profession where time is measured in leisurely hours rather than frantic minutes. Clockmaking, perhaps? Or snail farming? Anything but this mad dash against the clock, this frantic scramble to cram a day’s worth of Agile wisdom into a timeframe better suited to boiling an egg. But alas, such is the life of an Agile warrior, forever bound to the tyranny of the timebox, forever racing against the clock, forever trying to answer those three infernal questions before the Scrum Master’s gavel falls and we’re all condemned to the “parking lot” of eternal silence. And heaven forbid we should stumble upon a particularly loquacious teammate – why, they could eat up half the timebox with a single rambling monologue about their latest bug fix! 

But fear not, dear comrades, for even within this temporal straitjacket, there is hope for Zen-like calm. We must simply embrace the brevity, the succinctness, the haiku-like beauty of a well-crafted stand-up update. For in the words of the great poet, “Brevity is the soul of wit” – and, dare I say, the key to surviving the stand-up timebox with our sanity intact.

The Parking Lot – A Purgatory for Problems or a Crucible for Collaboration?

“OK let’s park that and we’ll come back to it”, that list of unresolved issues, that graveyard of forgotten tasks, that purgatory for problems that dare to raise their ugly heads during the sacred stand-up ceremony. It’s where good ideas go to die, where blockers fester and multiply, where team morale goes to wither and decay.

Ah, the parking lot was a very different concept when Agile was in its infancy. Once a haven for smokers, a place where the air was thick with nicotine and the clatter of brainstorming. A place where ideas were sparked, not by the sterile glow of a monitor, but by the shared embers of a real cigarette, the kind that left your fingers stained and your lungs yearning for a good scrub, before the advent of those newfangled vape contraptions, the ones that’ll probably turn out to be even more detrimental to our health, leaving us with glowing green lungs and a craving for unicorn tears. But I digress. The parking lot, you see, was more than just a place to indulge in a quick smoke; it was a crucible of creativity, a breeding ground for those “aha!” moments that often elude us in the confines of a stuffy meeting room. It was where the real magic happened, where those seemingly insurmountable blockers were wrestled into submission, where innovative solutions were hatched, and where the seeds of team camaraderie were sown. And let’s not forget the after-work gatherings, those impromptu pub crawls where the “parking lot” discussions continued, fuelled by pints of ale and a shared sense of purpose. 

But alas, the modern parking lot has lost its luster. It’s become a digital wasteland, a dumping ground for unresolved issues and forgotten tasks. A place where good ideas go to languish, where blockers metastasize into monstrous beasts, and where team morale goes to die a slow and agonizing death. It’s a purgatory for problems, a black hole of despair, a testament to our collective inability to confront the challenges that stand in our way.

But what if, we could reclaim the spirit of the old parking lot? What if we could transform this digital graveyard into a vibrant hub of collaboration, a place where problems are embraced, explored, and ultimately conquered? Imagine a stand-up where, instead of shunting issues aside, we gather ’round the metaphorical parking lot, our minds ablaze with the fire of a thousand cigarettes (metaphorical ones, of course, we wouldn’t want to set off the smoke alarm), and collectively brainstorm solutions, our voices echoing with the camaraderie of a late-night pub session. Imagine a stand-up where the parking lot becomes a hotbed of innovation, a breeding ground for those brilliant, out-of-the-box ideas that only emerge when we dare to venture beyond the confines of our comfort zones.

Okay, okay, I might be getting a bit carried away here. But the point is, folks, the parking lot doesn’t have to be a symbol of defeat. With a bit of that old-school parking lot spirit, a dash of Zen-like optimism, and perhaps a pint or two of creative inspiration, we can transform it into a powerful engine for problem-solving, team building, and, dare I say, project completion.

The “No Problem” Meeting – A Sign of Success or a Symptom of Dysfunction?

Next we come to the “no problem” meeting. That blissful stand-up where everyone reports smooth sailing, where no one dares to utter the dreaded “b-word”, where the task board glows with the green light of effortless progress. It’s a manager’s dream, a Scrum Master’s paradise, a utopia of Agile efficiency.

But what if this “no problem” facade is merely a mask, a deceptive veneer hiding a festering undercurrent of dysfunction? What if those smiling faces and upbeat reports are merely a performance, a carefully choreographed act designed to conceal the truth? What if, beneath the surface of this seemingly perfect stand-up, lies a team riddled with fear, insecurity, and a deep-seated reluctance to admit weakness?

Maybe a little bit too cynical here. But the point is, folks, the absence of problems doesn’t always equate to success. Sometimes, it’s a sign that something is amiss, that there’s a communication breakdown, a lack of trust, or a culture of fear that prevents people from speaking up. So, let us be wary of the “no problem” meeting, and instead strive for a stand-up where honesty and transparency prevail, where problems are acknowledged and addressed, and where the team can work together to overcome challenges and achieve true Agile greatness.

And with that, dear readers, I shall conclude this rambling exploration of the Zen of stand-ups. May your daily gatherings be filled with laughter, enlightenment, and a healthy dose of absurdist humor. And remember, even if your stand-ups are more Python-esque than Shakespearean, there’s still hope for achieving Agile nirvana, or at least surviving those 15 minutes with your sanity intact.

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!)

Agile: My Love-Hate Relationship with Iteration

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

Iteration. The word itself conjures up images of spinning wheels, cyclical patterns, and that hamster in its never-ending quest for… well, whatever a hamster sees in those wheels. But “iteration” is more than just a fancy word for “doing something again and again.” It’s a fundamental concept that permeates our lives, from the mundane to the profound.

Think about your morning routine. Wake up, stumble to the bathroom, brush your teeth (hopefully), make coffee (definitely). That’s an iteration, a daily ritual repeated with minor variations. Or consider the changing seasons, the ebb and flow of tides, the endless cycle of birth, growth, decay, and renewal. Iteration is the rhythm of existence, the heartbeat of the universe.

In the world of art and creativity, iteration takes center stage. Painters rework their canvases, musicians refine their melodies, writers revise their manuscripts – all in pursuit of that elusive perfect expression. Each iteration builds upon the last, refining, reimagining, and ultimately transforming the original concept into something new and hopefully improved.

But let’s not get all misty-eyed about iteration. It can be a cruel mistress, a source of frustration, a never-ending loop of “almost, but not quite.” Think about that DIY project that seemed so simple at first but has now become a Frankensteinian monster of mismatched parts and questionable design choices. Or that recipe you’ve tried a dozen times, each attempt yielding a slightly different (disastrous) result. Iteration, in these moments, feels less like progress and more like a punishment for our hubris.

And if we stretch it into the political arena, iteration takes on a particularly cynical flavor. The UK, with its revolving door of prime ministers, its endless Brexit debates, and its uncanny ability to elect leaders who promise change but deliver more of the same, is a prime example. Each election cycle feels like an iteration of the last, a Groundhog Day of broken promises, partisan squabbles, and that nagging sense that no matter who’s in charge, nothing really changes. Even the emergence of new parties, with their fresh faces and bold manifestos, often seems to get sucked into the same iterative loop, their initial idealism slowly eroded by the realities of power and the entrenched political system. Iteration, in this context, feels less like progress and more like a depressing reminder of our collective inability to break free from the past.

And then there’s Agile. Ah, Agile. The methodology that puts iteration on a pedestal, enshrining it as the holy grail of software development. Sprints, stand-ups, retrospectives – all designed to facilitate that relentless cycle of build, measure, learn. And while the Agile evangelists wax lyrical about the beauty of iterative development, those of us in the trenches know the truth: iteration can be a messy, chaotic, and often frustrating process.

We love iteration for its ability to adapt to change, to embrace uncertainty, to deliver value incrementally. We hate it for the endless meetings, the ever-growing backlog, the constant pressure to “fail fast” (which, let’s be honest, doesn’t always feel so fast). We love it for the sense of progress, the satisfaction of seeing a product evolve. We hate it for the scope creep, the shifting priorities, the nagging feeling that we’re building the plane as we fly it.

But love it or hate it, iteration is the heart of Agile. It’s the engine that drives innovation, the fuel that powers progress. And while it may not always be pretty, it’s undeniably effective. So, embrace the iteration, my friends. Embrace the chaos. Embrace the uncertainty. And maybe, just maybe, you’ll find yourself falling in love with the process, even if it’s a slightly dysfunctional, love-hate kind of love.

Wagile: In an iterative world, is there still a place for Waterfall

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

So Agile. It’s the buzzword du jour, the management mantra, the thing everyone’s been talking about for at least 10 years. Apparently, it is the antidote to all our project woes. Because, you know, Waterfall is so last century. And so, it seems, is cognitive function.

To be honest, Waterfall had a good run. Planning everything upfront, meticulously documenting every single detail, then… waiting. Waiting for the inevitable train wreck when reality collided with the perfectly crafted plan. It was like building a magnificent sandcastle, only to have the tide laugh maniacally and obliterate it. Ah fun times at Ridgemont High (aka RBS).

Agile, on the other hand, is all about embracing the chaos. Sprints, stand-ups, retrospectives – it’s a whirlwind of activity, a constant state of flux. Like trying to build that sandcastle while surfing the waves. Exhilarating? Maybe. Efficient? Debatable. Sane? No comment.

The Agile manifesto talks about “responding to change over following a plan.” Which is excellent advice, unless the change involves your entire development team suddenly deciding they’ve all become Scrum Masters or Product Owners. Then, your carefully crafted sprint plan goes out the window, and you’re left wondering if you accidentally wandered into a performance art piece.

And don’t even get me started on the stand-ups. “What did you do yesterday?” “What are you doing today?” “Are there any impediments?” It’s like a daily therapy session, except instead of delving into your inner demons, you’re discussing the finer points of code refactoring. And the “impediments”? Oh, the impediments. They range from “the coffee machine is broken” to “existential dread” (which is a constant in software development). It’s a rich tapestry of human experience, woven with threads of caffeine withdrawal and the gnawing fear that your code will spontaneously combust the moment you deploy it.

But the stand-up is just the tip of the iceberg, isn’t it? We’ve got the sprint planning, where we all gather around the backlog like it’s a mystical oracle, divining which user stories are worthy of our attention. It’s a delicate dance of estimation, negotiation, and the unspoken understanding that whatever we commit to now will inevitably be wildly inaccurate by the end of the sprint. We play “Planning Poker,” holding up cards with numbers that represent our best guesses at task complexity, secretly hoping that everyone else is as clueless as we are. It’s like a high-stakes poker game, except the only prize is more work.

Then there’s the sprint review, where we unveil our latest masterpiece to the stakeholders, praying that they won’t ask too many awkward questions. It’s a bit like showing your unfinished painting to an art critic, except the critic also controls your budget. We demonstrate the new features, carefully avoiding any mention of the bugs we haven’t fixed yet, and bask in the fleeting glow of (hopefully) positive feedback. It’s a moment of triumph, quickly followed by the realization that we have another sprint review looming in two weeks.

And let’s not forget the retrospective, the post-mortem of the sprint. We gather in a circle, armed with sticky notes and a burning desire to improve (or at least to vent our frustrations). We discuss what went well, what went wrong, and what we can do differently next time. It’s a valuable exercise in self-reflection, often culminating in the profound realization that we’re all just trying our best in a world of ever-changing requirements and impossible deadlines. It’s like group therapy, except instead of leaving feeling lighter, you leave with a list of action items and a renewed sense of impending doom. Because, you know, Agile.

But, amidst the chaos, the sprints, the stand-ups, there’s a glimmer of something… maybe… progress? Just maybe, Agile isn’t completely bonkers. Perhaps it’s a way to navigate the ever-changing landscape of software development, a way to build sandcastles that can withstand the occasional rogue wave. Or maybe it’s just a really elaborate way to procrastinate on actually finishing the project.

Either way, one thing’s for sure: it’s certainly more entertaining than Waterfall. And who knows, maybe in the process, we’ll all be forced to downgrade our cognitive functions to “basic operating level.” Who needs advanced cognitive functions when you have Agile and AI?

But amidst the gentle ribbing and self-deprecating humour, there is a serious point here. Agile, like any methodology, isn’t a magic bullet. It’s a tool, and like any tool, it can be used effectively or ineffectively. The key is understanding where Agile truly shines, where it needs to be adapted, and where – a touch of Waterfall might actually be the right approach.

That’s where I come in. With years of experience navigating the Agile landscape (and yes, even surviving a few Waterfall projects in my time), I can help your organisation cut through the jargon, identify the real pain points, and implement solutions that actually deliver results. Whether you’re struggling with sprint planning, drowning in a sea of sticky notes, or simply wondering if all this Agile stuff is worth the hassle, I can provide clarity, guidance, and a healthy dose of pragmatism. Because ultimately, it’s not about blindly following a methodology, it’s about finding the right approach to deliver value, achieve your goals, and maybe, just maybe, retain a little bit of your sanity in the process.

If you’re ready to move beyond the Agile buzzwords and build a truly effective development process, let’s talk.

Riverside Museum: Where History Met a Mac-mini Powered Time Machine

Posted on Posted in love/hate, shiel yule, vulture cultureTagged , , , , , , Leave a comment

Rewind to about 2010-11. Imagine a younger, more naive version of myself, sporting questionable fashion choices and an unwavering belief in the power of technology. I was working at this cool little agency called 55 Degrees, a melting pot of designers, developers, and video wizards. We were all about pushing the boundaries of digital storytelling, and we landed this epic project: the Riverside Museum in Glasgow.

Now, this wasn’t just any museum. It had just been built on the historic site of Clyde shipbuilding and was a cathedral of transport, a shrine to all things that moved, from steam locomotives to skateboards. With a loose brief, a band of eighteen of us were tasked with bringing these objects to life. Not with dusty labels and boring timelines, but with stories. Emotive, engaging, personality-packed stories.

So, we rolled up our sleeves and got to work. We churned out 34 documentary films, capturing the essence of Clyde-built ships, vintage cars, and even a penny-farthing or two. We crafted audio exhibits that transported you to bustling Victorian streets and roaring shipyards. We animated historical figures, giving them voices and quirks that would make a Disney character jealous.

Amidst this whirlwind of maritime history and technological ambition, I had my own pet project: a celebration of Glasgow’s skateboarding scene. See, just the year before, I had launched Skateboard Scotland in Edinburgh and gotten involved in the burgeoning skatepark scene. So, naturally, I had to inject a bit of that rebellious spirit into the Riverside Museum. Thus, the “Board Games” exhibit was born.  (And it was pretty darn satisfying to see it still going strong 15 years later, looking exactly the same, so much for progress.)

But the real challenge, the Everest of our digital ambition, was the interactive exhibits. Riverside wanted visitors to engage with the collection, to delve deeper, to become part of the story. And how did we achieve this, you ask? With an army of iPads, of course. Well, not actual iPads (they weren’t quite a thing back then), but these massive, portrait-oriented touchscreens we called “eIntros.” (Story Player)

These eIntros were our digital playground. We packed them with information, photos, videos, and interactive elements, all controlled by a central Content Management System (CMS). But here’s where our hubris kicked in. Did we use an existing CMS? Nope. We built our own. From scratch. With Ruby on Rails. Because, why not? (At this point, you might be picturing a montage of frantic coding, fuelled by caffeine and the unshakeable belief that we were reinventing the wheel. You would be right.)

This CMS, our Frankensteinian creation, was a beast. It managed everything. The eIntros, the games, the “What’s On” screens, even the museum lighting (because who needs a light switch when you have a CMS?). It could spit out HTML5, JSON, XML – you name it. We were like digital puppet masters, pulling the strings of the entire museum experience.

And because we had this perfectly controlled environment (a developer’s utopia), we went wild with the latest web technologies. CSS3 animations? Check. JavaScript wizardry? Double-check. HTML5 video? Oh, you better believe it. We even built our own full-screen browser, because Safari just couldn’t handle what we wanted it to do.

Then came the games. Multiplayer, interactive extravaganzas that had visitors racing trams, building bridges, and navigating historical maps. We built a custom framework, naturally, because off-the-shelf solutions are for the faint of heart.

And because we’re nothing if not extra, we threw in some generative graphics for good measure. Quartz Composer screensavers danced hypnotically on screens, and the Donor Wall became a mesmerising tapestry of names, brought to life with Processing.

The final pièce de résistance? A show control system baked right into the CMS. We could control projectors, media players, even the model ships sailing across a giant video projection, all from our custom-built command centre. It was a symphony of technology, a masterpiece of over-engineering.

Some of this digital wizardary has been lost to the sands of time (or, more accurately, the depths of the museum archives). But hey, we did manage to open-source one little gem: Makitzo, a Ruby deployment tool that saved our sanity during installation. Because, without it, we’d probably still be there, wrestling with cables and cursing Steve Jobs.

So, there you have it. The story of how a bunch of tech-obsessed creatives turned a museum into a giant, interactive playground. It was a wild ride, a testament to the power of passion, innovation, and a whole lot of caffeine. And while the technology might be outdated now, the memories (and the occasional nightmare about rogue CSS animations) live on.

The demise of 55 Degrees left a bunch of talented people out of work and some of us out-of-pocket but the museum is still going strong and the fact that most of the tech and content is still attracting visitors 14 years since it opened, to the tune of 1.3 million in 2023, is testimony to a talented team of creatives and techies, the names I can remember:

Tom Beddard

Russ Kyle

Dave Morrow

Joseph Briffa

Jason Frame

Alistair Macdonald

Tomek Augustyn 

Ian Airley

Shiel Yule

My Statistical Odyssey: How I Finally Conquered “The Art of Statistics” (without a brain aneurysm)

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

Gather ’round because I have a tale to tell. A tale of statistical daring-do, of intellectual battles fought and won (eventually), and of a book that nearly broke me but ultimately sparked a lifelong love affair with data.

The hero of our story? “The Art of Statistics” by David Spiegelhalter. The villain? My own statistically insignificant attention span.

Our story begins in 2019, a simpler time when “pandemic” was just a scary word in a board game and sourdough starter wasn’t a mandatory kitchen accessory. I bright-eyed and bushy-tailed, decided to tackle this tome, convinced I would emerge a statistical savant, capable of predicting the lottery numbers and the exact moment my toast would burn.

Turns out, statistics is a bit more complicated than the pie charts I used to colour in at school. Who knew? So began my years-long wrestling match with this book. I’d read a chapter, feel my brain cells staging a mass exodus, and promptly retreat to the soothing embrace of a comic, minecraft or Fortnite. Rinse and repeat.

But like a stubborn stain on my favorite shirt, I just couldn’t get rid of this book. So, I persevered. I re-read chapters. I Googled terms that sounded like they belonged in a Harry Potter spellbook (“heteroscedasticity,” anyone?). I even resorted to drawing diagrams on my windows with dry-erase markers (much to the confusion of my neighbours).

And slowly, miraculously, something started to click. David Spiegelhalter, bless his statistically significant heart, has a way of making even the most mind-bending concepts understandable. He’s like the data whisperer, the statistical Yoda, the… okay, I’ll stop with the analogies. But seriously, his writing is engaging, witty, and surprisingly relatable. Plus, the examples he uses are fascinating – from the probability of winning the lottery (spoiler alert: don’t quit your day job) to the statistical quirks of birth dates and death rates.

This book, my friends, was a journey. A statistical odyssey, if you will. It challenged me, frustrated me, and ultimately, inspired me. It sparked a curiosity about data that led me to the Google Data Analytics course I’m currently immersed in (more on that in another blog post, because this one is already longer than the average attention span, statistically speaking).

So, what’s the moral of the story? Well, first, never underestimate the power of a good book. Second, statistics can be fascinating. And third, if I can conquer “The Art of Statistics,” then by the transitive property of awesomeness, I can probably conquer this data analytics course too.

P.S. Pelican Books, you guys are the real MVPs. Bringing back all those school textbook memories (the good ones, mostly). And for publishing this gem of a book? You deserve a statistically significant high-five.

My Subconscious is Now a Loyal Customer of the Dallergut Dream Department Store

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

Okay, confession time. I have a problem. A delightful problem, but a problem nonetheless. It’s called the Dallergut Dream Department Store. Specifically, two Dallergut Dream Department Store-shaped problems.

Remember over Christmas when I raved about this whimsical Korean novel? The one where you can buy dreams? Yeah, that one. Well, I finished it, and I was bereft. Like, my brain was wandering around the real world, bumping into things and muttering, “But… where are the dream catalogues?”

Luckily, my literary fairy godmother (aka the internet) whispered sweet nothings about a sequel. A sequel! Turns out, my dream-buying days were far from over. And let me tell you, “Welcome to the Dream Department Store” was even better than the original. It was like going back to your favorite cafe and discovering they now serve your favorite cake with extra sprinkles.

Seriously, these books are pure magic. Miye Lee has this incredible way of weaving stories that just pull you in. I devoured both books (okay, maybe not quite in one sitting, but the temptation was REAL). The writing style is so refreshing. It’s different from what I’m used to in Western literature, but in the best possible way. It’s…gentle? Magical? Like being wrapped in a warm blanket made of storytelling.

Now, I have to give a shout-out to Sandy Joosun Lee, the translator. I’m convinced a huge part of the books’ charm is down to her skill. And I totally agree with her comment in the second book – I’ve been dreaming like crazy since I started reading these at bedtime! My subconscious is clearly a loyal customer of the Dallergut Dream Department Store. I’m pretty sure I bought a flying unicorn and a lifetime supply of chocolate in my last dream. (Sadly, neither were delivered. Dream Department Store customer service, if you’re reading this, I’d like to file a complaint.)

So, if you’re looking for a book that will transport you to another world, make you believe in the impossible, and maybe even inspire some seriously epic dreams, then I cannot recommend the Dallergut Dream Department Store books enough. Go. Read. Them. Your brain (and your dream life) will thank you. Just don’t blame me if you start trying to pay for your morning coffee with dream coupons. I warned you.

My Bank Account is Safe, But My Dream Wallet is Officially Empty (Thanks, Dallergut!)

From Zero to Data Hero: My Google Data Analytics Journey

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

Just a few short months ago, the world of data analytics felt like a vast, uncharted ocean. Now, after completing Google’s Data Analytics Professional Certificate (or at least the 12+ modules that make up the learning path – more on that later!), I feel like I’ve charted a course and am confidently navigating those waters. It’s been an intense, exhilarating, and sometimes head-scratching journey, but one I wouldn’t trade for anything.

My adventure began in October 2024, and by February (this week) 2025, I had conquered (most of) the learning path. Conquer is the right word, because it was definitely an intense learning curve. 2000’s dev junior SQL skills? Yeah, they got a serious dusting off. And my forgotten Python, which was starting to resemble ancient hieroglyphics? Well, let’s just say we’re on speaking terms again.

The modules covered a huge range of topics, from the foundational “Introduction to Data Analytics on Google Cloud” and “Google Cloud Computing Foundations” to more specialized areas like “Working with Gemini Models in BigQuery,” “Creating ML Models with BigQuery ML,” and “Preparing Data for ML APIs on Google Cloud.” (See the full list at the end of this post!) Each module built upon the previous one, creating a solid foundation for understanding the entire data analytics lifecycle.

But the real stars of the show for me were BigQuery and, especially, Looker Studio. I’ve dabbled with other data visualization tools in the past (mentioning no names… cough Microsoft cough Tableau cough), but Looker Studio blew me away. It’s intuitive, powerful, and just… fun to use. Seriously, I fell in love. The ease with which you can connect to data sources and create insightful dashboards is simply unmatched. It’s like having a superpower for data storytelling!

One of the biggest “aha!” moments for me was realizing the sheer power of data insights. Mining those hidden gems from large datasets is incredibly addictive. And the fact that Google makes it so easy to access public datasets through BigQuery? Game changer. It’s like having a data goldmine at your fingertips.

This learning path has ignited a real passion within me. So much so that I’m now pursuing a Data Analysis Diploma, which I’m hoping to wrap up before June. And, because I apparently haven’t had enough learning, I’m also signing up for the Google Cloud Data Analytics Professional Certificate. I’m all in!

I have to say, the entire Google Cloud platform just feels so much more integrated and user-friendly compared to the Microsoft offerings I’ve used. Everything works together seamlessly, and the learning resources are top-notch. If you’re considering a career in data analytics, I would wholeheartedly recommend the Google path over other options.

I’m especially excited to dive deeper into the machine learning aspects. And the integration of Gemini? Genius! Having it as a code buddy has been a huge help, especially when I’m wrestling with a particularly tricky SQL query or trying to remember the correct syntax for a Python function. Seriously, it’s like having a data analytics guru by my side.

Stay tuned for future posts where I’ll be sharing more about my data analytics journey, including tips and tricks, project updates, and maybe even some data visualizations of my own!

Coursera do an official course = https://www.google.com/url?sa=E&source=gmail&q=https://www.coursera.org/professional-certificates/google-data-analytics – this you get a recognised formal professional certificate.

Or jump into Google Cloud Skills Boost: https://www.cloudskillsboost.google/ and get yourself a Cloud account and friendly with Gemini.

Modules Completed:

  • Work with Gemini Models in BigQuery
  • Analyzing and Visualizing Data in Looker Studio
  • BigQuery for Data Analysts
  • Boost Productivity with Gemini in BigQuery
  • Create ML Models with BigQuery ML
  • Derive Insights from BigQuery Data
  • Developing Data Models with LookML
  • Google Cloud Computing Foundations- Data, ML, and AI in Google Cloud
  • Introduction to Data Analytics on Google Cloud
  • Manage Data Models in Looker
  • Prepare Data for Looker Dashboards and Reports
  • Prepare Data for ML APIs on Google Cloud

The Ghost of October: Echoes of the Cuban Missile Crisis in Today’s World

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

Sixty-one years ago, the world held its breath. President John F. Kennedy, in a somber address on October 22nd, 1962, revealed the chilling discovery of Soviet nuclear missiles in Cuba. The Cuban Missile Crisis, a 13-day standoff, brought humanity closer to nuclear annihilation than ever before.

Kennedy’s resolute yet measured response, a naval blockade combined with back-channel diplomacy, ultimately averted catastrophe. The Soviets backed down, removing the missiles in exchange for a US pledge not to invade Cuba and the dismantling of US missile installations in Turkey.

But the ghost of October lingers. Today, a multitude of conflicts simmer across the globe, each with the potential to escalate into a wider conflagration. Gaza, Lebanon, Palestine, Iran, Israel – the Middle East remains a tinderbox of tensions. The war in Ukraine grinds on, with the spectre of nuclear escalation a constant worry. Sudan, Georgia, Mexico, Haiti, the Sahel, Myanmar – all face internal strife or external pressures that threaten to boil over.

A World on Edge, Lacking a Steady Hand

The Cuban Missile Crisis was defused through a combination of firmness and diplomatic finesse. Kennedy, despite facing immense pressure to launch a military strike, chose a path of calculated restraint. Crucially, he had a direct line of communication with Khrushchev, allowing for tense but ultimately successful negotiations.

Today, that kind of leadership seems absent from the world stage. The current geopolitical landscape is fractured, with mistrust and animosity running high. While diplomatic efforts are underway in various hotspots, the absence of a strong, universally respected leader capable of bridging divides and de-escalating tensions is deeply concerning.

What Can Be Done?

While the challenges are immense, there are steps that can be taken to mitigate the risks:

  • Strengthening international institutions: The UN and other multilateral organisations need to be empowered to play a more effective role in conflict prevention and resolution.
  • Investing in diplomacy: Sustained diplomatic efforts are crucial to address the root causes of conflicts and build trust between adversaries.
  • Promoting dialogue and understanding: Open communication channels and cultural exchanges can help to break down barriers and foster cooperation.
  • Exercising restraint: Leaders must resist the temptation to resort to military force and instead prioritise peaceful solutions.

The world cannot afford to sleepwalk into another October crisis. The echoes of 1962 should serve as a wake-up call, urging us to pursue a path of peace and diplomacy before it’s too late.