After I went over the various reasons why Agile may be perceived dead, or undead, it’s time to take a look on the reasons why Agile is alive – and I think it will remain so for some time. Maybe the goldrush times of Agile are over, but there are certainly some things that will stick. Let’s explore again.
Other entries in this series:
Continue reading Agile is aliveContinuing our journey in the “Agile is dead” space, I thought Halloween was the perfect date to explore the ways in which Agile is actually not just dead, but undead in many companies. If you read my earlier entry, you might have come across the thought that this was where we were heading towards. Let’s investigate further.
Other entries in this series:
Continue reading Agile is undeadThis entry is a continuation of the discussion I started yesterday. Stick long enough in any community, and over time you will hear claims about the movement being dead. For some communities, there is some reasonable truth to the claim – at a certain point in time. To others, there is not. Let’s tackle some of the background on why I think that Agile might be dead.
Other entries in this series:
Continue reading Agile is deadStick around long enough in the agile world, and sooner or later you come across the age-old discussion about whether agile is dead – as is the case at the time of me writing these lines. Just when I had that discussion again at two recent user groups, I recalled on my way back home that I had that kind of discussion about a decade ago. So, when I came home, I had to digest my old blog entries. To my surprise, I found something similar, yet, seemingly different in my blogosphere past.
Other entries in this series:
Continue reading “Agile is dead” – and I thought I had that conversation…Stick along long enough in software development, and you may have come along the ride for Agile software development practices, methodologies, and/or frameworks. Stick along long enough in that community – ok, that might be a reach too far, given that community only exists about 30 years or so. All of the above said, I notice some developments lately around the term Agile, and need to get my thoughts down. Not that I think I have a particular relevant perspective to start with. But maybe I can offer some perspective to one or another reader.
If you know me, you probably know that I have a tendency to look back on where did we come from to better understand things happening in the present. If you are not that kind of understander, maybe this blog entry might not be for you. So, be warned before moving on.
Continue reading My view on the current state of AgileSince minqlx seems to stand for “Mino’s Quake Live eXtension” and I go by the player name of ShiN0 in QL, I thought an obvious name for my Rust implementation of minqlx would be shinqlx for ShiN0’s Quake Live eXtension.
But before we dive into the first steps I took, maybe a few introductory words and maybe some references in case you want to go a similar route.
Continue reading Getting started with Rust and shinqlxI recall discussions in the early software craft days on the mailing lists. One thread, in particular, comes to mind today, that was about whether a good crafter should learn a new programming language every year to learn new coding styles and paradigms, and maybe bring those back to their usual work environment.
Last year, Craig Larman recommended learning the programming language Rust to help, especially with embedded programming. Linus Torvalds also allowed Rust as a third language in the Linux kernel development around the same time. It took me a while to actually try it when I found the perfect for me pet project to dive into.
Over the next couple of blog entries, I want to dive into some of my learnings and approaches. Today, let me give you an introduction to the project I picked for my personal Rust learning curve, where I am, and maybe give you an update now and then about the things I still have open to learn.
Continue reading So…, I got a bit rusty latelyIt’s been five years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. I already covered Jerry’s physical books in the past year. There are some gems left in some of the books he later published on Leanpub. This week, I will dive into three of them in one blog post: Experiential Learning: Beginning, Inventing, Simulation. (You can get most of the content of the physical books I reviewed on Leanpub as well – some might have a slightly different name.)
It’s been five years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. I already covered Jerry’s physical books in the past year. There are some gems left in some of the books he later published on Leanpub. This week, I will dive into Agile Impressions. (You can get most of the content of the physical books I reviewed on Leanpub as well – some might have a slightly different name.)
It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. One of the final physical books I recall reading is about Jerry’s work, not written by him, but by his students: The Gift of Time, edited by Fiona Charles with contributions from James Bach, Michael Bolton, Esther Derby, Naomi Karten, Tim Lister, Johanna Rothman, Dani Weinberg, his wife, and more. My copy of the book is copyrighted in 2008 and published by Dorset House.
