(Jan 31, 2023)
It is not given to us to be perfect, nor to do perfect work. But this program, surely it's close? Let's talk about the value of tiny improvements.
(Jan 30, 2023)
Now that the Collision Strategies area all broken out, let's have a look and see what we think about them. Am I reversing yesterday's work? Yes, some of it. That's OK. (Ninth decade? Really?)
(Jan 29, 2023)
After an idea that doesn't pan out, we complete the installation of CollisionStrategy objects. We begin assessing what we like — and what's troubling.
(Jan 28, 2023)
We'll try another one of our CollisionStrategy things. I was hoping for some reuse but am not clear yet how to get it, nor whether its really worth it. I think we'll complete all four Strategies and then look around.
(Jan 28, 2023)
Delegation using Kotlin's `by` seems not to be quite the thing, though I believe I could make it work. I think that late yesterday I invented the Strategy pattern. Let's find out.
(Jan 27, 2023)
As promised, we'll discuss `by` delegation, but I now think that it isn't going to be as useful as I had hoped. I could be wrong, and — oddly enough — hope that I am.
(Jan 25, 2023)
Let's simplify some tests. I think we can get `knownObjects` out of Game.
(Jan 25, 2023)
Let's see how we like the look of the new GameCycler, and review how it went. There are things to do. Could we get more objects to be immutable? That would be interesting.
(Jan 24, 2023)
Let's move some more code over into GameCycler. We complete the Strangler!
(Jan 24, 2023)
Let's look at cohesion, duplication, and other considerations. Maybe we can get a bit more gilding on this lily.
(Jan 23, 2023)
I've gone back and forth on how much type information to preserve. Let's try to compare the two.
(Jan 22, 2023)
With the simpler SpaceObjecgCollection in place, it's time for Transaction. Do we just check out the old version? No, we do not. But why not? Also: You are waffling, sir!
(Jan 21, 2023)
I think we're ready to try the new simpler collision scheme, which is really the old collision scheme from before we started this centralized version. We'll discuss further whether this is a step backward or forward.
(Jan 20, 2023)
I really thought I was finished improving the centralized version, but these small changes will, I think, make things much simpler overall.
(Jan 20, 2023)
There's a lot to like about the centralized version, but this morning I realized that it's far from ideal. Let's explore why and what to do.
(Jan 19, 2023)
Let's explore some possibilities for improvement. Maybe we can even reduce some duplication. That would be nice. Added in Post: Almost a complete waste of time! Dammit! My hopes are dashed!
(Jan 18, 2023)
Last night, I made a change that I now believe to be a mistake. In fact, I did it twice. Further: We begin to draw a conclusion.
(Jan 17, 2023)
With changes to Transaction, I think I can get rid of most of the type checking in the system. I could be right ...
(Jan 17, 2023)
I think that code in Missile is a bit too clever. I may have a better idea. Let's find out. Also: remarks on Jira.
(Jan 16, 2023)
Let's rename all the `interactWithThisAndThat` to `interact`. I think that will reduce unnecessary noise. We'll see.
(Jan 16, 2023)
The new Interaction object is in place. Now let's work to unwind the calls through Subscriptions, moving toward simplifying the hierarchy. Added in Post: Woot!
(Jan 15, 2023)
Let's do interactions in our new type-sensitive style. Let's do it with an object. Let's test-drive the object.
(Jan 14, 2023)
Let's try replacing interactions all at one go. It might not be too difficult. In Post: I do it, it works, I roll it back.
(Jan 14, 2023)
I think we just have one more `finalize` to remove. After that, well, I hope not the Deluge. Also: Do you have a lessón for your minkey?
(Jan 13, 2023)
I'll take another run at finalize. I expect to succeed this time. I could be wrong.
(Jan 13, 2023)
Today, probably, we'll push on with making things more cognizant of type. Probably in Transaction. But let's think first. (Added in Post: we don't do what I thought.)
(Jan 12, 2023)
I'm rather sure there is no active use of the `attackers` and `targets` collections. Let's remove them.
(Jan 12, 2023)
We're engaged in a somewhat extended diversion in our centralization effort, aimed at making better use of Kotlin's strict typing. Let me explain.
(Jan 11, 2023)
Last night, in a stroke of good fortune, I was schooled by GeePaw Hill. I may have learned an idea, and I may be able to learn to apply it. Also, ducks, and an oblique reference to a koala bear. Added in Post: Nice result so far.
(Jan 10, 2023)
Let's experiment today with the sketched collision logic that I threw in a number of days ago. Maybe it has been long enough to see its flaws. Hypotenuse!
(Jan 9, 2023)
This morning, we Big Plan a bit, then do small changes. We're refactoring toward a new design: we're not doing a big rewrite. It's going quite well.
(Jan 8, 2023)
I think we can simplify things a bit by adjusting the hierarchy of our space objects, now that a number of subclasses have been removed. Let's see if I'm right. It could happen.
(Jan 7, 2023)
I had an idea the other day, something I should probably have done a while back, so with a little time this afternoon, I'll try it now.
(Jan 7, 2023)
I plan to wrap up the centralized version of Ship creation this morning, with the concomitant removal of two classes from the mix and the system.
(Jan 6, 2023)
I have a cunning plan for doing the ship insertion in the centralized version. I predict that this is going to be nice.
(Jan 5, 2023)
I have a little time. Let's try another experiment.
(Jan 5, 2023)
It's time to address centralizing creation of the Ship, including hyperspace. This is one of the more complicated bits in the game. (Ron keeps a spike. Shall we withhold his treats?)
(Jan 4, 2023)
I have a test that sometimes fails. I have no notion of how that can be happening. Let's find out.
(Jan 4, 2023)
As we centralize more and more code, the Game class is getting messy. Should we start to improve it now, or let it get worse before it gets better? Some thoughts about thinking.
(Jan 3, 2023)
I have a little time. Let's see if we can take a few small steps toward wave-making. Should be possible, I had it working yesterday.
(Jan 3, 2023)
Today, I was hoping to finish up the new centralized wave-making. But first I need to bring my testing up a bit. Added in Post: Includes Ron's Jira.
(Jan 2, 2023)
Today, I think I'll start on moving the WaveMaker logic into the game. There are issues.
(Jan 1, 2023)
I'll begin this new year as I ended the old one, programming and writing about it. Today, I think we'll work on score.
(Dec 29, 2022)
Now on a somewhat better build, I'll begin by redoing yesterday's changes, and then continue with the centralizing work. Bison?
(Dec 29, 2022)
Continuing to work on creating a centralized version of Asteroids, for comparison with the current decentralized design. Amazing the things I don't know how to do.
(Dec 28, 2022)
I think I can start on a collision detection thing. Shall I test it, or spike it?
(Dec 28, 2022)
An insight and an idea show me a way to approach centralized control. I think it'll be quite nice.
(Dec 27, 2022)
Let's try another way of decelerating to see if we like it better.
(Dec 26, 2022)
While I muse about a different design, there are a few things that we need to do, and I need something to distract myself. Things go oddly but turn out OK. Details in Summary.
(Dec 24, 2022)
Not that this version is exactly done, but I was thinking: Would it be interesting to start over and do Asteroids in a different style?
(Dec 19, 2022)
Going to try for a light morning, as I have an appointment. Let's check the checklist and pick some small but beneficial changes
(Dec 19, 2022)
Yes, I know there's a closed-form solution for targeting. Let's see if there's something simpler. But first, a bit more safety.
(Dec 17, 2022)
The Saucer can fire targeted missiles. Let's explore what we might do about that.
(Dec 15, 2022)
'When things get too complicated, add simplicity.'' Let's try that.
(Dec 14, 2022)
An issue in the design troubles me. I'm not sure whether it really should trouble me, but I think something needs to be done. I really find this hard to think about. I'll discuss why at the end. And I'll tell you what you should do.
(Dec 12, 2022)
The Kotlin game appears to me to have a different scale factor between asteroids and ship. I don't see yet what's going on. I discover that I've done a very poor job. Don't read this, it embarrasses me.
(Dec 9, 2022)
Can you believe that I forgot the flare of the ship's exhaust when it accelerates? No wonder I can't win this game.
(Dec 8, 2022)
The original game spawns more and more asteroids. I'm terrible at the game but I guess we need the feature. Just a little afternoon playing around.
(Dec 8, 2022)
The game should display some info about the keys to operate it. Not that I don't know, or the other person, but there might be one more person ...
(Dec 7, 2022)
When it's GAME OVER and we want to go again ... where do we put the quarter? A HARD DECISION: which way would you go?
(Dec 6, 2022)
I'd like to clean up ship emergence. I believe it can be more clear and if it can be, it should be. BONUS: A movie of the most interesting bug so far.
(Dec 5, 2022)
I think I've thought of a defect. Let's find out.
(Dec 5, 2022)
Best laid plans scarcely get past the first paragraph.
(Dec 4, 2022)
This morning, out of the blue, I plan to assess a core aspect of my Asteroids design: the subscription model. The conclusion surprised me. (Yeah, click bait. Skip to the end if you're that way.)
(Dec 3, 2022)
the OneShot and DeferredAction are looking for places to be used. It's 'small boy with hammer' time!
(Dec 3, 2022)
In which, our intrepid hero has yet another idea. Will this one be better, or just another idea?
(Dec 2, 2022)
Got this thing, might as well use it. Let's eliminate WaveMaker.
(Dec 2, 2022)
Where do ideas come from? I don't know. Where do they go? Into the code, of course.
(Dec 1, 2022)
The game is supposed to give you a finite number of ships. And it's supposed to be possible to earn new ships at certain levels of point score. How could my 'independent' objects do that?
(Dec 1, 2022)
Finalize existed because an object could be destroyed by another object. The unwritten rule now is that objects do not destroy other objects. Can we get rid of finalize?
(Nov 30, 2022)
I improved the Splats a bit last night. I report on last night, think about design, improve Saucer some more, and feel rather ashamed of myself. But good, too.
(Nov 29, 2022)
Let's have the saucer fire randomly. Should be about what I need for an afternoon session.
(Nov 29, 2022)
Let's give the Saucer some more capability. And a question/request to readers.
(Nov 28, 2022)
Too much duplication in colliding. Let's sort it a bit.
(Nov 28, 2022)
As much fun as I'm having with the odd simplicity / complexity mix of this program, it's time for a feature. We'll do the Saucer ... or at least start on it.
(Nov 27, 2022)
Still thinking about the essence of this design and what it implies. This time for the game, not the world. I am fascinated and love what it is ... and isn't. In a real sense ... it isn't a game at all.
(Nov 27, 2022)
Events of the morning cause me to reflect on what the odd design of my Asteroids program might tell us about life in general. Turning social, a bit. Observing, not deciding.
Social ]
(Nov 26, 2022)
I'm renaming Interactions to Subscriptions. IDEA helps. What else?
(Nov 26, 2022)
Now that all the SpaceObjects are broken out, we have duplication. Let's see how much and how we might improve things.
(Nov 25, 2022)
I think I'm ready to create a Ship class and remove SolidObject (or turn it into ship, whichever works. Let's do this!
(Nov 25, 2022)
I'd like to get my version of this thing closer to the state of Hill's, so that whatever changes he comes up with are easier to assess, and to learn from.
(Nov 24, 2022)
GeePaw Hill and I paired remotely for about three hours on the new 'Interactions' idea that I am borrowing from him. It went rather well, though differently than I had expected.
(Nov 23, 2022)
I feel that I understand something when I can do it, not when I can just use it. Let's try to learn Hill's latest idea.
(Nov 22, 2022)
I want to break all the Solid objects out into separate classes. Have not yet found a smooth way to do that.
(Nov 22, 2022)
An imaginary chat leads to a determination to push this design as far as it can go. Along the way I face an apparent fact.
(Nov 21, 2022)
In which our intrepid author expresses frustration and then gets down to making the program better.
(Nov 20, 2022)
Let's see if I can sort out the HyperspaceOperation a bit.
(Nov 20, 2022)
Fundamental theorem or not, implementation inheritance the tool of the devil or not, what we have is better than anything I can foresee. Full speed ahead! (Three false starts, then success.)
(Nov 19, 2022)
The Fundamental Theorem of Software Engineering is 'We can solve any problem by introducing an extra level of indirection'.
(Nov 18, 2022)
Hill has been learning the code with an eye to helping me understand why he is right and I am wrong. I fully support this and have some comments.
(Nov 17, 2022)
Having written up the theory of the game this morning, this afternoon I feel pretty certain that what's supposed to happen isn't really happening. We need to see what's to be done about it.
(Nov 17, 2022)
Implementation inheritance, or delegation? I've chosen the former in a fairly big way. Why? It seems that I'm evolving a sort of 'framework', and to make it do what I want, I think I need this inheritance. Some may disagree.
(Nov 16, 2022)
A change improves many objects. Summary follows.
(Nov 16, 2022)
Kent Beck has me thinking about cohesion and coupling. Let's look at the ShipMaker with that sensor turned on.
(Nov 15, 2022)
We replace ShipMonitor with ShipChecker and ShipMaker, about the same number of lines but far less intricate. A win.
(Nov 14, 2022)
Tidying. Why are we all setting asteroid velocity?
(Nov 14, 2022)
I'd like to push the new interaction scheme a bit further, returning something less basic than a Pair. A day to make the code a bit better.
(Nov 13, 2022)
Sometimes you just know you have a good idea. Sometimes you're even right. Is today one of those sometimes?
(Nov 12, 2022)
What if we run out of asteroids? What shall we do? Is a GameGod trying to be born? Sorry. Nope. Won't do that. Minor deities, that's one thing. One thing to rule them all? Nope.
(Nov 11, 2022)
I have dedicated the next portion of my life to implementing that cool hyperspace emergence rule. It means that I have to be able to count asteroids. So be it. But how? You'd think it'd be easy. It isn't.
(Nov 11, 2022)
Info from a viewer leads to a question. The answer leads me to a bigger question: Why didn't I think of that? THEN THIS ARTICLE GOES SIDEWAYS.
(Nov 10, 2022)
Let's do hyperspace ... and try to do it right.
(Nov 9, 2022)
My Zoom Buddies made an interesting observation. I choose to respond productively.
(Nov 8, 2022)
Things are a bit ragged here and there. Let's just trim them up a bit.
(Nov 8, 2022)
When things get bad in space, your ship has a hyperspace capability that will remove you from normal space and, after a delay, insert you back somewhere else. There is a chance that you'll not survive the attempt. Our mission today: implement this capability. There are issues.
(Nov 7, 2022)
Before a respawned ship appears, the game is supposed to check to be sure that it won't emerge colliding. How, in our distributed system, can we do that? At this writing, I do not know.
(Nov 6, 2022)
In Asteroids, after your ship dies, if you are allowed any more, a new one appears ... somewhere. Let's see how to make that happen.
(Nov 5, 2022)
No, not young people tweens. Tweens are little objects that do interpolation for us. I think we should have them. P.S. Dealt with that little lifetime issue.
(Nov 4, 2022)
It's 0500, way too early to be awake. I am awake. To keep the demons away, I think I'll see about narrowing the Flyer creation interface. As one does.
(Nov 3, 2022)
Hill tweeted something. Perhaps it had been mentioned at the Zoom Ensemble but if it was I missed it. It seems like a good idea. Spoiler: It was!
(Nov 3, 2022)
Options abound. further cleanup of Flyer seems prudent. But it might be fun to do the Splat. So many choices. Splat wins.
(Nov 2, 2022)
Looking at Flyer collisions, I wonder how it would look if it didn't look like it does. P.S. Two more little refactorings. Free of charge!
(Nov 2, 2022)
I think something needs to be done about the growing mess in the flyers. Let's take a look and see what we see. I'm trying to honor GeePaw's concerns ... and yet ... and yet, I go a different way than I anticipated, with better results.
(Nov 1, 2022)
It's about time ... to work on time. I think the code is telling me something, but I'm not sure just what it is. Shadows in the mist.
(Oct 31, 2022)
I have in mind some learning to do about Interfaces, and possibly abstract classes. I want to work on scoring, and I have in mind a way to do it with a flyer. Spoiler: He shoots! He scores!!
(Oct 29, 2022)
We have an interesting architecture going here, unlike any I've used in these games before. Let's see if it can go all the way.
(Oct 28, 2022)
What shall we do today, Brain? Let's see if we can get this baby under some semblance of control. Spoiler: It's ALIVE!!!
(Oct 27, 2022)
I believe I learned enough yesterday to make a good job of the ShipMonitor today. One question is whether to start over, or move forward. I make the right decision, of course.
(Oct 26, 2022)
I have what seemed, in the early morning hours, to be a good idea. Is it? Let's find out. ARRGH: What we may have found out it that it's too cute to live. HOWEVER: There may be a clean way out.
(Oct 25, 2022)
Let's get the display loop running on a Game instead of a couple of ships. Then I'll see if I can figure out the keyboard connection. Probably.
(Oct 24, 2022)
OK, I've seen it move. Should I plug in drawing for each element? Or test controls?
(Oct 23, 2022)
Creeping up on actually having to display some objects. Maybe I should just do it today?
(Oct 22, 2022)
We're like ten articles in on a video game with no video. This is rather interesting. I'll try to explain why.
(Oct 20, 2022)
I may not get much coding in today, but I have some ideas and will set them down in the few minutes before I have to head out.
(Oct 19, 2022)
The Zoom team 'might have done differently' but agree that current code isn't signalling very strongly how it wants to be. I guess today I have to add more of a mess.
(Oct 18, 2022)
This morning I'm wondering whether I made a mistake yesterday. Well, I must have made some mistake, but I have a particular possibility in mind.
(Oct 17, 2022)
It's lonely in outer space. We need some other stuff up here.
(Oct 17, 2022)
Space objects, as everyone knows, have a maximum speed limit. This morning, I plan to implement it.
(Oct 17, 2022)
Space objects, as everyone knows, have a maximum speed limit. This morning, I plan to implement it.
(Oct 16, 2022)
I seem to be zeroing in on an asteroids kind of game in this exercise. That's probably good, because I've done asteroids at least once before.
(Oct 15, 2022)
I managed to make a test work in the Ship project (its new name). Let's see what we can predict about a game design.
(Oct 15, 2022)
A growing list of questions, and hopefully answers, as I learn about Kotlin, IDEA, OPENRNDR, and all that jazz.
(Oct 14, 2022)
I want to play further with OPENRNDR. I've skimmed the docs. I'm impressed, and probably dangerous.
(Oct 13, 2022)
Yesterday, the OPENRNDR starting project ran on my machine. Today, before studying the system, let's take a look at the code and tweak it a bit.
(Oct 12, 2022)
This morning, I'm going to try to get OPENRNDR running with Kotlin on my machine. I've seen it done on a Mac and on a Windows machine. What could go wrong?
(Oct 11, 2022)
Let's see if we can figure out a clean way to accomplish yesterday's accomplishment.
kotlin ]
(Oct 10, 2022)
I think I'll do a bit more on darkness. With some TDD, of course.
kotlin ]
(Oct 10, 2022)
First, some thoughts on TDD.
(Oct 9, 2022)
Two stories loom before me: some kind of a magic bridge, and darkness. One of these is easy.
kotlin ]
(Oct 8, 2022)
A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.
(Oct 8, 2022)
I have in mind recreating, or ripping off, some special rooms from the old adventure. Ideally, I'll be able to build these with no new features. Whether we have all that we need, I'm not sure. We'll find out.
kotlin ]
(Oct 7, 2022)
In honor of the occasion, I think I'll sum up my current thoughts, feelings, notions, regarding Kotlin, IntelliJ IDEA, and all that jazz. I admire good work. These are good.
kotlin ]
(Oct 6, 2022)
Why am I putting so much wonderful capability into a game-making system that will never be used to make a game people will actually play? To tell the truth, I kinda lost track ...
kotlin ]
(Oct 6, 2022)
Sometimes something really simple is not obvious. This may be a case for pair and mob and ensemble programming.
kotlin ]
(Oct 5, 2022)
A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.
(Oct 5, 2022)
Further thoughts on the past few days' transformation, followed by looking for similar opportunities.
kotlin ]
(Oct 4, 2022)
Can we remove the duplication of the action methods from World and Room? Let's try.
kotlin ]
(Oct 4, 2022)
More world-building.I'll try to devise some affordances.
kotlin ]
(Oct 3, 2022)
A bit of world building. Will it point up any notable needs? Oh, yeah!
kotlin ]
(Oct 3, 2022)
What shall we do today, Brain? Same as every day, Pinky, try to create a world.
kotlin ]
(Oct 2, 2022)
It's 0420 and I have an idea. I figure never pass up an idea, so here I am at the keyboard.
kotlin ]
(Oct 1, 2022)
I think the Covid jab hit me this time. Just a short article. Anyway, it's Saturday, what do you expect? (We do stumble on a nice result.)
kotlin ]
(Sep 30, 2022)
Typing 'go blue' instead of something like 'go east' results in a runtime exception. I take exception to that. Let's fix it.
kotlin ]
(Sep 30, 2022)
Converting the enums to Kotlin's preferred rules. Published for the record, whatever that means. Probably means, scan or don't read at all. Nothing to see here, move on ...
kotlin ]
(Sep 29, 2022)
Just a bit more play with the Direction and Room enumerations and related code. Should I work out why 'e' doesn't work, or just make it impossible?
kotlin ]
(Sep 29, 2022)
I don't know quite what we'll do this morning. Something fun. Let's start by talking about good times.
kotlin ]
(Sep 28, 2022)
Often tiny changes can have very desirable effects. When that happens, it may be a sign that things are in decent shape.
kotlin ]
(Sep 28, 2022)
Feeling rather done with Gilded Rose, I take another look at the text game building code. There are issues.
kotlin ]
(Sep 27, 2022)
A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.
(Sep 27, 2022)
It seems to your faithful author that we've done nearly all we can with the Gilded Rose. We'll take a final look. Or maybe not final. Who knows?
(Sep 26, 2022)
I want to try another approach to the product-type lookup. I have to try it to see if I like it.
(Sep 26, 2022)
We'd like a better way of getting from an items name to its type. We'd like it to be bullet-proof, but not difficult to manage.
(Sep 26, 2022)
A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.
(Sep 25, 2022)
I was glancing at yesterday's article last night, and noticed some truly odd code that IDEA generated for me. We'll start there, and I have some improvements in mind.
(Sep 25, 2022)
I'm going to start keeping track of the 'resolutions' I make as I program. I'm sure some of these are generally applicable but I'm working in Kotlin as I start this list.
(Sep 24, 2022)
We are supposed to implement a new feature in the Gilded Rose program. Let's do that ... and let's take a look at where we are ... and where we might go. (Final: We go somewhere rather nice!)
(Sep 23, 2022)
The point of a kata is that we do it again and again, practicing to get better. This isn't really a kata, but it's somewhat like one. (Outcome: Two points to GeePaw.) (UPDATE: Not a bug! Woot!)
(Sep 23, 2022)
I do some microtests. Didn't even take an hour, including writing.
(Sep 22, 2022)
Let's see if we can wring a bit more out of refactoring the Gilded Rose. (Some wiggling back and forth to slightly better code.)
(Sep 22, 2022)
Continuing the long refactoring from the previous article.
(Sep 21, 2022)
One course seems obviously better. I shall choose the other.
(Sep 21, 2022)
Articles 76 and 77 are a long, tiny-step refactoring. Here, we'll preview where we started and where we wind up.
(Sep 21, 2022)
Yesterday the FGNO / Zoom Ensemble played with the Gilded Rose. This morning we'll look at it here.
(Sep 20, 2022)
Mostly I plan to solve the water problem this morning. But I'm wondering about concision. When is enough too much?
kotlin ]
(Sep 19, 2022)
Two small changes for your amusement. UPDATE: No, three! Thanks Christian!
kotlin ]
(Sep 19, 2022)
Wrapping collections keeps the tricky stuff inside and offers nice clean easy stuff on the outside. That's why we do it, right there.
kotlin ]
(Sep 18, 2022)
This morning I plan to encapsulate my map of Item instances, and show why I think it's a good idea. In addition, I'll clarify what I mean by 'always' and 'never'.
kotlin ]
(Sep 17, 2022)
Let's keep banging away at the new Item. We'll make them a bit smarter.
kotlin ]
(Sep 17, 2022)
Yesterday's work on using the DSL turned up some issues. None of them surprise me—but that doesn't mean I know how to deal with them. Or ... do I? (And: I seem to be feeling whimsical.)
kotlin ]
(Sep 16, 2022)
Let's do some world-building, with tests. OK, I admit it: no tests yet. Barely made it work.
kotlin ]
(Sep 16, 2022)
Let's fix one of those 'lateinit' variables. They're definitely a code smell.
kotlin ]
(Sep 16, 2022)
Some things seem to me to be happening at the wrong time. One issue is the GameResponse. Another is in building the world. What ever shall I do? (I 'discover' TODO.)
kotlin ]
(Sep 15, 2022)
There's not really much left to do here, if my purpose is to build a DSL for Zork-like games. That's a big problem. Today: A nice refactoring in tiny steps.
kotlin ]
(Sep 15, 2022)
Some tidying, but I do need to find a smooth way to do it.
kotlin ]
(Sep 14, 2022)
A quick test of a simple idea seems good. I am pleased.
kotlin ]
(Sep 14, 2022)
Let's make some progress toward Room actions. Some fairly nice refactoring and feature addition in here. Includes: praise for IDEA and Kotlin.
kotlin ]
(Sep 13, 2022)
Let's see if we can untangle things a bit in and around Imperative, Phrase, and the like.
kotlin ]
(Sep 12, 2022)
Back to the Phrase-matching find. I'll grow it incrementally this time ... and it works! Life is good.
kotlin ]
(Sep 12, 2022)
OK, with that off my chest, we can do some code. Let's keep after Actions and the associated items. Things do not go as I expect.
kotlin ]
(Sep 12, 2022)
Some Twitter chatter and a moment of not knowing what I wanted to code this morning has led me to think about what people should do.
(Sep 11, 2022)
I think this morning's thinking was good enough to deserve a chance. Could my thinking be wrong? It has happened before.
kotlin ]
(Sep 11, 2022)
In which, our intrepid hero realizes that while thinking is good, clear thinking is better than muddy thinking.
kotlin ]
(Sep 10, 2022)
A really nifty idea collapses. Yet, I ain't bovvered! Come read and find out why.
kotlin ]
(Sep 9, 2022)
Let's do a bit more on the SmartMap, and then try to get it in play. (Spoiler: It works nicely! I am pleased.
kotlin ]
(Sep 8, 2022)
I have what I think is a very nice idea. Let's talk about it and then start working toward it. Is this BUFD?
kotlin ]
(Sep 7, 2022)
Now I'll try adding something to my actions collection, first in regular code, then tomorrow I'll try to add the capability to the DSL.
kotlin ]
(Sep 7, 2022)
Let's look at the Actions in the new Imperative. Advice from my betters suggests I could do, well, better.
kotlin ]
(Sep 7, 2022)
Report and confession on last night and some behind the scenes grunt work.
kotlin ]
(Sep 6, 2022)
Let's make the Actions in the Lexicon do their job. There are some issues ... do we resolve them? We do and it's great! A big lesson is relearned.
kotlin ]
(Sep 4, 2022)
This time around, I'll plug the Imperative into the game, or know the reason why I couldn't. I'm hoping for the former. (Spoiler: works!)
kotlin ]
(Sep 4, 2022)
Let's find more small steps toward replacing the old Command idea with Imperative. I have in mind providing a Lexicon in the existing structure.
kotlin ]
(Sep 3, 2022)
I want to move the testing bits for Imperative back down to the test branch, segment, section, whatever it's called. IDEA impresses me.
kotlin ]
(Sep 3, 2022)
Let's put this in context. No, I'm not explaining. We're going to put all this into Context. Includes Shiny Squirrel pattern.
kotlin ]
(Sep 3, 2022)
This morning, I want to try a different way of mating the new Imperative to the existing scheme. First, I'll have to figure out what that scheme is, and whether there's anything in it to like. I suspect there is.
kotlin ]
(Sep 2, 2022)
Let's see about converting the `when` to a table. Sounds easy enough.
kotlin ]
(Sep 2, 2022)
A bit more work with the new Imperative. In reviewing the code, I'm not sure what else it needs to do the job. After a bit of testing and enhancing the tables, I'll think about whether and how to use it.
kotlin ]
(Sep 1, 2022)
This morning I plan to share some early thoughts and perhaps turn them into code. (To enjoy this article, please set your expectations to 'I wonder how Ron might go from a vague dreamy idea to something that might actually be useful'.)
kotlin ]
(Aug 31, 2022)
I think I'll experiment a bit with a Command object and its context. I'm not sure where this will lead. Perhaps to the bit bucket.
kotlin ]
(Aug 31, 2022)
Some interesting insights from last night's Zoom inspire me to morph my design. A lot of thinking, a little coding. A decent direction, I think.
kotlin ]
(Aug 30, 2022)
A fix for the warnings, but do I like it?
kotlin ]
(Aug 30, 2022)
Today's plan: plug in the new parser. We'll need to refine it just a bit, but I'd like to get it in play this morning. Best laid plans ...
kotlin ]
(Aug 29, 2022)
Let's see about cleaning up that `expand` method.
kotlin ]
(Aug 29, 2022)
It's 0525. I want to begin to try something before actually starting my day. This may go somewhere interesting, or crumble to sand in my hands. (Spoiler: I think it went rather well.)
kotlin ]
(Aug 28, 2022)
Refactoring in the direction of what we think we might prefer. Beck said: Make the change easy, then make the easy change.
kotlin ]
(Aug 28, 2022)
I get good advice from my betters. In the face of that, I forge ahead.
kotlin ]
(Aug 27, 2022)
Let's do some very simple parsing.
kotlin ]
(Aug 27, 2022)
A little refinement, and then let's press forward on Picov Andropov objects.
kotlin ]
(Aug 26, 2022)
At a more civilized hour, I have an improvement in mind. And it's really time to start doing something about inventory. And, curiously enough, I am rather successful.
kotlin ]
(Aug 26, 2022)
It's 0415 and I'm awake, with what seems to be a good idea. Is it a good idea to program at 0415? That remains to be seen.
kotlin ]
(Aug 25, 2022)
Let's push the Spike in a little deeper. I've got some ideas for how it could be quite nice. Good ideas? We'll find out.
kotlin ]
(Aug 25, 2022)
Yesterday, in an astounding flurry, I made a magic word open a lock. I also made a bit of a mess, which is partly good but probably mostly bad. Today, I set out to improve the code—and the feature. (As usual, that's not what happens.)
kotlin ]
(Aug 24, 2022)
I want to set up a test world where you have to say a magic word to open a door, or something like that.
kotlin ]
(Aug 24, 2022)
When we make two changes at once, there are four possible outcomes, and three of them are bad!
(Aug 24, 2022)
Still working toward the View displaying our new 'say' text. Might make it this morning.
kotlin ]
(Aug 23, 2022)
I think the next thing I need is for a message to come out in response to a command. We need an extension to GameResponse. (For once, reverting would have been the wrong thing to do ... probably.)
kotlin ]
(Aug 23, 2022)
I have some design thinking to report, but my hope for today is to have an operating grate somewhere in the world. I manage a good first small step.
kotlin ]
(Aug 22, 2022)
I need smaller steps. The Game sends the command to the current rRoom. But the World knows the rooms, and neither the Game nor the Room do. Let's try passing the World to the Room.
kotlin ]
(Aug 22, 2022)
In order to find out what our DSL should be like, I propose to code up a few scenarios 'by hand'. I make some progress but not as much as I'd hoped for. Lost thread. Reverted. Good man!
kotlin ]
(Aug 21, 2022)
Now that the game can be played, more or less, it's time to think of some scenarios that we need our DSL to support.
kotlin ]
(Aug 20, 2022)
Inching forward. Pretty sure I can make a TextField work. Final Result: The Game is Playable!
kotlin ]
(Aug 20, 2022)
There must be text things in JavaFX/TornadoFX. Everyone has them. How hard can it be? Wow, I hate being ignorant. But I love learning!
kotlin ]
(Aug 19, 2022)
How bad is it when you actually EXPECT your own article to be boring? I'll do my best to say something interesting. Includes a very long sentence and a small but important win.
kotlin ]
(Aug 18, 2022)
Time for a little planning, and some worrying. How far can I go before making this thing somehow playable? How far should I go? Bonus: A devil duckling!
kotlin ]
(Aug 17, 2022)
I wonder what we can do about output without actually having a way to play the game ...
kotlin ]
(Aug 17, 2022)
I'm psyched after two consecutive sessions with some success and no big troubles. What could possibly go wrong?
kotlin ]
(Aug 16, 2022)
How about a bit of code improvement? That might be fun.
kotlin ]
(Aug 16, 2022)
Let's parse a bit more of the DSL (Dungeon Scripting Language?) and then see what happens. I have high hopes, tempered by decades of experience.
kotlin ]
(Aug 15, 2022)
Let's try something specific with the DSL builder idea. I have in mind a text game like ADVENTure or ZORK.
kotlin ]
(Aug 13, 2022)
In which your intrepid author suddenly realizes something, and decides to do something he rarely does.
kotlin ]
(Aug 11, 2022)
I want to understand DSLs and builders. First, I have to figure out how to make a new project with tests in it. I anticipate an onset of grumpiness as I learn new things.
kotlin ]
(Aug 10, 2022)
OK, I'm feeling like working on acceleration.
kotlin ]
(Aug 10, 2022)
I have tidying to do, and some stories to implement. At this writing (0815), no actual plan.
kotlin ]
(Aug 9, 2022)
So few lines, so many design questions. We'll work more on Ship motion. (I manage some whimsy. Must be getting more comfortable with IDEA/Kotlin.) P.S. Learned a thing.
kotlin ]
(Aug 8, 2022)
OK, let's see if we can code up an operator in this baby. Overall Result: Much more comfort.
kotlin ]
(Aug 8, 2022)
Let's plug away, learning IDEA, Kotlin, and whatever, while also seeing how much TDD we can do on an essentially graphics-oriented game.
kotlin ]
(Aug 7, 2022)
First some grumbling, then an idea for something useful that I've not done before.
kotlin ]
(Aug 5, 2022)
I'm inching forward in my learning of Kotlin and TornadoFX. Progress is happening, but so slowly that I can't write as I usually do.
kotlin ]
(Aug 3, 2022)
We've all agreed to fork the repo. I'm on my own, more or less, and already confused even though I haven't even started.
kotlin ]
(Aug 2, 2022)
After more than a little hassle, my colleagues and I have a Kotlin shell that we can pass around. Today, for fun, I'm going to try to write some tests and code.
(Jul 28, 2022)
Perhaps the biggest mistake in XP and Agile ...
(Jul 26, 2022)
There is a sticky note on my desk needing attention. Let's attend to it. I have a small concern. Also: smaller steps pay off.
(Jul 25, 2022)
Usage changes. Language is usage. Language changes, not necessarily for the better, in my opinion.
(Jul 24, 2022)
I wonder why I'm doing what I'm doing. Meanwhile, requirements changes to the robot's radar result in some design issues.
(Jul 23, 2022)
I've decided to deviate from the spec to make my work with this example more interesting (to me). I anticipate no real difficulty with this extensive set of changes.
(Jul 22, 2022)
Today I have to find a way to do it right ... and light. How little can I do while still improving the code?
(Jul 21, 2022)
I think we need to improve the map display a bit. We'll spike, and that's going to prove a point that I made yesterday, I hope. Or disprove, in which case we can laugh at me hahaha.
(Jul 20, 2022)
My Customer (me) wants the radar screen rotated to forward = up. The developers (me) are happy to oblige. P.S. Came back later for the thrilling conclusion.
(Jul 19, 2022)
Maybe we need a bit of console display. And I'm sure we'll find some code to improve. Foraging, basically.
(Jul 18, 2022)
Let's not allow movement into obstacles, and maybe penalize moving into pits.
(Jul 18, 2022)
I found a little something. And some other somethings.
(Jul 18, 2022)
I have an idea for something that might be better. But that's not my reason for being here. (And should all ojbects be written for their own convenience? Yes, and ...)
(Jul 17, 2022)
Let's slide in the remaining callbacks, and see what else we can see before brekkers.
(Jul 16, 2022)
My Inner Eddie says we may be in big trouble. Let's find out. ClickBait: Absurd claim at the end.
(Jul 14, 2022)
In which our intrepid author takes on important notions while scarcely mentioning the actual topic at all, hoping to enlighten himself while offending no one. Tall order.
(Jul 12, 2022)
Oddly, I take as today's writing prompt, a strange tweet from a person of curious name.
(Jul 11, 2022)
Let's see if we can get the new connection object to run as if it were on a thread, even though we don't have threads. That should be amusing.
(Jul 10, 2022)
More on TCP/IP. A realization that might have come sooner, but today's OK too.
(Jul 9, 2022)
I've been trying for days to get a decent TCP/IP socket connection working on the iPad, apparently for my sins. So far, I've failed miserably. Today, Saturday, another try.
(Jul 5, 2022)
More on server code. I have an idea. Should I try it? Answer: no.
(Jul 4, 2022)
I think we have only one hard problem remaining. Let's see what we can do about that. MORAL: Don't be like Ron's brother's brother.
(Jul 3, 2022)
Well, I don't know. A bit more on motion. Maybe a start on scan/look? Oh and a better look for the robot?
(Jul 2, 2022)
Let's turn around and go backward, and see whether we begin to see some improvements to how we do these things. RELEARNING: I need smaller steps.
(Jul 1, 2022)
More on Request-Response. Maybe some little objects?
(Jun 30, 2022)
Moving toward standard request-response. Seems about time. But Never would be better. ALSO: A very brief introduction to industry standards of completeness.
(Jun 29, 2022)
I've made a mistake. Or I'm about to make one. Or both. Certainly not neither.
(Jun 28, 2022)
Today we work further toward accommodating the 'spec'. I think we'll focus on the robot status. I think I may rediscover why something is a good idea.
(Jun 27, 2022)
We need to make the robot-world communication a bit more like the spec, and a bit more like client-server. Then we can make more progress. ERRATUM Near the end.
(Jun 26, 2022)
More on the JSON connection. I think I see something symmetric, if not actually easy.
(Jun 25, 2022)
The spec requires us to communicate using JSON. It's time to get started with that. As I type this I wonder something ...
(Jun 24, 2022)
TCP. I think I know what I did wrong yesterday. If I can make this work, it'll help me TDD the server's main loop. Bonus: Kitty!
(Jun 23, 2022)
Let's try more than one connection. Do I need coroutines? Let's try without. LEARNING: I seem not to be able to have multiple connections within this one program.
(Jun 23, 2022)
I'm spiking TCP. Not writing the article as I go. Instead, I'll record bits of progress and what I may have learned.
(Jun 22, 2022)
Something in last night's Friday Coding Zoom struck me. I need to think about this and try it.
(Jun 21, 2022)
OK, sockets. At least for a little while. And a conversation with myself. No, I'm OK, really. And thanks to Dave1707.
(Jun 20, 2022)
Let's start by talking about design. Software design. I definitely don't know anything about any other kinds. Interesting thoughts interwoven with vague mumblings.
(Jun 19, 2022)
Let's review some code.
(Jun 18, 2022)
Try again. Fail again. Fail better. Been down so long, it looks like up to me. Summary: Much better.
(Jun 17, 2022)
Let's see about helping the robot understand the new 'look' tables. I feel sure that I'm going to want an object up in this thing. The outcome may surprise you.
(Jun 17, 2022)
Today's demo day. We're good to go, but I think we can do better. Anyway, gotta do somethin'. Anti-Spoiler: I decide not to spoil the code for the sake of maybe a feature.
(Jun 16, 2022)
Rotation Matrices? Why not, might be better. Let's spike. Warning, this is gonna get a tiny bit mathematical.
(Jun 16, 2022)
Awakened by a strong rainstorm, I decided to get up and watch it. I'll code a bit while I do. I'll try to think before, during, and after coding.
(Jun 15, 2022)
So many good ideas. But we need to ship it. We'll talk about that—and get ready to do it! UPDATE: Walking skeleton works!
(Jun 14, 2022)
I think we're ready to draw something. How can we make the drawing more testable? I have a p-baked idea, for small p.
(Jun 13, 2022)
First we do a Lens. Then an amazingly smooth, very long, step by step refactoring. I'm proud of this one!
(Jun 12, 2022)
I have a bit more time and an urge to do some code improvement. Let's see what we can do to make all this a bit easier.
(Jun 12, 2022)
A bit of musing about the world, a bit of planning, a bit of coding. It's Sunday, so this will probably be short.
(Jun 11, 2022)
Working toward a 'walking skeleton'. I think I know what I'd like it to be.
(Jun 10, 2022)
What do skeletons have to do with robots? Could there be more than one skeleton?
(Jun 9, 2022)
Day 2. I did watch a couple of GeePaw's videos. Good news. Thinking ensues. Concerned about Knowledge.
(Jun 8, 2022)
Tuesday night's Friday Night Coding Zoom has hooked me. This is the beginning of the result of that hook.
(Jun 6, 2022)
Completing a refactoring makes a feature easier. Unless I'm wrong, but I'm not.
(Jun 5, 2022)
Apparently not Done-geon. Those missing tests for that trivial code bug me. There's something to learn in here. LATER: A very nice outcome!
(Jun 4, 2022)
Unable to do nothing, I made a 'simple' change to the Dungeon program. It works ... and I don't like it. Later: Sometimes doing the right thing doesn't work out.
(Jun 3, 2022)
Some thoughts after another pleasant conversation with Colin Hammond of ScopeMaster.
(Jun 2, 2022)
If in fact I'm done, for a while at least, with the dungeon program, what shall I do and write about. Your input welcome.
(Jun 1, 2022)
Countdown to ... what, exactly? Let's check the yellow sticky notes. Time for a break from Dungeon?
(May 31, 2022)
Let's clean up those free-hanging functions just for fun. It'll make things just a bit better.
(May 31, 2022)
I think that today I might get all the Decor specified for all the dungeon layers that are supported. That's an estimate, and I could be wrong. (Spoiler:not wrong, and some nifty refactoring.)
(May 30, 2022)
Let's work again, on controlling the dungeon layout. My objective this morning is to define at least one level's Decor. I'm extending the story based on feedback.
(May 29, 2022)
No promises, just a look at Tile and its friends.
(May 28, 2022)
This one's gonna be rambling. A design idea keeps coming back to me. I feel that the program would be much better, if ...
(May 27, 2022)
I was asked what I tell people to do that I don't do myself. The answer may surprise you.
(May 26, 2022)
Up-front Design? In Agile? Sure, let's do some. I call it 'thinking'.
(May 25, 2022)
More on improving control over Dungeon creation. And a RAT. And a bear bite, kind of.
(May 24, 2022)
OK, with discussion of ease out of the way, let's get some ease up in this Decor.
(May 24, 2022)
We should have it. What should we do when we haven't?.
(May 23, 2022)
I start out to think about that clever trick and my plans for Decor. Then I change direction based on what I've learned. This has important implications for estimation, COSMIC or otherwise.
(May 22, 2022)
Let's work on the Spike aimed at creating DungeonObjects. Uh oh: Something too clever has been done here!
(May 21, 2022)
Still working on better control over creation of Dungeon Objects. I think I'll do a Decor factory method this morning. I can't think how to test it. The Internet helps me.
(May 20, 2022)
Estimation and a tiny bit of code. ScopeMaster took up my challenge.
(May 19, 2022)
Let's start on the Dungeon Object allocation story. I think we'll start in the middle, or near the bottom. So far, no takers from the pro-estimation folx. UPDATE: Hammond has done CFP for the story! Details tomorrow.
(May 18, 2022)
I don't like estimates in this world. Perhaps you do. If so, and you're so inclined, pick up this challenge. I'll tell you everything I know to help you.
(May 17, 2022)
This morning, I plan to write about COSMIC Function Points, Agile Practices, Civility, and Kindness. I can't wait to find out what I have to say.
(May 14, 2022)
Some thoughts on something GeePaw said. And I think we'd better complete the fixing of the publish situation. What is `the best we know how`?
(May 13, 2022)
Friday the 13th. That bodes well, always my lucky day. Besides, it was yesterday where I interfered with the canine. (Oh No! He did it again!)
(May 12, 2022)
Time to pick something to do. This always surprises me. Late update: THIS IS NOT GOOD. WE HAVE A MAJOR SHIPPED DEFECT!
(May 11, 2022)
Today I'm going to try to learn something. I wonder if I'll learn what I set out to learn, or something else.
(May 10, 2022)
Loose ends. Finding little things to do. Generalizing from few cases and many years. Delenda Chicago est.
(May 9, 2022)
A bit of thinking and doing with the `publish` feature. Small changes, much thinking.
(May 7, 2022)
'Nothing at all', the game says. What's up with that? And various musings.
(May 6, 2022)
Colin Chapman of Lotus said that to add speed, you must 'add lightness'. Can we add some simplicity up in this dungeon?
(May 5, 2022)
Let's apply some of the ideas from D3 in the curreent Dungeon program. We'll see whether they're a step toward a better design.
(May 4, 2022)
I'm wondering whether I need the complex publishing approach that I'm using in the Queue. Only one way to find out: reasoning fails me. (As always, I wind up somewhere else.)
(May 3, 2022)
More work on the new event-driven scheme. I hope to get to an interesting problem today.
(May 2, 2022)
What have I learned in this Dungeon Crawl? What would I do differently? I've decided to find out.
(Apr 30, 2022)
Yesterday, testing something required my code to be a bit less smooth than I'd have liked. Today I have an idea that I think is going to be quite fine. It's not even too clever.
(Apr 29, 2022)
We need to talk. We need to code, as well. And we need to test. A nice result, a better commitment.
(Apr 28, 2022)
Let's check our stories along the way to better control over the trash, er, treasures in the Dungeon.
(Apr 27, 2022)
Let's do some messages.
(Apr 27, 2022)
What do we do when we find two classes that are rather similar? We make them more similar, of course! (That''s not what happens.)
(Apr 26, 2022)
More work on improving the ability to place Dungeon Objects. Today I want to look at Decor and Loot. What will really happen? I never know until I get into the code.
(Apr 25, 2022)
I saw an interesting contagion-related graph on Twitter and decided to do something like it.
(Apr 25, 2022)
Another run at the current Big Story. Need to find something that will lead me away from confusion rather than into it. Might have to think. Might even have to draw a picture.
(Apr 23, 2022)
More on providing control over placing things in the Dungeon. I'm thinking about changing my mind, but I might change my mind about that. (Spoiler:Bear bites man.)
(Apr 22, 2022)
We're still prepping for the story about better control over what goes into the Dungeon. Some things remain that I'd like to clear up. And a small story!
(Apr 20, 2022)
The FNCS has spoken regarding the defect. I do some smoothing. Multi-signature method? Possibly. I ain't bovvered.
(Apr 19, 2022)
I have shipped a defect, and a serious one. What happened? How could I have avoided it?
(Apr 18, 2022)
Planning Meeting. I'm not sure what to do today, but have some ideas.
(Apr 17, 2022)
Pushing the object further down. What does he mean by that?
(Apr 15, 2022)
Let's look at some of the 'story' cards I've saved up and see what we might work on.
(Apr 14, 2022)
Just a bit more tidying, as Kent Beck puts it. Soon, new features or something. But today is not that day.
(Apr 13, 2022)
The experiment i did yesterday deserves a bit of commentary. Something to think about.
(Apr 12, 2022)
My plan for the day is to find a place to try out my clever idea, so that we can look at it in place and decide whether to allow it. Will it stay in?
(Apr 11, 2022)
A bit of Internet dispute about cleverness. When is code too clever to live? I have an example in mind.
(Apr 8, 2022)
A couple of working diagrams. Here's why I think rough diagrams are quite often good enough.
(Apr 7, 2022)
Drug-free, our intrepid author looks upon his works. Does he despair? (Spoiler, No, Mikey likes it!)
(Apr 6, 2022)
Today: Recovering from a couple of days on Nyquil. Is my brain operating?? We'll see.
(Apr 3, 2022)
Gonna refactor you a little bit more ...
(Apr 1, 2022)
I think we'll look at some of the methods that analyze the dungeon as part of building. I'm hoping for a good idea to pop up. TL;DR: Ron is out of kilter, copes, then stops before doing damage..
(Mar 31, 2022)
Back to tiny steps, if I possibly can. And you know what? I bet I can.
(Mar 30, 2022)
My side quest to move dungeon building out of Dungeon class continues. What monster shall I slay today? Let's find out. (Stress level too high. A clue.)
(Mar 29, 2022)
Continuing separation of building from running. Today, narrowing the scope of Tile. An idea for a better way of doing it. A good idea? I'm not sure.
(Mar 28, 2022)
Last time I had part of an idea. Today I have a larger fraction of the idea. Let's see if we can get all the way.
(Mar 26, 2022)
What are you trying to prove, Ron?
(Mar 25, 2022)
Pecking away to reshape things more to our liking. Small steps in roughly the right direction, that's the ticket.
(Mar 24, 2022)
Are we missing some layers in the Dungeon? The classes, not the places.
(Mar 23, 2022)
Reducing the span of concern for Tiles. Seem like a good idea. Will it be too difficult? Let's find out. (Spoiler: Almost, but not too difficult.)
(Mar 22, 2022)
Some tiny improvements ... or are they?
(Mar 18, 2022)
There's probably a bit more to do on isolating dungeon building from dungeon running, but the low-hanging tasty fruit has mostly been harvested. As for larger design improvements, I am at a loss. That may be a good thing.
(Mar 17, 2022)
Here, some thoughts raised by yesterday's Agile Alliance Zoom thing.
(Mar 14, 2022)
You'd think that software developers would realize that they are prone to error. Yet we are often more opinionated than we probably should be. Here's my opinion on that.
(Mar 12, 2022)
Plotter or Pantser? Which am I? Which are you?
(Mar 11, 2022)
Let's look at what we've done and see what might be next on our quest to separate building from running the Dungeon.
(Mar 10, 2022)
Let's do some more opportunistic refactoring toward DungeonBuilder. And I have a few thoughts to think about the direction I've taken.
(Mar 9, 2022)
Here are just a few of the unsolicited favorable comments I've received about 'The Nature of Software Development'. Some drawings included.
(Mar 8, 2022)
More gentle refactoring in the general direction of DungeonBuilder. No Monty Python reference intended.
(Mar 6, 2022)
Trying again. Last time was a disaster. I'll sum up.
(Mar 6, 2022)
Still trying to drift in a good direction. So far we've just barely improved, if at all.
(Mar 4, 2022)
Oh Hell, let's just do something in roughly the right direction.
(Mar 3, 2022)
Time to set a tentative direction and move that way. I am daunted before even starting. No code today.
(Mar 2, 2022)
I found myself wondering what I'd do with this program if I started over. I shouldn't do that. But what I could do ...
(Mar 1, 2022)
Today I plan to just look for some small opportunities to improve the code. I will be particularly looking for ways to use my fp primitives, and to improve them to make them more useful.
(Feb 28, 2022)
I'm disappointed, at least so far, that my 'functional programming' capability seems not to be helpful in the Dung[eon] program. But maybe there's still hope.
(Feb 27, 2022)
In which: Our intrepid author attempts to find some use for the FP library he has been toiling on for over four hours.
(Feb 26, 2022)
Today, for your delectation, I offer: the Library Trap! (Update: I looked at XSet2.)
(Feb 25, 2022)
Let's see if we can find a decent way to provide filter, map, reduce functions in Codea Lua.
(Feb 24, 2022)
Kent Beck is writing about 'tidying'. It's a whole patch of delicious strawberries, and I highly recommend them.
(Feb 24, 2022)
Yesterday's search for strawberries in the XST patch discovered problems. I want to at least double check what we did. TL;DR: It all works. Odd morning.
(Feb 23, 2022)
We're taught to 'make it work; make it right; make it fast'. We're taught that if it's hard to test, it's not right. Let's explore. TL;DR: No strawberry here?
(Feb 22, 2022)
Further thoughts on the river, the hill, and the nature of reality. I don't know why I wrote this. It's just here in today's part of the big integer.
(Feb 21, 2022)
A river flows rapidly down a hill.
(Feb 19, 2022)
Can we make our programming life immediately easier with this one simple trick? The answer may surprise you.
(Feb 16, 2022)
Some day--and that day may never come--it may fall to you to write the most important program of your life. Here's one man's example of how to do that.
(Feb 15, 2022)
One 'reason' why folx don't want to learn technical practices seems to be that they expect no benefit. Sometimes that's more about futility than actual benefit.
(Feb 12, 2022)
Some developers show little or no interest in learning practices that could make their lives better. I'd like to understand that.
(Feb 11, 2022)
I don't know whether this is good or bad, but it's an interesting trick.
(Feb 10, 2022)
Wandering off. Spinning down. Fading out. My projects here have a habit of that. What does that say about me, about you, and about our work? And krill? Really?
(Feb 9, 2022)
In my thinking about Strawberries, I'm wondering what issues folks have with Scrum, good or bad. Please tell me. I'll mention some ways here.
(Feb 8, 2022)
There are signs and portents. What are they telling us? Is this death--or is it perhaps a rebirth?
(Feb 3, 2022)
I'm taking a couple of on-line comments as writing prompts today. Let's see what we get.
(Feb 1, 2022)
Today I learned a new term. Maybe better/worse than 'Dark Scrum'. (TL;DR: If it isn't joyful, we're doing it wrong.)
(Jan 29, 2022)
Agile Software Development is about people working together. For that to happen, it helps to be kind, respectful, and helpful. Let's talk about that.
(Jan 28, 2022)
I'm pressing forward with the Lispy thing, but I have some concerns. I find it difficult to think about but I think I have an angle. (Spoiler: It's a wrap!)
(Jan 25, 2022)
TDD is too big a lump to be a good strawberry. Today I'm playing with TDD to try to find a bite-sized goodie. I expect not to accomplish that.
(Jan 24, 2022)
Technical Practices, Craft, Excellence, Improvement, Ease, Joy. What ARE you talking about??
(Jan 21, 2022)
A Twitter exchange yesterday and today has given me today's topic. I love it when not having a plan comes together. (Hm. Societal impact is similar ...)
(Jan 20, 2022)
Let's consider the implications of small-step development on our three shadow views of the program. (Includes Sarlacc.)
(Jan 19, 2022)
Yes, short feedback cycles are good. But is the trick of the trade 'small', rather than 'short'? The answer will not surprise you.
(Jan 18, 2022)
Working software is at the core of success with agile methods. Let's remind ourselves about that.
(Jan 17, 2022)
GeePaw Hill is workin on an idea. I urged him to publish his thoughts because I knew it would help him to make things concrete. Also I wanted to comment here.
(Jan 17, 2022)
I wasn't really planning to write about Sudoku again, but here we are.
(Jan 15, 2022)
I know what you're thinking: 'Is this four rules or only one?' Well, to tell you the truth, in all this excitement, I kind of lost track myself. You've got to ask yourself one question: 'Can I use this?' Well, can you?
(Jan 14, 2022)
We're here to replace raspberry jam with strawberry jam. We need those delicious nodules of flavor and value.
(Jan 13, 2022)
It's not the method. It's not the framework. It's your unique assemblage of innumerable small things that work together toward success. And some larger things: the people.
(Jan 12, 2022)
It's Wednesday. At last night's Friday Zoom Ensemble, we talked about Jam. I am inspired to put down some thoughts. Bottom line: On-line strawberry, not raspberry. (Updated, more links.
(Jan 11, 2022)
Just a bit more playing with the Lispy Calculator to while away a few minutes in the afternoon.
(Jan 11, 2022)
Thoughts and observations. Stuff and nonsense.
(Jan 10, 2022)
I'm going to push forward with this LISP / Scheme dialect. I'll begin by explaining why, and why not.
(Jan 9, 2022)
It's still the weekend, so I'm going to follow Peter Norvig's Python LISP Implementation a while and see where it takes me.
(Jan 8, 2022)
It's my weekend and I'll try if I want to. You could try too if it happened to you. Spoiler: This takes a very weird turn. Final line: Your move, Bill!
(Jan 7, 2022)
I guess there's nothing for it but to figure out how to rewrite, i.e. refactor, a set operation based on the existence of helper structures. But how? I have ideas but are any of them any good?
(Jan 6, 2022)
Bill Wake is trying to get me to think in terms of trees. I don't want to, but he does have some good ideas. Thanks, Bill!
(Jan 5, 2022)
Today I plan to experiment with creating some form of expressions that might be optimized. I expect to stumble a lot. Come along, point, and laugh.
(Jan 4, 2022)
No, not smiles and frowns. Algebra. At this moment I don't think much code will be done today. Feel cute, might delete later.
(Jan 3, 2022)
It's 6 AM and I have an idea. This could be very good or very bad.
(Jan 2, 2022)
I don't love the interface for adding functions into an XSet. And I want to add them 'one level in'. Will hilarity ensue? Probably not, but something will happen.
(Jan 1, 2022)
Some HNY thoughts, and more on the function as an element idea. Joy, philosophy, code. What's not to like?
(Dec 31, 2021)
I was thinking before I got up about median and mode. Then I had a truly marvelous idea.
(Dec 30, 2021)
I want Lua tables to be more useful as XSets. There's a hard way. But the current design also offers an easy way. (The answer will surprise you. It surprised me.)
(Dec 29, 2021)
I'm on a path to make ordinary tables behave like XSets. But first, I have to figure out how this thing actually works! Much musing, then some code.
(Dec 28, 2021)
I have in mind small things for today, starting with an interesting and confusing mistake left over from yesterday.
(Dec 27, 2021)
No, I'm not hearing voices. But the code does tell us things, just like any working material. We need to learn to listen. Today, we listen and the result is good.
(Dec 26, 2021)
A look at the code. Maybe a bit more on stats. P.S. I learn something and ditch almost all the code I wrote this morning.
(Dec 25, 2021)
It's Christmas, I'm waiting for the household to wake up, and I enjoy what I'm doing. Perfect holiday so far!
(Dec 24, 2021)
I didn't do the best possible thing in this morning's XST article. Here's what I think about that.
(Dec 24, 2021)
Today I plan to get grouping and summing working. Who knows, it might happen. If not, there's always tomorrow or my birthday.
(Dec 23, 2021)
Let's think about what the current drafts of summing and grouping tell us about our system. Then code (anyway).
(Dec 22, 2021)
Today, rather than make any deep progress, I plan to work on something I consider interesting, sums, averages, and grouping. I promise to publish this even if it explodes. (It doesn't, quite.)
(Dec 21, 2021)
Transformations, optimizations, and the relationship between OO and XST. Got some thinking to do. You get to watch, if you're tough enough. At least a tiny bit of code.
(Dec 20, 2021)
Step by step, inch by inch, slowly we turn long searches into more direct accesses.
(Dec 18, 2021)
I don't want to get stuck in a never-ending series of new setops: there won't be much learning there. Where's the beef?
(Dec 17, 2021)
I'm sure a lot of you have been saying 'Yes, but what about tuples?', or 'Why XST anyway?'. Today, we address those fascinating concerns.
(Dec 16, 2021)
Let's work on those new operations a bit.
(Dec 16, 2021)
Short morning today. I have a tentative plan for indexes. I'll scribble some sets. Might code.
(Dec 15, 2021)
Last night's Zoom Ensemble netted me a few ideas. I'll start exploring those today. Hilarity or perhaps something good will ensue. I can't wait to find out.
(Dec 14, 2021)
Further reading leads me to think about design, and design motivation. Castles in the air. Or underground. Good stuff happens.
(Dec 13, 2021)
In conversation with Bill Wake and with the Internet, I have an idea for something to try. And I'm just about ready to assess where we are and where we should go.
(Dec 12, 2021)
I'm not sure whether this will be useful, but Bill Wake gets the credit if it is.
(Dec 11, 2021)
Bill Wake was trying to hammer an idea into my head. I must think about that. And I have a small idea of my own.
(Dec 10, 2021)
Time to work on the actual restrict operator for CSV, since the pattern-maker experiment was a success.
(Dec 9, 2021)
There's no way around it, I've got to work on the fast restrict today. Might not finish. We'll see.
(Dec 8, 2021)
Getting started with CSV data. And reporting a conversation.
(Dec 7, 2021)
Reflection leads me to focus a bit more on set operations, and less on internal methods. Does this call for a new layer? Also: real technical debt! Updated with idea from Carl Manaster!
(Dec 6, 2021)
I'm going to try to create pipelines using coroutines. I think they may make for a more expressive interface. I turn out to be partially right.
(Dec 6, 2021)
How do you design a thing like this, Brain? Same as everything else? Or not?
(Dec 5, 2021)
I was puzzling over an issue with 'union' and gained an insight that either I've never had, or that I had lost. Whee!
(Dec 3, 2021)
I found the easy way to build an iterator in Lua, so we'll do that and see whether it improves the code as much as I think it will.
(Dec 2, 2021)
I think I'm going to start on restrict today. There are some issues around atoms.
(Dec 1, 2021)
Last night I understood how to do something with XST that I've not in the past been able to do. So let's talk about why XST is interesting and what one might do with it.
(Nov 30, 2021)
I have a random idea about the data structure for sets, so thought I'd give it a try.
(Nov 30, 2021)
Save me, I'm thinking about Extended Set Theory again.
(Nov 28, 2021)
I have a mad scheme for making an object move using applyForce and momentum. (Arrgh, results suggest that we need to file a bug report.)
(Nov 27, 2021)
An experiment by Dave1707 inspires Ron to figure out what's really going on with applyForce. Will he succeed? The answer may not surprise you.
(Nov 26, 2021)
Ooo, an accidental play on words. We're going to change our cube's direction, but also the direction of these articles.
(Nov 25, 2021)
On this day of thanks, I'm moved to think about all the -isms that seem to plague us, and how to deal with them.
Social ]
(Nov 24, 2021)
We've learned how to move things using code. It turns out that Codea can handle moving them for us, for fun and profit.
(Nov 23, 2021)
I think we need to learn about Craft physics so that we can tutorialize something about it. This turns out to be a bit of fun.
(Nov 21, 2021)
Here's how you really do that. An improved design for our entities.
(Nov 20, 2021)
A couple of new entities lead to a design concern.
(Nov 19, 2021)
In this tutorial, we'll make our cube move around the 3D volume a bit, then improve how it looks. And we'll improve how we look at it.
(Nov 18, 2021)
Converging on a plan, I decide to do a series of tutorials. Herein, an explanation of what I mean and intend, and the first one.
(Nov 16, 2021)
I'm setting out to learn, again, about Codea's 'Craft' capability, its 3D voxel-based facilities. Today, I'll talk about my reasons, ambitions, and look at some code.
(Nov 12, 2021)
Just because I think I should do SOMETHING, I think I'll improve how CodeaUnit displays results on the screen.
(Nov 10, 2021)
I'm going to try to build a 'fluid interface' feature for Codea's graphical style capability. Why? I don't know.
(Nov 9, 2021)
Let's improve CodeaUnit a bit. But first, what's the deal with iOS shortcuts? An odd report on an odd morning.
(Nov 8, 2021)
Driven by some Slack chatter, I've been thinking about feedback. How does that fit into life, and into this little program?
(Nov 4, 2021)
Some refactoring, and some thoughts on a Twitter thread. And an odd surprise: the code says No.
(Nov 3, 2021)
Rules, rules. TDD rules, Beck Rules, OK. And a cat.
(Nov 2, 2021)
I'm just not up for going back into the Dung mines. Gonna put plain function detection into the stats instead. Also, random subtweeting. Also bear bites man.
(Nov 1, 2021)
At last, I get to apply Dave's scrolling thing. It's simple, and obvious, and I never thought of it. And a couple of stories of a great programmer.
(Oct 31, 2021)
This morning, I plan to add detailed method reporting to the full report. I am expecting no real trouble but have recognized a mismatch.
(Oct 30, 2021)
Let's get some output up in this baby. I plan to steal two good ideas while I do this.
(Oct 28, 2021)
I wonder what we could do about comments. They're tricky.
(Oct 27, 2021)
"If this is his idea of fun, he must be a laugh riot at parties." -- A Reader
(Oct 25, 2021)
Backward? Or forward? Which was it?
(Oct 24, 2021)
We continue working on our little 'Making App', because it's kind of fun. Today, I foresee a 'major refactoring'.
(Oct 23, 2021)
Let's do methods, and try to drive out some objects.
(Oct 21, 2021)
In the interest of variety, let's do some work for the makers here. Let's see how we can collect some interesting statistics from Codea programs.
(Oct 20, 2021)
One small improvement. Then I want to consider the bigger picture: if I were starting over, how would I do this program differently?
(Oct 19, 2021)
Late start today. Not sure what to do. Try the hex map again, I guess. Feeling meh. But it works!
(Oct 18, 2021)
Let's continue to prepare the Dungeon class to work on hexes as well as square tiles. I expect no real trouble. I look forward to learning why my expectations will not be met.
(Oct 17, 2021)
I have in mind a fun small win on the path to hexes: a multiple dispatch. If nothing else, you may be surprised at what I think is fun. (And I do get in the weeds a bit along the way.)
(Oct 16, 2021)
I said I wasn't going to write an article today. Was I wrong? I want to just look around. And some thoughts on self improvement.
(Oct 15, 2021)
I found the defect, and I think I can fix it. Let's find out. Then I rationalizeXXX explain something.
(Oct 15, 2021)
What's the deal with Jira? Is it a bad thing, or the worst thing?
(Oct 14, 2021)
I'm thinking of adding a shark to the game that you can only escape by jumping over it. Today, however, a bit more on Maps.
(Oct 13, 2021)
Already wrote one article today. Not sure about this one. Probably I'll find an acorn somewhere.
(Oct 13, 2021)
We were thinking about words for code. Let's consider these. New! Improved! Now with more words!
(Oct 12, 2021)
Well, I guess there's nothing for it but to forge ahead getting a hex map to draw. I rather regret committing to this idea.
(Oct 11, 2021)
Can I make a hex map in the game yet, or do I need more than a couple of changes? I don't know. Let's try to find out. Spoiler: Not great, not horrible.
(Oct 10, 2021)
Today, I'm going to try a fun exercise to demonstrate Codea's translate, scale, and rotate.
(Oct 9, 2021)
Today my cunning plan is to try to make the Map the primary container of Tiles, and the tiles collection secondary.
(Oct 8, 2021)
My commitment for the day is to be using the new Map objects for something in the actual game. I think I see at least a couple of ways to go. Spoiler: It's in!
(Oct 7, 2021)
Today I'm going to start plugging the new Map classes into the actual Dung program. I expect a little chaos. For large values of 'little'.
(Oct 6, 2021)
Let's keep on drilling. Real soon now, we'll have hexes in the game.
(Oct 5, 2021)
Another idea? A possibly better idea? We don't pay you to think, we pay you to do.
(Oct 4, 2021)
I promise, I'm nearly ready to plug in the new hex coordinates. There's just one more thing that I want to do ...
(Oct 3, 2021)
In Agile, there's no design. Everyone knows that. So why is there so much design in Agile, and how can they go so fast?
(Oct 2, 2021)
No, not really. Cartesian coordinates, perhaps. Yesterday I was optimistic at session end. How will I feel today? Let's find out.
(Oct 1, 2021)
Frequent readers know that I try to keep my code well-organized and well-designed. No one is perfect. Well, I'm not. Today we face mistakes.
(Sep 30, 2021)
Today I'll do the first experiment, or a few of them, putting hexagonal tiles into the Dung program. I expect this to get really messy, but with luck, we learn a lot.
(Sep 29, 2021)
Today I want to step back and write about screen transformations, translate and rotate. They are fairly natural to me, but some folks are not so familiar with these powerful tools.
(Sep 28, 2021)
In a fit of madness, I decided to try to convert the square-tiled Dung game to use hex tiles. Let's see how well my theory of programming holds up. Just inspection and planning today.
(Sep 26, 2021)
I have to face facts: I simply enjoy writing code and making it better.
(Sep 25, 2021)
Today we'll talk about why no one should do what I've been doing the past few days, and intend to do for a few more.
(Sep 24, 2021)
Bill Wake found an interesting site about hexes (not the magical kind) and now I'm not sure what I want to do.
(Sep 23, 2021)
Let's push this Hex spike a bit further, see what we can learn. Come on, it'll be fun. You can hold my beer. Well, chai.
(Sep 22, 2021)
An idea from the Zoom Ensemble last night has caught my attention. Let's explore it.
(Sep 18, 2021)
Notes on getting up and running on my new Mac. Probably not an interesting article, I'm writing it as a letter to the future me.
rj.com ]
(Sep 7, 2021)
Two ways of doing a thing appeared on the Codea forum today. I'd like to see whether we can transform the one into the other in small steps.
(Sep 7, 2021)
Another in my continued attempts to come to terms with what Scrum is rather than what it could (and should?) be.
(Sep 4, 2021)
Satire? Idiocy? Monkeys? Why not all three?
(Aug 25, 2021)
Again today, I take my writing prompt from GeePaw. I have a good purpose in mind. (Added: Dammit. I didn't expect to end up here.)
(Aug 23, 2021)
Is it useless marketing BS? Certainly there are issues. [CW: language, systemic racism/sexism]
(Aug 22, 2021)
Events in a few worlds lead me to write a few words about how we treat each other.
(Aug 15, 2021)
When someone shows you who they are, believe them the first time. -- Maya Angelou
(Aug 10, 2021)
I've had a reply from the Chief Product Owner of the Scrum Alliance.
(Jul 28, 2021)
I think that today I'm going to write about joy. I have no idea where this goes. Walk with me ...
(Jul 23, 2021)
I mentioned that the dungeon program is boring me on Twitter and asked for ideas. Andreas asked about software design. Practice, folks, practice!
(Jul 21, 2021)
Are we ready to lock classes? Probably not yet.
(Jul 20, 2021)
I'm bored with this program. What shall we do about this?
(Jul 19, 2021)
Jeff Patton writes about the importance of outcomes. Yes, and ...
(Jul 17, 2021)
I've think I've figured out the disconnect between my view of the Scrum Developer priorities, and those of the Refactoring Team who created the new CSD track.
(Jul 16, 2021)
Responses from Scrum officials to my recent Scrum articles here and on more private slacks have not been favorable. I think I'll sum up and move on for now.
(Jul 13, 2021)
I've chosen a large windmill at which one might tilt. Could we, of good heart and great skill and courage, fix Scrum? If so, should we?
(Jul 10, 2021)
The End Scrum Now site, a bit of a rant, raises important issues. Let's explore some of them.
(Jul 8, 2021)
That Temporal Coupling bothers me. What are some ways to resolve it?
(Jul 7, 2021)
I believe that I have fallen into my own trap, Could this be the end of our intrepid hero? Click on in and see.
(Jul 6, 2021)
Just button highlighting, I guess, unless we see something interesting. Ooo, joy! Some tests!
(Jul 5, 2021)
Herewith, some remarks pro-Scrum, and a reminder that Scrum is not as good for developers as it might be. Even some advice to developers.
(Jul 5, 2021)
On June 19th, I sent this email to the CPO of the Scrum Alliance. I have had no reply. In a second article today I will offer some related ideas.
(Jul 4, 2021)
No idea what I'm going to do this morning. Or too many ideas. Let's find out.
(Jul 3, 2021)
One nice thing. One at a time. One nice thing at a time is enough.
(Jul 2, 2021)
A week ago, I posted a Scrum-related survey. Today, the results of that survey, and my comments.
(Jul 1, 2021)
Let's try our new FSM and query logic in the Horn Girl NPC. Watch Jefries add mass duplication and then reduce it!
(Jun 30, 2021)
Those words came up in our Zoom Ensemble last night, and they're part of my theme this morning.
(Jun 29, 2021)
Fantastic day! Completely augured in. Recovered. Brilliant.
(Jun 28, 2021)
OK, I like the Finite State Machine, but I don't like it enough. What can we do to make it better?
(Jun 27, 2021)
Let's get some tests directly on the Finite State Machine. Maybe give it a little shot of YAGNI.
(Jun 26, 2021)
Let's do an experiment with a Finite State Machine, to get a sense of whether we want one.
(Jun 25, 2021)
Extremely Artificial Intelligence: Let's see if we can give our NPC some rudimentary smarts.
(Jun 24, 2021)
Scrum asks for an Increment every Sprint. Of all the Scrum rules, this one is most important for developer success and survival.
(Jun 23, 2021)
A Quest! Let's have a Quest.
(Jun 22, 2021)
Let's try to finish moving InventoryItem to publish-subscribe, and maybe centralize Item creation. And look for Watch This near the end.
(Jun 21, 2021)
Are you wondering why i don't start a new program? There are reasons. Also: let's take the Bus.
(Jun 20, 2021)
Maybe I'll fiddle some more with InventoryItem, Loot, and Decor. Depends what time breakfast is.
(Jun 20, 2021)
Some consolidation and refactoring is what I have in mind. What will I really do? At this moment, I have little or no idea.
(Jun 18, 2021)
A few(?) more thoughts on the battle between Scrum and Software Development. A review of some past thoughts, and some of today's.
(Jun 18, 2021)
I just want to program a bit after all the screed-writing. No promises on what I'll do or whether it'll be any good at all.
(Jun 17, 2021)
The Scrum Alliance mission? Let's talk about that. Fail better.
(Jun 16, 2021)
I'm at a loss to find anything interesting to do. But I bet I can find some code that could be improved. Thinking about an idea from Bruce Onder leads in an interesting direction.
(Jun 15, 2021)
As often happens, this article didn't go where I expected. I hope you like where it went.
(Jun 15, 2021)
Well, with that musing out of the way, what shall we program today?
(Jun 14, 2021)
Today I have in mind an improvement to Announcer, because I think it'll be nice and will give us something to wonder about.
(Jun 12, 2021)
In which our intrepid author muses at length and decides to keep on keeping on. And to do some random stuff, no doubt.
(Jun 11, 2021)
Some odds and ends, a nice feature, and a bit of trouble. And the most distracting thing ever!
(Jun 10, 2021)
Let's pretend we care about that inefficiency in drawingOrder. Also a momentary loss of momentum.
(Jun 9, 2021)
I don't usually predict an outcome but today I think something good is going to happen. Let's find out.
(Jun 8, 2021)
Today, more refactoring to remove connections between dungeon objects and their tiles. And, as always, some thinking.
(Jun 7, 2021)
Two starting ideas: Quest, and removing duplication in the dungeon objects. These are not unrelated. And: as so often happens, we go in a surprising direction.
(Jun 5, 2021)
Maybe some wind for my sails. A need for better notes. An idea from Bryan's experiment with Unity. A thought about apps without programming. Everything is hopeless. Not necessarily in that order.
(Jun 4, 2021)
I am really tired of this game. I think I understand why. Is there anything I can do about it?
(Jun 3, 2021)
Doors, or I'll know the reason why! Just in: Ron bites bear!
(Jun 2, 2021)
Let's advance the game, and try to advance our 'making' tech at the same time. This just in: Bear bites Ron.
(Jun 1, 2021)
What are you doing, Ron, how do you do it, and most of all, WHY?
(May 31, 2021)
Let's set some direction. I'm concerned that I'm off track on what is of value to work on. Possibly it's residual fear from decades ago.
(May 29, 2021)
I think we'll do a bit more on our 'Making App', the part of our code that helps us make the 'Shipping App', the product we ship. (We decide to bless this effort.)
(May 28, 2021)
One more challenge in the class/method finder, then maybe we'll think about what we actually need in our Making App.
(May 27, 2021)
I've had an idea about a change--perhaps an improvement--to the class/method reporter. As I write this, even I don't know what happens next.
(May 26, 2021)
More work on our nascent Making App. Dave1707 has some interesting tricks in his programs. And we have a fine small example of refactoring 'legacy' code.
(May 25, 2021)
Dave1707 from the Codea forum provided an interesting program. I would like to bring it under control.
(May 24, 2021)
Turns out we do a number of small but nice, and somewhat interesting, things. Not much stumbling, sorry. I know you love to see me mess up.
(May 23, 2021)
Let's press on a bit with our learning level. And, I have an idea that may be a bit difficult to implement. Let's hope so.
(May 22, 2021)
'With a little help from my friends', my tests are now fast. All of us are greater than any of us. This is important.
(May 21, 2021)
A bit more on the Learning Level, I think, but I'd really like to make some progress on untangling some mistakes, er, learning opportunities in the code.
(May 20, 2021)
Let's put some announcements in the rooms of the learning level. That should be easy, and it should give us a sense of how designers might want to work.
(May 19, 2021)
I think today I'll work on room announcements. I have a partial idea.
(May 18, 2021)
I have yet another idea about how to handle switching between developer and player modes. This might be what Bruce Onder was talking about.
(May 17, 2021)
Variations on an Idea from the Wild Blue Onder. No success.
(May 17, 2021)
I guess we'll work on the Learning Level, but honestly I'm getting a bit tired of this project. Must think about that.
(May 16, 2021)
A random idea for an interesting dungeon layout may give me some more insight into the tools needed for designed dungeons.
(May 15, 2021)
Still making a place for our new designed dungeon capability to stand. What I'm about to do may surprise you, and raise questions.
(May 14, 2021)
Let's take another swing at moving dungeon creation out of GameRunner. We'll focus on creating our learning level's layout.
(May 12, 2021)
Untangling the knots. Let's see if we can clean up the coupling between GameRunner, tile, and their friends.
(May 12, 2021)
Working toward the Learning Level. Is it time to start on our 'Making App'? We do start. Then we revert.
(May 11, 2021)
Planning the Learning Level. We need to do a bit better than our usual small feature ideas here. Get some shape up in this b- baby.
(May 10, 2021)
The business people--me, with my business hat on--want to be able to better define levels in the game. The tech people--my other hat--get to figure out how to do this.
(May 8, 2021)
We need puzzles. How do we address a big problem like 'puzzles'? Same way you eat an elephant.
(May 7, 2021)
After a brief digression to build polyominoes, we are back in the dungeon. I'm beginning to wonder why. And: Why XP is The Way.
(May 6, 2021)
I was going to move back into the dungeon today, but realized I wanted to talk about what I learned doing the ominoes exercise. Here goes ...
(May 5, 2021)
It is of course necessary to display yesterday's polyominoes, for our viewing pleasure.
(May 4, 2021)
The Zoom Ensemble folks have been playing with polyominoes. I can't resist embarrassing myself by trying them.
(May 2, 2021)
I shipped a defect yesterday. And there was a test for it! What happened?
(May 1, 2021)
More about the crawl. But let's see if we can get the Mimic animated the way we'd like. Unfortunately, these two ideas are not unrelated.
(Apr 30, 2021)
Spikes. My Darling Crawl. And a simple change generates many reverts.
(Apr 29, 2021)
Will this thing never end? More on the Mimic. User(!) concerns. Pluggable behavior.
(Apr 28, 2021)
I'm dismissing my desire to convert to mesh for animation. Let's get that Mimic hiding.
(Apr 27, 2021)
Dave1707 wrote a nice demo showing how to get project information in Codea. Let's think about what it tells us. No code, just think
(Apr 26, 2021)
More with the Animator. Maybe we can get it plugged in today. That would be nice.
(Apr 25, 2021)
Improving the Animation idea. Moar cohesion, less coupling. At least that's the plan.
(Apr 24, 2021)
We're animating our Mimic. Naturally, that leads us to thoughts of coupling, cohesion, and Beck's Four Rules. Naturally.
(Apr 23, 2021)
A bit of a tricky issue today. We want our Mimic to have different animation sequences, depending on what's going on. No other Entity does this at present.
(Apr 22, 2021)
I 'created' new art for an open chest. Then let's see if we can make the Mimic behave differently depending on its mood.
(Apr 21, 2021)
Convert Chests to look like Mimics. Look for other interesting things to do. Short morning today. But some progress.
(Apr 20, 2021)
Let's let the Mimic be oversize. Oh, that works nicely!
(Apr 19, 2021)
There's this thing called a Mimic ...
(Apr 18, 2021)
Today, for fun, I decided to give Decor better query messages. And it was fun.
(Apr 17, 2021)
More work on untangling the objects. Perhaps we'll find some interesting refactoring. Maybe a feature?
(Apr 16, 2021)
We'll start with the garbage collection issue and move on from there. We should be able to remove all Floater's references to GameRunner--if nothing else goes wrong.
(Apr 15, 2021)
Let's drive the bus a bit further. And, I've seen a suggestion for a slightly different angle. We should consider that. Ohhh and a garbage problem!
(Apr 14, 2021)
Let's catch a bus and see what happens. Maybe it will take us to the WayDown.
(Apr 13, 2021)
Once more, into the breach ... is it good luck when Friday the 13th falls on a Tuesday? I may need some good luck.
(Apr 12, 2021)
First, some planning. Then we consider why it's hard to test this thing. What will we decide? I don't know yet. P.S. Turns out to be one of THOSE days.
(Apr 11, 2021)
Alistair found some ancient estimate for a KWIC program and challenged folks to implement it. I'm picking up the challenge.
(Apr 10, 2021)
Deleting tests, not writing tests. A moral issue? Hardly. Also an interesting discovery about InventoryItems.
(Apr 9, 2021)
Some cleaning, I expect. And a user(!) has discovered a defect!
(Apr 8, 2021)
I guess we're going to have to plan a bit today. Maybe a bit more fun with the new more intelligent Decor?
(Apr 7, 2021)
It's interesting how one idea leads to another. I'm sure I have too many ideas now, but some of them seem interesting. The dungeon objects come to life!
(Apr 6, 2021)
Every time these organizations stamp out a new ScrumMaster, there are programmers somewhere whose lives will be made worse.
(Apr 6, 2021)
After getting my blood flowing with a bit of a rant, let's see if we can get a venomous creature up in this ... place.
(Apr 5, 2021)
I hesitate to say that we'll work on poison and antidotes, the way things have gone, but one of these days it could happen. Is today that day? Click to find out.
(Apr 3, 2021)
Musing on Technical Debt. A very interesting series of tiny commits leading to an important change: my invariant.
(Apr 2, 2021)
We have a defect to fix, and, I suspect, a lesson to re-learn. Then, maybe we'll look at poison and antidotes. And liddle lamzy divey.
(Apr 1, 2021)
I think today I'd like to get started on Poison and Antidotes, and on eliminating death from the dungeon. Is that what I'll do today? Maybe. One never knows, do one?
(Mar 31, 2021)
With a handle on pre-planned dungeon layouts, we need to decide what to do next. Have we squeezed all the juice out of this program yet? No real code today, just one little experiment.
(Mar 30, 2021)
Marketing makes an impossible demand. Can we make it possible? If not, does that mean incremental/iterative doesn't work? Is 'Agile' wrong???
(Mar 29, 2021)
Let's make icons in the Inventory do things. Pick something easy, it's Monday up in here.
(Mar 28, 2021)
A good idea from Bruce. Let's move toward it. I have no real idea how to start.
(Mar 27, 2021)
Ron, why do you write this stuff? And let's get that Pathfinder guy working better.
(Mar 26, 2021)
There's a defect! Also, I'd like to do something about creating a monster who leads you to the WayDown. And there's inventory. But first, the defect.
(Mar 25, 2021)
Let's do some work on inventory items and touch to use. That should be amusing in its fashion.
(Mar 24, 2021)
I'm starting to wonder if we have all the juice out of this program, but there sure is a lot that we could still do. Let's consider some options.
(Mar 23, 2021)
Second shot down. Slices looking good. What shall we do today?
(Mar 22, 2021)
Now that we can slice images, let's see what it takes to plug them in. I'm sure we'll need to adjust how things work.
(Mar 21, 2021)
Images, free stuff, ideas, random thoughts. It's Sunday, cut me a break!
(Mar 20, 2021)
Some planning, then something. Come find out with me. I have no plan for the morning.
(Mar 19, 2021)
I really want to make some progress on the creatures that hang around the WayDown. But first, I am going to write a Coda on CodeaUnit and my simple toolset.
(Mar 18, 2021)
I want to get a creature to lead us to the WayDown. And I feel the need to improve the campground. Also St. Gertude. And, as often happens, we don't go where I expect. Neat outcome, thoughl
(Mar 17, 2021)
Top o' the morning' to ya, and I think we'll be starting on a set-piece today. Unless I change my mind. Also, some ranting about Definition of Ready.
(Mar 16, 2021)
More pathfinding, that's the plan. Testing is likely to be harder than doing.
(Mar 15, 2021)
I think today I'll try some pathfinding. And, yes, I have a story asking for it.
(Mar 14, 2021)
It's Pi Day, Sunday, and I think we'll take a look at our new Strategy object with fresh eyes, if we have any.
(Mar 13, 2021)
What we need here is a Strategy. Well, not so much need. Want.
(Mar 12, 2021)
Thoughts on throwing things away. And let's move these monsters.
(Mar 11, 2021)
A bit more on Monster movement. I'm not certain the implementation is correct. After that, I'll think of something.
(Mar 10, 2021)
Thoughts on 'Tiny Habits', maybe a change to Monster behavior, maybe poison.
(Mar 9, 2021)
A time for healing. Gonna do it this time.
(Mar 8, 2021)
It's International Women's Day here at the dungeon, so let's see whether we can give the Princess the ability to heal.
(Mar 5, 2021)
I noticed something significant last night. Something I don't recall ever really thinking about before. Of course, in 8 decades you forget a lot ...
(Mar 4, 2021)
Today we'll follow up a good idea from an idea source that is new to me. I expect that we'll have an interesting and desirable outcome. Interesting, at least.
(Mar 3, 2021)
Will this thing never end?? Let's take a small cut at inventory.
(Mar 2, 2021)
Implementation inheritance? Why not? A challenge to my betters.
(Mar 1, 2021)
Some small cleanup items. Then ... I don't know, I'll have to wait and see what I do.
(Feb 28, 2021)
Today, I'm going to create a new class to deal with Monsters. And I'll tell you why it's OK to do that. And it'll be in tiny increments!
(Feb 27, 2021)
Hide the WayDown. Make the spikes spikier. A new test, and a smarter DeferredTable improves some code.
(Feb 26, 2021)
We have to set a trap in a hallway. Let's make that more efficient to do. Also, we don't do it in the more efficient way after all. Also invariants. Also: Ron defines 'should'.
(Feb 25, 2021)
I have traps in mind, and smarter monsters. Is that what the day brings? One never knows, do one?
(Feb 24, 2021)
Monster levels should be easy. Then I wander off into code improvement.
(Feb 23, 2021)
Let's get items properly distributed. After that, some leveling, perhaps. I don't know. I'll have to wait and see what I do.
(Feb 22, 2021)
I feel the need to make Dung a bit more like a game, with levels and such. Let's start pushing in that direction.
(Feb 21, 2021)
A second cut at TDDing the music players. Simple isn't easy.
(Feb 20, 2021)
I decide to redo the music playing logic with TDD. Results are mixed.
(Feb 19, 2021)
Music? And then, idk, something else. Maybe refactoring? Poison?
(Feb 18, 2021)
Verbs. Then, who knows?
(Feb 17, 2021)
Today, girls just want to have fun, and so do I.
(Feb 16, 2021)
Combat and the Crawl have been kicking my tail. This does not please me, even a little bit. I'm sure the difficulty is at least partly due to a poor description of the problem, leading to poor solutions. Today I win.
(Feb 15, 2021)
Let's clean some code. Let's also try to make combat more interesting. Let's also try to stay out of trouble. Is that so much to ask? (As usual, the plan changes before long. Also, trouble.)
(Feb 14, 2021)
Happy Valentine's Day. In other news, I have an idea.
(Feb 13, 2021)
A new day dawns. New chai. Consolation from the Zoom Ensemble. Technical debt. And another run at combat.
(Feb 12, 2021)
Wow, he's really dragging this one out, isn't he? Let's do some more Combat, round this out a bit. Later: Things go very wrong. This is a debacle.
(Feb 11, 2021)
Let's work a bit further on combat. I'll start with something easy, but there are some possibly tricky roads ahead. (Plus, Ron comes out against death.)
(Feb 10, 2021)
Let's see how far we can push this 'little language' we're making for combat. I should try something tricky next, to be sure the idea can bear weight.
(Feb 9, 2021)
More on Combat. I have now been advised by my betters on how, possibly, to test this thing. I may have an angle.
(Feb 8, 2021)
Let's start on our new combat logic. But first, those failing tests ...
(Feb 7, 2021)
Now for some magic. How can we get screen effects synchronized with the information crawl? You won't believe this cunning plan!
(Feb 6, 2021)
Everyone thinks they know how I should do combat. There are issues that daunt me. I'm sure there's a pony in here somewhere.
(Feb 5, 2021)
Last night I found a rather embarrassing defect. Fortunately, there are probably lessons to be learned.
(Feb 4, 2021)
More on turn-based. Let's try converting Encounter to a combat round, or writing a new combat round. Or something else.
(Feb 3, 2021)
Input from Bruce. And our turn-based implementation isn't quite good enough yet. I'm not sure what to do about that.
(Feb 2, 2021)
In my roles as Product Owner and Chief Game Designer, I have thrown me in my role as Programmer a curve: We want me to make the system turn-based.
(Feb 1, 2021)
Let's do some more user input. And some planning, not necessarily in any particular order.
(Jan 30, 2021)
You know that thing where they ask you for something no one ever thought they'd ask for? They just asked for it.
(Jan 29, 2021)
Let's talk about some design aspects, starting with the new DeferredTable. Then we'll follow our nose. But there's kind of a paradox.
(Jan 28, 2021)
Let's try a more conventional approach to our deferred collection. First, some words on why it's a good idea.
(Jan 27, 2021)
Let's reach deep into the bag of tricks, and see whether we like what we find there.
(Jan 26, 2021)
Let's use the new Loot object for Health and Keys. That should test the concept and drive out some nice clean generality. (N.B. Plan changes one page in.) Worse yet: hours of confusion!
(Jan 25, 2021)
Loot today. And a possibly interesting problem.
(Jan 24, 2021)
Just some little things. There may be nothing interesting to see here. One never knows, though, do one?
(Jan 24, 2021)
A tricky graphics issue. And about those walls. Is there a problem?
(Jan 23, 2021)
Let's try the wall data. This calls for a slightly different scheme, I think.
(Jan 22, 2021)
An interesting problem. Is there a clean solution, or do I need a bigger hammer?
(Jan 20, 2021)
Random floor tiles, why not?
(Jan 19, 2021)
New Tiles? Torches? Redecorating the Dungeon.
(Jan 19, 2021)
Why do I almost always do something other than I planned to do yesterday? It's a mystery.
(Jan 17, 2021)
Some display work. Then let's start on treasures. I have a cunning plan ...
(Jan 16, 2021)
Damage display, and what about showing attacks? I have a few weak ideas ... WARNING: Big movie files.
(Jan 15, 2021)
Some thoughts on the world as I see it today, in 2021, from my privileged vantage point as an old white guy in the USA.
(Jan 14, 2021)
Mostly some thinking and planning about behavior. Maybe some code. Now: with movies!
(Jan 13, 2021)
Just a little bit more, for an afternoon's relaxation.
(Jan 13, 2021)
Let's finish up and clean the coroutine message floater, and purge the unused tabs. Then make all the tests run. Then, stick our head up and look around.
(Jan 12, 2021)
More on Encounter coroutine version. Rationalizing not doing much more TDD. Will he be sorry?
(Jan 10, 2021)
I'll save you some reading and trash the first version of this article. I will sum up. Then I'm going to try a coroutine. Hold my chai.
(Jan 9, 2021)
More work on Encounter. I still want the fighters to separate after a round.
(Jan 8, 2021)
Today, more work on combat encounters. I have in mind separating the fighters.
(Jan 7, 2021)
Fortunately, I have programming to distract me. But there's too much going on in there, too. Also: a rather large mistake.
(Jan 6, 2021)
Let's display Encounter results before we enhance it further. This may become tricky, but let's hope not.
(Jan 5, 2021)
More thinking and doing on combat encounters. Can we avoid turn-based?
(Jan 4, 2021)
I'm sorry--I have to do some planning. Then maybe some code.
(Jan 3, 2021)
Tweak attributes. Make some tentative decisions on combat.
(Jan 2, 2021)
Let's try again today to improve the character sheets. I have a new idea. That rarely goes well.
(Jan 1, 2021)
Character sheet for the player today, then a daunting bug, er, defect.
(Jan 1, 2021)
Thanks for visiting! If you value what I do, here are some ways you can support my work.
(Dec 31, 2020)
Probably my last article of 2020. Some thoughts on these articles, and the design of OO programs. Perhaps a character sheet for the Player.
(Dec 30, 2020)
I think we need to work on treasures today.
(Dec 29, 2020)
More work on Character Sheets, and a feature idea from Twitter follower WR. Nothing interesting happens.
(Dec 28, 2020)
Levels, treasures, or character sheets, that is the question. The answer is only a bit interesting. One good bit tho.
(Dec 26, 2020)
Monsters. We need more monsters. Bigger, badder monsters.
(Dec 25, 2020)
While I wait to see whether Santa came, I want to enhance Monster movement a bit. This will require the TileArbiter table and code to change.
(Dec 24, 2020)
Not a political idea, but perhaps it should be. But I digress. Let's do on-screen controls.
(Dec 23, 2020)
Let's do some more with the TileArbiter, including plugging it in to actual game play.
(Dec 22, 2020)
If at first you don't succeed, try something different. Sorry, no pics or movies today. Just code.
(Dec 20, 2020)
Probably not THE answer but maybe some small ones.
(Dec 19, 2020)
Brute force FTW, a sound in the silence, and ... I don't know what else yet.
(Dec 18, 2020)
Lighting? Better lighting? In a DUNGEON??? Are you serious?
(Dec 17, 2020)
Let's create a mini-map.
(Dec 16, 2020)
Double dispatch! Chet will be so proud. Or jealous. And Keys!
(Dec 15, 2020)
It's time to put some game-playing features into this thing. That could lead anywhere, but I'm hoping today at least will be easy.
(Dec 14, 2020)
More refactoring: I want more habitable code to work in. Maybe one tiny feature.
(Dec 13, 2020)
Too many notes. Just refactoring today, with reasons why.
(Dec 12, 2020)
More pushing things to Tile. I'm required by law to publish this but I'm not required to like it.
(Dec 11, 2020)
Today I'm interested in learning something about how far to push the 'tile' design. Join me.
(Dec 10, 2020)
Maybe give the monsters a bit of volition. Maybe place them randomly. Maybe some screen controls. Who knows, I just write this stuff.
(Dec 9, 2020)
I believe that the dungeon should have some monsters in it. Let's take a cut at that. Also, I provide an overview of how it works.
(Dec 8, 2020)
I think we should refocus the design a bit, for improved graphics. This promises to confuse me.
(Dec 7, 2020)
Let's limit the Princess's view of the dungeon. I know one way to do that. Let's think of at least one more.
(Dec 6, 2020)
Two nice little things. A short report. Thanks to GeePaw for one of them. A weird explanation for the other.
(Dec 5, 2020)
I'm fairly satisfied with room and hallway generation. It's time to work on what the screen looks like in play.
(Dec 4, 2020)
Let's get some rooms up in this ditch.
(Dec 3, 2020)
It helps if your tests actually check something. Sounds like a good idea, let's try it.
(Dec 2, 2020)
Current plan is to move forward from the little tiled-space experiment, evolving it into a playable game. If I'm right, we should see faster progress. It could happen.
(Dec 1, 2020)
A New Hope, from a New Direction. Yes, that's right, I'm thinking about starting over. Could this be a good idea?
(Nov 30, 2020)
Technical debt, or messy code? Why not both?
(Nov 28, 2020)
Another run at moving into the new hallway rooms and back out again. Fortunately, as I mention at the end, my purpose isn't to show you how smart I am.
(Nov 27, 2020)
Session was a total loss. Do not read: Still working on letting the Princess get out of room one. After creating doorway-hallways as rooms, we're getting close.
(Nov 26, 2020)
So many things to be thankful for here on Thanksgiving. One small one, I hope, is the Rectangle. Then, a wild Andrew appears!
(Nov 23, 2020)
I guess I should work on putting a player in the room and moving her about.
(Nov 19, 2020)
More tiling, trying to make all the floors align.
(Nov 18, 2020)
A new, possibly better idea about room tiling. That may be enough for the day. We'll see.
(Nov 17, 2020)
More like a game, step by step. There's arithmetic involved. I hate that.
(Nov 16, 2020)
There's a bit of tidying up I'd like to do, but I think we have to start making this act more like a game.
(Nov 14, 2020)
The Zoom Ensemble met last night. Our 'work' gave me some ideas. Plus we have an issue to resolve.
(Nov 13, 2020)
My plan, the day notwithstanding, is to get door markers drawn and, with luck, improve the design. But I'm not sure that's what I'd advise.
(Nov 12, 2020)
I wouldn't call them ideas, exactly, but I have some things I want to try.
(Nov 11, 2020)
Is there a difference between creating a better design and discovering one? I think so.
(Nov 10, 2020)
Some thoughts on consistency, clarity, abstraction, and efficiency. A LOVELY REFACTORING!
(Nov 9, 2020)
Feature or improved code? Maybe a feature spike? Who knows, not I.
(Nov 8, 2020)
My recursive pathfinder doesn't work as I thought it did. This cannot endure.
(Nov 7, 2020)
Today I think I need to deal with tiling, or decide that we can do without it.
(Nov 6, 2020)
I've become aware of some issues, as should be expected in a new venture. The question is what to do about them.
(Nov 5, 2020)
Most of what I did yesterday was dreck, detritus, dung. Not very good at all. I plan to revert today and figure out a new plan.
(Nov 4, 2020)
I can't face reality, so I'll keep working on this little imaginary world. At this moment, no idea quite what I'll work on.
(Nov 3, 2020)
Today, I think, separation of the primeval blob of rooms.
(Nov 2, 2020)
Some pals are Zoom-mobbing on a dungeon program that one of us was working on. I'm gonna try one in Codea.
(Oct 30, 2020)
I asked myself, and Twitter, a hard question the other day. Today, I'm going to try to answer it.
(Oct 28, 2020)
Today, some code review. No big plans. We'll see what we see. I expect to mention Beck's Four Rules.
(Oct 27, 2020)
We'll look at using invader count as a flag to start a new rack. I don't promise to change it.
(Oct 26, 2020)
I don't feel very bright this morning. Let's see if I can prove it.
(Oct 23, 2020)
I have an idea and I can't wait to try it out. Niagara Falls.
(Oct 23, 2020)
Today's plan: Code review, and targets of opportunity. Short morning, just one new class.
(Oct 22, 2020)
Displaying two player score. Beyond that, we'll see.
(Oct 21, 2020)
Attract mode needs to be turned back on. Maybe we should show both players' scores. What about those buttons?
(Oct 20, 2020)
Let's do more on the two-player game mode. We're probably getting to the hard part.
(Oct 19, 2020)
It's time to start on the two-player option. I have ideas but not precisely a plan.
(Oct 18, 2020)
A lesson from history, a surprise refactoring, and, apparently, a sermon.
(Oct 16, 2020)
Not really, but the saucer is looking to score.
(Oct 14, 2020)
A Slack conversation brought up the question of why I do ... the things that I do.
(Oct 13, 2020)
The Agile Manifesto says that working software is the primary measure of progress. What does that mean?
(Oct 10, 2020)
This morning, rather than toil over the scattered bodies of evil but admittedly cute space invaders, I'm minded to talk about privilege.
(Oct 9, 2020)
Users observe the need for more racks of invaders. That's going to get ... interesting. Also Game Over if they reach bottom.
(Oct 8, 2020)
I've convinced myself that a global would be a better way to handle constants than the singleton. Kill your darlings.
(Oct 7, 2020)
Users have detected a problem. Users, do you hear me? Users!
(Oct 6, 2020)
Improving zombie behavior. Sound adjustments. Maybe more. Maybe less.
(Oct 5, 2020)
Let's take a look at a simple attract mode. Zombies!
(Oct 4, 2020)
More with Singletons. And distractions. And no singletons.
(Oct 3, 2020)
Improving our Singleton and using the idea elsewhere.
(Oct 2, 2020)
There's no reason to think that I'm smarter today than I was yesterday, but I am a bit more experienced.
(Oct 1, 2020)
Touch to Start has me thinking that attract mode might be within reach. Things go Very Wrong.
(Sep 30, 2020)
Saucer Scoring, then whatever makes sense to me at the time.
(Sep 28, 2020)
Another day of improv. Let's see what looks worth doing. (Wow, a factory object!)
(Sep 26, 2020)
What shall we do today? I honestly don't know.
(Sep 26, 2020)
Remarks on a Twitter comment from Jez Higgins.
(Sep 25, 2020)
Another defect. I'm starting to feel ... afraid. That's not a good sign.
(Sep 24, 2020)
This isn't Houston, but we definitely have a problem. And it's not a new one. And I'm tired of it.
(Sep 23, 2020)
Things we might do. And I'm thinking about conditionals. The next trick may surprise you.
(Sep 22, 2020)
I have an idea. Let's find out if it's a good idea.
(Sep 21, 2020)
Maybe some tuning. Do we need more start-up settings? Should the test results disappear? What about a FireControl object?
(Sep 19, 2020)
The world is burning, and I'm really just trying to ignore reality, but in addition, I've made a mistake. Another mistake, that is.
(Sep 18, 2020)
If nothing else, you have to admire me for getting over 100 articles out of ancient video games. Let's do another today.
(Sep 18, 2020)
A couple of interesting articles crossed my virtual desk yesterday. Links and some reflection within.
(Sep 17, 2020)
Better scaling, then more with the saucer, I guess. Plus whatever opportunities we spot.
(Sep 16, 2020)
More with the saucer, that's my plan.
(Sep 15, 2020)
I know the voices in my head aren't real, but they're sure ticked off at me for the past few days of messing up.
(Sep 14, 2020)
Well this goes entirely not as planned. Double Arrgh.
(Sep 14, 2020)
In which our intrepid author makes a grievous error: disagreeing with Kent Beck. Or does he?
(Sep 12, 2020)
No, not space pirates all of a sudden. I released a fatal defect yesterday. What's up with that?
(Sep 11, 2020)
A couple of small changes to CodeaUnit and my CUBase template. Then let's see what we can improve about Space Invaders. (Saturday: Arrgh, a defect!)
(Sep 10, 2020)
More to do with bombs, especially targeted ones. We need some refactoring as well. The results may surprise me.
(Sep 9, 2020)
I think today we'll work on the bomb timing, and targeting the rolling bomb. Often, what I think will happen is what actually happens.
(Sep 8, 2020)
Let's continue the bomb dropping logic. Our current design can't do what's required.
(Sep 7, 2020)
Speed indicator; Bomb dropping order; Free player, maybe.
(Sep 5, 2020)
Some recovery from repo problems, some work with the clock, whatever else seems right.
(Sep 4, 2020)
The web site with sounds came back, so I'm scarfing them down and starting to install them. Should be mostly straightforward, he said. Except when my repo locked up.
(Sep 3, 2020)
If you're like me, you're wondering what space invaders eat. The answer will surprise you.
(Sep 2, 2020)
Let's damage shields from below, and try to continue small steps toward 'better', whatever we mean by that.
(Sep 1, 2020)
Let's make missiles explode, and continue improving this design.
(Aug 31, 2020)
I want to figure out why this program makes me feel bad. Then do something about it.
(Aug 27, 2020)
Some improvements. But first, a word about less technical matters, the book `x + y`, by Dr Eugenia Cheng.
(Aug 27, 2020)
A bit of planning, a bit of action.
(Aug 26, 2020)
Let's get a start on scoring. This should be easy enough. But--when is too much way too much?
(Aug 26, 2020)
I woke up this morning certain that some of my bitmap calculations were STILL off. Something has to be done.
(Aug 25, 2020)
A bit more exploding. I'm going to continue to let things get messy.
(Aug 24, 2020)
Let's do some damage
(Aug 21, 2020)
It's my ball and if I want to play with it you're not the boss of me.
(Aug 20, 2020)
One of these two things is not like the other ...
(Aug 19, 2020)
If the world isn't flat, how come these invaders keep falling off the edge?
(Aug 18, 2020)
Today we'll try to fix the collision logic to accommodate our origin changes, and to make the invaders explode.
(Aug 16, 2020)
I've moved the good iPad into the TV room and while waiting for our Sunday festivities to start, I'll set up the project's bitmap assets.
(Aug 14, 2020)
Having decided to move to CORNER mode from CENTER, we've got some work to do. I'm hoping this one isn't interesting.
(Aug 13, 2020)
Is it worse luck when Friday the 13th comes a day early? Or a near miss? Time to dig further into bombs failing to miss shields. (Added Friday: It was worse luck.)
(Aug 12, 2020)
I had no plan. Now I have a plan. Check code clarity, then work on shields. Things go ... oddly
(Aug 11, 2020)
Maybe make the invader bombs do some damage? Or what?
(Aug 10, 2020)
My plan for the day is to retrain myself by reading this code that I've not touched for two whole days, and then to see about moving things forward. My guess: invader missiles.
(Aug 7, 2020)
I think today I'll work on making the invaders march back and forth. Right now they just march forth and forth and forth ...
(Aug 6, 2020)
A friendly demo of shield damage techniques leads to an examination of an interesting coding approach. I need to figure out what I think about it.
(Aug 5, 2020)
It's 6 bloody AM and I'm programming. What's up with that?
(Aug 4, 2020)
Let's see about extending our square invaders game-like thing to be a bit more like a game.
(Aug 3, 2020)
Twelve articles and no product. What's up with that?
(Jul 30, 2020)
Adam Savage (@donttrythis) posted a marvelous video of his attempt to build a giant brass nut and bolt. It reminds me of software.
(Jul 22, 2020)
In the real game, the invaders' missiles eat away at the shields. How can we duplicate this effect?
(Jul 21, 2020)
An experiment and some planning. Then even some doing.
(Jul 20, 2020)
Learnings from the ancient scrolls. What shall we do about them?
(Jul 18, 2020)
This one is mostly for the record, if it goes as planned. I'm just going to import some more bitmaps. I recommend against reading this.
(Jul 17, 2020)
Let's see what happens if we try to refactor our little spike into something reasonable.
(Jul 16, 2020)
A bit of an idea about marching, and thoughts about spikes.
(Jul 15, 2020)
I need an idea. Representation is important.
(Jul 14, 2020)
I'm wondering how to move these invaders. Let's do an experiment.
(Jul 13, 2020)
Dave1707 from the Codea forum shows a much better approach to converting the bitmaps.
(Jul 11, 2020)
Importing Invaders. How hard could this be?
(Jul 10, 2020)
I'm having so much fun with Asteroids that I thought I'd look at the old Space Invaders game. I'm sure I'll learn something.
(Jul 10, 2020)
I'm going to try to write today about social concerns. It would be easier to write about Asteroids, and I'm sure I'd be better at doing that.
Social ]
(Jul 9, 2020)
Let's clean up that level handling a bit.
(Jul 8, 2020)
Unfortunately, we need to take things to whole new levels. This'll be fun. (Later: not as interesting as some, but it has its moments.)
(Jul 7, 2020)
Let's get some more modernization up in this baby. I'm sure it's the only reason we aren't selling millions.
(Jul 6, 2020)
Let's see about reducing a Singleton or two, and maybe some more modern graphics.
(Jul 6, 2020)
Our marketing people have a challenging request: modernize the look of this game.
(Jul 2, 2020)
It could happen: I've figured out a good way to handle these callbacks.
(Jul 1, 2020)
We'll continue our code review, with particular attention to our tweens, especially that tricky one.
(Jun 30, 2020)
I feel like reviewing some code. What I learn? Kill your darlings.
(Jun 29, 2020)
We're nearly done here!
(Jun 29, 2020)
Some tweaks to hyperspace seem in order, but I feel that this thing is nearly done.
(Jun 27, 2020)
Enhance Hyperspace?
(Jun 26, 2020)
Perfect saucer shots and a start on hyperspace.
(Jun 25, 2020)
Let's put in some options.
(Jun 25, 2020)
Let's clean up the Aimer and look around. I think we need options.
(Jun 24, 2020)
I really want to crack missile targeting. I've made some observations.
(Jun 22, 2020)
Two things go right. One thing goes horribly wrong
(Jun 20, 2020)
Free ships. Beyond that, maybe some reorganization? No, more like confusion.
(Jun 19, 2020)
Let's finish up the small saucer, and how about testing it this time?
(Jun 18, 2020)
Ships Remaining Indicators. After that, who knows?
(Jun 17, 2020)
After some discussion of things we might do, we decide to do GAME OVER. The results will surprise you.
(Jun 16, 2020)
Run tests automatically, dribs, drabs, and oddities. Pretty calm.
(Jun 15, 2020)
Today I plan to give the saucer the ability to aim its shots. I anticipate zero trouble.
(Jun 13, 2020)
A bit of planning and a bit of doing.
(Jun 12, 2020)
Not really an answer, but just a bit of fun.
(Jun 11, 2020)
Some sound, and saucer needs to stop helping so much.
(Jun 9, 2020)
Let's do collisions. And try to TDD them.
(Jun 9, 2020)
We move saucer and ship in the direction of our new scheme, and get rid of the cloning of the collection. Also took a nice walk.
(Jun 8, 2020)
We made a number of useful changes last time. Let's harvest some value.
(Jun 8, 2020)
I'm sure my double dispatch approach will work fine. But the pattern seems simpler than that ...
(Jun 7, 2020)
Some thinking and working on collisions. Is Ron converting to London School???
(Jun 6, 2020)
I've determined that it's time to collapse some 'technical debt', in small, incremental steps.
(Jun 6, 2020)
We need to improve collision detection. I think we have to do it in one go.
(Jun 5, 2020)
I think this afternoon I'll just push a little further on the saucer. Maybe make it dangerous.
(Jun 5, 2020)
I've decoded how to draw the saucers. Let's see about making them fly. That will require some research.
(Jun 4, 2020)
Some rationale, an experiment, some learning, some protection.
(Jun 3, 2020)
We start asteroids on the edge, which gives us an edge on refactoring.
(Jun 3, 2020)
A new approach to steering. And an apology.
(Jun 1, 2020)
I need to say a bit about what's going on in the world today, and to confess how it's affecting me.
Social ]
(Jun 1, 2020)
I found some better recordings of the Asteroids sounds. And it's time to trigger new waves.
(May 31, 2020)
Stereo, because I can.
(May 30, 2020)
Based on the 'learning' from #25, let's just make bigger buttons.
(May 30, 2020)
Today I decided to experiment with improved controls. The experiments, um, succeeded oddly.
(May 29, 2020)
New ship, new sounds, learn new tricks, amaze your friends, confuse your enemies. Apply now! UPDATED!
(May 28, 2020)
I think today we'll do waves of asteroids. And some tests.
(May 27, 2020)
I've made yet another mistake. Will the embarrassment never end?
(May 27, 2020)
I reckon it's time to kill the ship when it's hit by an asteroid. I have a clever way to do it and a direct way. Which is best?
(May 26, 2020)
I'm feeling like coding a bit this evening. So stand back.
(May 26, 2020)
Thinking about tests and refactoring. The boss wants a feature.
(May 25, 2020)
I think it's time to move more toward objects. Part of our mission is to decide what we like. And: 'No large refactorings!'
(May 25, 2020)
I thought I knew what we had to do today but I was a bit mistaken. We need more, and better thinking ... and code.
(May 24, 2020)
Just arriving 'at work' this morning, I'm thinking we'll make the Ship move. We need a safe place to land first. EDIT: Arrgh, a defect!
(May 23, 2020)
A report on last night, and a 'major' refactoring. P.S. There is no such thing as a major refactoring.
(May 22, 2020)
A quick report on a short project last night, then let's try to get something nearly playable.
(May 21, 2020)
I looked up tween and my tween example and it seems like just the thing. Let's find out.
(May 21, 2020)
First, I'm really feeling the need to improve this code. But maybe it's too soon to do good work? Plus explosions.
(May 20, 2020)
Displaying different shaped asteroids is nice, but we have an issue of size we might work on for a bit. And let's split them!
(May 20, 2020)
Having converted the 6502 asteroid shapes to Codea style, let's plug them in. This design is starting to bug me, and we'll think about that too.
(May 19, 2020)
Dave1707 offers a much better idea for the conversion of Asteroids graphics into Codea. Let's explore it.
(May 18, 2020)
I found the definitions of the asteroid shapes in DVG language. Let's draw them in Codea.
(May 17, 2020)
I spent last night decoding some graphics chip code on computerarchaeolgy.com, and I managed to draw an Asteroid in the classic style. Today, a look at what I found out. Updated: New Resource.
(May 16, 2020)
I've decided how buttons should work. It only remains to make it so.
(May 15, 2020)
To move forward with this project, the ship needs to be able to move forward. And turn. And fire ...
(May 14, 2020)
OK, Asteroids doesn't have a horizon, but today we'll start on the ship. Shouldn't be too hard: it's a triangle.
(May 13, 2020)
I needed to test some floats the other day. Let's improve CodeaUnit to help with that.
(May 13, 2020)
Today we'll clean up the code a bit. It really needs it.
(May 12, 2020)
Today I decided to draw two square asteroids at random angles. All's well that ends well, but I did get confused.
(May 11, 2020)
For something to do, and because it might be helpful to new Codea users, I'm going to implement an homage to the old Asteroids game.
(May 5, 2020)
The Gilded Rose 'kata' exists in many languages, but I've not seen Codea Lua. Maybe I should fix that bug. This is pretty boring. Skim, don't read. Needed for the record.
(May 2, 2020)
Some final thoughts on the Gilded Rose exercise. Well, final for now ...
(Apr 30, 2020)
To round out a dozen, we simplify things a lot. Too much? What do you think?
(Apr 29, 2020)
Experiment with lambda.
(Apr 28, 2020)
Today I think I'll double-check that double-decrement issue. Then I want to see if we can combine those two parallel if nests.
(Apr 27, 2020)
Some really nice progress today ... and one open question.
(Apr 25, 2020)
Dave Nicolette mentioned on Twitter that he was wondering whether a Mob Programming Gilded Rose kata, using Arlo Belshee's 'Read by Refactoring' would make a good video. That gave me an idea.
(Apr 24, 2020)
We're on a path more like re-implementing the program than refactoring it. That's a concern. Can we do better?
(Apr 22, 2020)
Today I plan to move the Conjured item code to the new scheme, and see what that tells me. Something will probably go wrong.
(Apr 21, 2020)
It's noon on Tuesday. I've whiled away the morning. Let's try to make a bit more progress on this code.
(Apr 20, 2020)
Monday, Monday ...
(Apr 18, 2020)
Are we doing it right? Are we in trouble already?
(Apr 17, 2020)
It's April 17th. It's snowing. We're on lockdown. Let's look at Gilded Rose and see what we might do that would be interesting.
(Apr 16, 2020)
Chet, Amitai Schleier, and I played with the Gilded Rose exercise the other day. I think I'll write about it a bit, starting from scratch. [edited]
(Mar 22, 2020)
Wow. Shapr 3D is neat! I wish I could use it. It's so cool I might warp my process just to fit it into my plans.
(Mar 18, 2020)
This may be the most powerful most frustrating 3D application ever created.
(Mar 17, 2020)
To create reasonable creatures or vehicles, I'd need a decent 3D object creation tool. Ideally, since this is an iPad project, an iPad app.
(Mar 11, 2020)
I am supposedly on a course to make the Orc stay within bounds of our little world. Today might be the day ...
(Mar 9, 2020)
It's probably time to work on behavior, so I want to take a bit of time to look forward at what we might do, might not do, and probably won't do.
(Mar 8, 2020)
It's Sunday. My long-suffering wife is prepping for the upcoming election. On my own, I decided to spike motion for my game creature.
(Mar 7, 2020)
I've decided a bit about the 'game' I'm writing in Codea. This should keep me off the streets for a while.
(Mar 3, 2020)
I've been reading examples and searching the web about terrain generation and I'm ready to start sharing. Brace yourself, this gets pretty random.
(Feb 28, 2020)
I feel I've got my feet firmly on the grass, dirt, and bedrock, and I can see what I'm doing. Time to become confused again.
(Feb 27, 2020)
I think I nearly have a solid place to stand: a tiny application that I understand pretty well. Today we'll clean it up and see what's next.
(Feb 25, 2020)
There's trouble, my friends, right here in river city. Is this little project serving my needs? Am I about to break through to the other side ... or to break through the ice and freeze?
(Feb 17, 2020)
We're at a fairly clean point right now. There are a couple of small topics in the code to consider, but we need to figure out a plan for what's next.
(Feb 17, 2020)
Owing to driver error, I lost all my code versions for the Orc program. We'll speak of recovery and then move on.
(Feb 11, 2020)
In response to some question on the codea.io forum, Dave1707 showed me a neat trick with text. It taught me something, and raised some questions.
(Feb 10, 2020)
Despite its great value in the hands of experienced TDDers, the uptake is slow and the practice is often hard to sustain. What's up with that?
(Feb 7, 2020)
The bird experiment worked pretty well. Now it's time to clean it up and consolidate what we've discovered.
(Feb 5, 2020)
I've made a couple of objects move, in two different ways. I figure that topic is spiked. What should I look at next? This session is gonna be rambling, I'll wager.
(Feb 4, 2020)
Today I'll build a different kind of creature, who moves differently from the Orc. The idea is to build up an understanding of where the design needs improvement in terms of flexibility or clarity.
(Feb 3, 2020)
Today I'll review the code, and think about whether to build in some object thinking. I want to ... but should I?
(Jan 31, 2020)
Last time I managed to make a fairly simple Codea Craft program draw an Orc standing on (or near) the floor. Today I plan to make him move a bit, and then to see what I've learned.
(Jan 30, 2020)
Yesterday I managed to move an Orc, by hacking a sample program. Today, let's try to do a clean version to consolidate our learning and ask ourselves some questions. Maybe even begin to answer some ...
(Jan 29, 2020)
I begin trying to make sense of Codea's ambitious and powerful Craft components.
(Jan 20, 2020)
>Alex Bunardzic has been part of a rambling Twitter thread about TDD and people who object to it. One of his concerns is that TDD proponents agree that TDD isn't always appropriate but don't say when. Let's explore that.
(Jan 18, 2020)
I tweeted this on the 18th, in response to something left frustratingly vague by one of my dear colleagues, which caused me to think more deeply about what they said.
(Jan 8, 2020)
Some folks who don't know TDD, and some folks who should know better, have been describing TDD in ways that don't match what I experience. Herewith, some thoughts.
(Jan 8, 2020)
In a Twitter conversation a week or so ago, I was asked to do a TDD video, to show how I do it. A video isn't within scope just now, but here's an article with real TDDed code in it.
(Nov 28, 2019)
A Medium article with an interesting mix of observation and questionable opinion inspires me to write what I hope will be the same. 😈
(Nov 25, 2019)
Despite my concerns about experienced coaches advocating against practices that are often quite useful, there are a few things where I'd at least advise great caution.
(Nov 24, 2019)
Some thoughts from Twitter on 'technical debt', what it is, what it isn't, and why we avoid it.
(Nov 24, 2019)
Why do we do that? One word: Productivity
(Nov 24, 2019)
A number of blogs, tweets and emails have crossed my 'desk' lately, gently or strongly advocating against some generally well-thought-of practices. I'm troubled by that.
(Sep 15, 2019)
This article expresses, in written form, the talk that Chet Hendrickson and I gave at the deliver:Agile conference.
(Sep 12, 2019)
A private note from GeePaw Hill, and a tweet from Brian Marick inspire me to mumble a bit about mindfulness and collaboration.
(Sep 10, 2019)
When I was blurting about the Increment as the most important thing, just the other day, GeePaw Hill mused about collaboration as the most important thing. Today, I'll muse on that and his notion of makers-making-made.
(Sep 5, 2019)
If you are not producing working, running, tested usable software in every single Sprint or iteration, you are not [yet] 'doing' Agile, you are not [yet] 'doing' Scrum.
(Aug 29, 2019)
A question on AgileMentoring.com triggered this little article. Perhaps repetition is the mother of something ...
(Aug 24, 2019)
Kate chats with people at the KALE Society meetup. They discuss some small issues and then one big one. Test Doubles come up. Darts are thrown.
(Aug 20, 2019)
A Twitter conversation and some reading has triggered some new, and probably some old, thoughts on estimation and the #noEstimates tag and meme.
(Aug 5, 2019)
A bit of a screed about naming, triggered by a super idea from Dan Terhorst-North.
(Jul 6, 2019)
We're here to discuss whether Agile ideas fit in with fixed-scope efforts. We'll look at Agile values, principles, frameworks, and practices. The answer is that Agile works just fine.
(Jun 17, 2019)
... to ScrumAlliance.org, Scrum.org, and the Scrum Community at large
(May 23, 2019)
I like to say that I may have invented story points, and if I did, I'm sorry now. Let's explore my current thinking on story points. At least one of us is interested in what I think.
(Apr 19, 2019)
There was a thread on Twitter talking about Agile being anti-management. No, it's much more radical than that.
(Apr 15, 2019)
Sprints, Iterations, Cadences, Continuous Flow. Planning sessions, daily scrums, retrospectives, increment reviews. Are these all, in the end, overhead to be eliminated along the way to some Agile Nirvana?
(Apr 13, 2019)
A couple of people asked me to list all the technical skills required in order to do Agile Software Development. I can't do that, but I can do this.
(Apr 2, 2019)
YAGNI can be a legitimate way to go fast at minimal cost. Skimping on the practices that support YAGNI? That's a mistake. Technical Debt? Not the same thing.
(Mar 31, 2019)
Some words and pictures about the various notions of 'technical debt', or, as I like to call it, wishful thinking.
(Mar 26, 2019)
A recent idea from an Organization That Should Know Better suggested that use of a standard story card format was a good idea. I tweeted 'wrong'. However, Chet and I talked about the subject a bit this morning.
Practices ]
(Mar 25, 2019)
Probably not a good thing to say. Possibly a good thing to think about.
(Mar 13, 2019)
A lovely post by GeePawHill led to a Twitter conversation about up front design, inspiring this article.
(Mar 11, 2019)
This is a small excerpt from The Nature of Software Development. It's a good reminder of some ways to think about value.
(Mar 4, 2019)
First some refactoring - then some behavior.
(Mar 4, 2019)
I decide to follow Braitenberg's approach a bit more closely, driving the wheels at different speeds rather than rotating the vehicle.
(Mar 4, 2019)
Let's Turn - making our little guy turn. And see the comments on Gross Hackery at the end of the article.
(Mar 4, 2019)
I'm playing in Codea with 'Braitenberg Vehicles', just for fun. I'll be sharing what I do with you all.
(Feb 28, 2019)
Scrum is founded in the belief that self-organizing teams can figure out what they need. When true, this is sometimes not sufficient. And sometimes, particularly in software development, it seems not to be true.
(Feb 27, 2019)
Let's talk about what responsibility we have for those who never take a course from us, read our books or web sites, or even see our tweets. I think we have rather a lot.
(Feb 26, 2019)
I wrote this in response to some tweets from an esteemed colleague, who I think is a bit less sensitive to dangerous ideas than I'd prefer our 'thought leaders' to be.
(Feb 21, 2019)
Another little tweet-storm about estimation. I think it's useful and not as easy to use as some people think it is.
(Nov 27, 2018)
Agile transformations have little, if anything, to do with Agile Software Development. Let me hook up some connections for you. Bit of a rant here ...
(Nov 26, 2018)
A short little thing that I tweeted recently. I think it's about transformation and 'Agile Leadership Training'.
(Nov 26, 2018)
Another tweet-storm, this one about slicing from top to bottom of the software. Slicing provides value, and information, sooner.
(Nov 3, 2018)
I was asked on Twitter what I meant when I said 'Simple, not easy. There's a difference.' I have no idea what I meant then, but here's what I think just now.
(Oct 26, 2018)
Are Imposition and Dark Agile both bad? Yes. Are they the same thing? No.
(Oct 7, 2018)
I tweeted about the SCOTUS situation. Seems I need to make myself more clear.
Social ]
(Sep 26, 2018)
Some early unfocused thoughts around original XP practices and what I might say today.
(Sep 17, 2018)
I'm not going to define a new framework, and don't think I should redefine XP, as it's not my baby. But I was thinking ...
(Aug 17, 2018)
I tweeted a storm about responsibility when 'Agile' doesn't go well. Here we'll unroll it and say a few more words.
(Jul 25, 2018)
Yesterday, I tweet-improvised the following thread. I had intended to write it up later as an article on my site, and here it is. It received a number of replies and comments, and I'll address some of those here as well.
(Jul 20, 2018)
There's a lot of whinging going on about imposing 'Agile' methods and practices. These whiners just don't know how to do imposition correctly. Me either, but here's what I'd try.
(Jul 19, 2018)
People have been telling me for years that Scrum is not an Agile Software Development Framework. I should have paid more attention. It's still good stuff, though.
(Jul 11, 2018)
A discussion of my personal values in the light of way too many 'well-reasoned' but mistaken notions on diversity.
(Jul 9, 2018)
A chapter from 'Software Development, How I'd do it'.
(Jun 24, 2018)
I'm writing a thing for GitHub Pages, so I decided to write a thing for GitHub Pages. Yaks all the way down!
(Jun 11, 2018)
Last night I had an interesting dream about files and folders ...
(May 10, 2018)
The above was the title of my talk with Chet Hendrickson at deliver:Agile. I'll update this with a link to the talk when it is published. Meanwhile, here are some thoughts.
(Apr 20, 2018)
I watch The Expanse to force myself to exercise. Today this quote hit me pretty hard.
(Apr 12, 2018)
Where do we place the responsibility–surely not blame–when things don't go well on a Scrum team? Who's responsible for taking action? (A bit of something I wrote on Twitter, lightly edited.)
(Apr 9, 2018)
You're probably wondering what I've said about estimates and the NoEstimates movement. Well, wonder no more. (bumped)
(Apr 6, 2018)
Just a few words about why I publish all these words, going over and over the same topics again and again, repeatedly and repetitively.
(Apr 6, 2018)
On the Agile Mentoring Slack group, Jack Caine and I were discussing what it means to be Agile. I wound up writing something like this, and wanted to share it more broadly.
(Apr 3, 2018)
I'm not finished ripping Scrum a new one, but I don't want to come off all negative. So let's talk a bit about what I'd like to see done.
(Apr 2, 2018)
We've spoken often before about the backlog. Let's get down and dirty today. Delenda est backlogus or something like that.
(Mar 29, 2018)
If your factory pollutes the river, you're supposed to clean it up. If you plant kudzu to combat erosion, you are responsible for its destruction of everything in its path. If you swallow a spider to catch the fly, and die when you swallow the horse, of course -- it's on you.
(Mar 28, 2018)
The Sprint causes serious problems in many Scrum installations. What are some ways to mitigate those problems?
(Mar 27, 2018)
Let's consider the Scrum Sprint. What's the strongest case we can make against it? It harms people, how's that for a case?
(Mar 27, 2018)
In the spirit of inquiry, fairness, and a generally bad attitude because it's raining, let's consider how strong a case we can make against Scrum. It might be fun.
(Mar 22, 2018)
These articles about hills to die on are in response to a continuing trope on Twitter and elsewhere, to the effect that X is bad, or Y is better than X, and therefore don't do X do Y. These are amusing, provocative, and rather frequently ... mistaken.
(Mar 21, 2018)
When are Sprints a good idea, when not so good? What are their values, and their costs?
(Mar 20, 2018)
Bashing of Scrum (and other methods) is a common form of Internet Entertainment, and not without reason. Some of the concerns are more accurate than others. Choose carefully which hill you want to die on. In this series we'll explore some hills.
(Feb 27, 2018)
To meet the deadline, all the software has to work on that day ...
(Jan 23, 2018)
There's a lot of noise going on on the Twitter just now, about starting with Scrum, with kanban, or with nothing. Here are some thoughts.
(Jan 19, 2018)
And what did you do with that iPad project?
Erors ]
(Oct 27, 2017)
We keep re-reading about the FTP object, and re-learning how it works. Then a week later, we've forgotten.
(Oct 19, 2017)
Last time we zeroed in on the FTP capability of our new cut at my 'iPad' project. Today, I'm hoping we'll TDD an FTP object.
(Oct 10, 2017)
Against all my best judgment, we decide to 'start over' on this tiny product.
(Oct 3, 2017)
We've not done work on this for ages. Tozier and I try to figure out what's up.
(Oct 2, 2017)
A blog on hiring for 'merit' has come across one of my input streams today, and I've decided to share a few thoughts on that subject.
Social ]
(Sep 26, 2017)
Some random thoughts on the times we are living through.
Social ]
(Sep 21, 2017)
Just a bit of reflection after two weeks off. Next week, I hope we'll actually do something. Today I remember the Boy Scout Refactoring Rule.
(Sep 8, 2017)
Responding to a mistaken TDD flowchart.
(Sep 7, 2017)
It has been a week since Tozier and I last worked, and I spent most of the time under repair. I'm thinking we'll work on the date-sensitive stuff. I'm mostly wrong.
(Sep 6, 2017)
Mike (GeePaw) Hill storified about sense of urgency and an acronym RAMPS. I like what he said and will muse upon it.
(Aug 29, 2017)
Chet has me nearly convinced to move my site base to Dropbox. Today we'll talk further about that and about moving the product forward.
(Aug 25, 2017)
I decide to spike a bit on folder and file manipulation.
(Aug 24, 2017)
When this article appears, it will have been processed by our new (MVP) iPad Transfer Mechanism. 'Thank you for pressing the self-destruct button.'
(Aug 23, 2017)
Tozier and I learned something about habitable code yesterday. Topics may include bits of Confirmation Bias and fragments of Coding Morality.
(Aug 17, 2017)
You'll meet them where they are. You'll work with them where they are. And when you leave, they'll still BE where they are.
(Aug 15, 2017)
I thought today we'd work on the triggering mechanism for the iPad build. Instead something important happened! (Clickbait)
(Aug 4, 2017)
I'm wondering, today, whether the Increment could be the driver for all 'Agile' software development.
(Aug 3, 2017)
If I were a REAL product owner, I'd be pressuring the hell out of my team right now. So I will. How did that work out, Ron?
(Aug 1, 2017)
We'll try to focus on building features today, but there are lurking issues in those magical incantations we do about Dir and FTP classes.
(Jul 31, 2017)
Today, let's talk about cadence. Iterations, Sprints, to have them or not, that is the question.
(Jul 28, 2017)
Thoughts about Technical Debt
(Jul 28, 2017)
Time to do some work after the heavy refactorings involving quantum mechanics. Let's see if we remember how.
(Jul 27, 2017)
I had the most amazing dream last night ...
(Jul 26, 2017)
I was asked a question about one of today's modern approaches to Agile software development. Here are some general thoughts.
(Jul 25, 2017)
In this short session, we inch forward and wind up in a better place. Not THAT better place. I just mean the code is better.
(Jul 20, 2017)
What's next for the iPad project? Refactoring, it turns out.
(Jul 13, 2017)
We knew last Thursday that we had an issue with folders and folder names. A week later, we dig back in.
(Jul 12, 2017)
An innocent email question leads me off into wildness and chaos. What's new with you?
(Jul 10, 2017)
In which a really fascinating little study piques our interest and suggests some thoughts. Please, I mean no harm here.
(Jul 6, 2017)
We really hope to get from end to end today. You won't believe what happens next. Unless you're paying attention.
(Jul 4, 2017)
Tozier and I shoot again for end to end on the iPad project. What happens next? As I write these words, I don't know either.
(Jun 30, 2017)
We're clearly closer than we were, and it feels very close. But not as close as we thought.
(Jun 28, 2017)
Bill and I decided to do a bit more on the iPad publication project. You won't believe what happened next. Unless you expect trouble.
(Jun 26, 2017)
What if I were to create a new software development framework? I'd never do that, but if I did, what might I do? Let's find out. Let's talk today about Whole Team.
(Jun 25, 2017)
Terms seem important to me today. (Revised 2017-07-05: Techniques)
(Jun 25, 2017)
Some Notes on the theme "If I were going to create a new framework, what would it be?".
(Jun 21, 2017)
A number of tweets and posts this week point out, correctly, that if we don't think about what we're doing, Scrum and Agile won't work. Apparently people need this reminder.
(Jun 20, 2017)
Today Tozier and I will do a Quick Design Session and start TDDing something that will, I hope, turn into the actual app.
(Jun 16, 2017)
In which we suddenly realize something about Tozier.
(Jun 15, 2017)
Tozier and I start with some Ruby code for FTP or something.
(Jun 14, 2017)
Tozier and I try some things.
(Jun 12, 2017)
A couple of things passed by my Twitter last week and I'll try to comment briefly on them. For values of 'briefly'.
(Jun 10, 2017)
I'm told the iPad is the new Mac, or something. Anyway, it'd be nice to be able to write articles on the iPad and get them on my web site without lugging around my Macbook.
(Jun 5, 2017)
Thoughts on the state of Scrum and Agile. Pressing harder isn't the point at all. Bit of a rant, really.
(May 25, 2017)
Some thoughts about kinds of people, kinds of words, and kinds of hair and clothing. We need to come together.
Social ]
(May 10, 2017)
If you're like me (as of last week) you haven't read this book. I recommend that you do so, right away.
(May 9, 2017)
I had an idea relating to my habit of 'Programming in Public' with all my mistakes, errors, bobbles, fumbles, and goofs showing. Why not write a book (again), with different languages and problems? Interested? Let me know.
Erors ]
(Apr 24, 2017)
Based on our Scrum Gathering 2017 talk, we discuss the impact on real software development of growing focus on the 'enterprise'.
(Feb 19, 2017)
I've been trying to learn a 3D drawing program. Yesterday I noticed that I was working but not learning.
(Oct 17, 2016)
Possibly not the best stance to take on, if you can manage it.
(Oct 5, 2016)
Time was, you got a spec, got browbeaten into saying you'd do it in 6 months, then got mostly left alone for 6 months. Now, they get to **** with you every ******* day!
(Sep 13, 2016)
Good frameworks are deep. Quick-entry courses sell well. It turns out they sell TOO well.
(Sep 8, 2016)
Scrum is good, when done as intended. Otherwise it can be oppressive and dangerous to developers. Let's study: Defense Against the Dark Arts of Scrum.
(Jul 9, 2016)
A twitter conversation got me thinking about the extent to which Agile ideas are intended to support small improvement, or to disrupt things.
(Jun 27, 2016)
Some interesting tweets make me wonder: if I were creating a method today, what would it be?
(Jun 24, 2016)
A foray into Google App Engine turns into a Tibetan adventure with Bos grunniens. No real lesson is learned.
(Jun 21, 2016)
Mike Vizdos and I are starting a new Slack team and we invite you to join us.
(May 27, 2016)
Over the past few days, an ancient twitter thread accidentally revived, talking about how you don't need quality code when you're just validating assumptions. What do the ants have to say about that?
(May 24, 2016)
Tozier and I did a little work on the ants experiment. Lessons are beginning to be learned.
(May 17, 2016)
Tozier posed an interesting problem today, and we decided to work on it at the coffee shop.
(Apr 21, 2016)
I found this picture of a roulette wheel. I wonder how hard it would be to make my little game use it.
(Apr 20, 2016)
Let's finish wiring up our second pass at Jim Jeffries' roulette example, and see what we can see.
(Apr 19, 2016)
I felt I owed it to myself to do Jim Jeffries' roulette exercise, this time with more tests. You won't believe what happened next. (Sorry, I have a click-bait virus.)
(Apr 18, 2016)
Jim Jeffries (no relation) proposed a TDD exercise / challenge. I took it on. The results may surprise you. (Sorry.)
(Mar 29, 2016)
Measure teams by metrics. Because that's how you get Crappy Agile!
(Dec 18, 2015)
I was asked a question via email and liked my answer enough to write it up. I hope you like it too.
(Dec 8, 2015)
Some twitter leftovers got me comparing Scrum and [Kk]anban. Are they Agile?
(Dec 6, 2015)
Some tweets inspire me to write a bit about management in Agile.
(Nov 27, 2015)
Going too far is quite difficult to do.
(Nov 25, 2015)
Bob Martin has published the Programmer's Oath. What do I think about that? The answer may surprise you.
(Nov 23, 2015)
Just some small thoughts bordering on rants. Something here for everyone to get mad about.
(Nov 12, 2015)
It's common to tweet things objecting to high automated test coverage as if it's irrelevant, incompetent, or stupid. I suggest otherwise with a thought experiment.
(Nov 9, 2015)
In which we discuss the technical debt metaphor, bright code, and the inevitable decline of civilization.
(Nov 5, 2015)
Mistakes, I've made a few [thousand], but then again too many to take personally. – not Frank Sinatra
(Nov 3, 2015)
A Twitter thread gets me thinking about Mock objects and whether they're more than just a matter of personal taste.
(Nov 2, 2015)
Let's try this again. The previous article was not clear to all readers. I suppose this is often the case with my work but in this case I thought I'd try again.
(Oct 30, 2015)
At the time of the Agile Manifesto, we all did the best we knew. Here's something I wish we had done. (Revised)
(Oct 18, 2015)
The Backlog is an essential artifact in Scrum. It may also be the root of serious dysfunction.
(Oct 12, 2015)
Generalizing from a few results isn't proof. In this article I'm going to prove that by generalizing from a few results. Wait, what?
(Oct 9, 2015)
Let's look at what Agile-focused individuals can do to improve their own lives, and, through interacting, help their colleagues and their organizations.
(Oct 8, 2015)
In a conversation about religion, I found myself saying something that makes me think about 'Agile'. Trigger warning: includes words like 'Christian'.
(Sep 28, 2015)
I've been a bit disappointed lately by the state of Scrum in companies, and rightly so. But there's another way to look at it.
(Sep 15, 2015)
Chet and I were talking about the importance of the Increment and the Sprint Goal. Herewith, some musings.
(Sep 11, 2015)
FiftyThree has released a new version of their excellent product, Paper™. Powerful changes. Bravely different.
Product ]
(Sep 8, 2015)
You have to either laugh or cry. -- Wm. M. Rogers
(Sep 1, 2015)
You people could help me by doing a better job and making fewer mistaks.
(Sep 1, 2015)
One great way to remove an impediment is to replace an old idea with one that's better. Let's give that new idea a new name.
(Aug 26, 2015)
Kate and Dan estimate a new project. Or do they?
(Aug 24, 2015)
I haz one.
(Aug 24, 2015)
The Estimate-Commitment relationship stands in opposition to collaboration. It supports conflict, not teamwork.
(Aug 22, 2015)
After a lot of email and blogging, Steve McConnell and I "Came out by the same door where in we went".
(Aug 18, 2015)
Semantics is important. Or is it 'are'?
(Aug 6, 2015)
Many individuals are creating new, marvelous, incredibly valuable Agile contributions. These were inspired by the Manifesto. They are not updates to the Manifesto, they're founded upon it.
(Aug 1, 2015)
In which we search for common ground and disputed ground.
(Jul 31, 2015)
Steve makes some great points. I think I'd make somewhat different ones.
(Jul 29, 2015)
If we can't build software well, all our Agile is for nothing.
(Jul 24, 2015)
A recent Twitter conversation bugged me (and bugged Clarke Ching even more). Here's why.
(Jul 22, 2015)
Privilege. No privilege. Screw it, improve your situation. Or don't. It's up to you.
(Jul 20, 2015)
OK, one more on this bowling thing: I decided I should do some tests.
(Jul 19, 2015)
Scoring bowling is Chet's and my go-to application for demonstrating pair programming and TDD. So here it is in Elixir, without either pairing or TDD. Interesting, though.
(Jul 16, 2015)
A report on building up a payroll pipeline. Twice. And still not entirely liking it.
(Jul 15, 2015)
Let's see whether we can sketch a little payroll. In Elixir. As the title suggests. Expect trouble - I do
(Jul 15, 2015)
It seems like time to experiment with something new. Will it be Elixir? Hold on, this is going to be chaotic.
(Jul 13, 2015)
Apparently the word 'estimates' is not clear. Here's what I mean and don't mean.
(Jul 11, 2015)
You keep using that word. I don't think it means what you think it means.
(Jul 9, 2015)
Slicing is easier and better than estimation for projecting done. And slicing adds value, while estimation does not!
(Jul 7, 2015)
That's all you need. You don't need no more.
(Jul 6, 2015)
A Twitter conversation got me thinking about how often teams or organizations fall away from their process, when it happens, and why.
(Jul 5, 2015)
Theory, Practice, Received Wisdom, Certification. These are not the things that make things work. Good people make things work.
(Jul 3, 2015)
Keep seeking better ways.
(Jul 2, 2015)
Deciding what kind of tests, and what tools, would be good for a payroll series, if I continue with it.
(Jul 1, 2015)
I love computers! Trying to set up Fitnesse and landing squarely on rspec.
(Jun 30, 2015)
Every minute we spend just thinking and talking, and not programming, is wasted!
(Jun 29, 2015)
Chet and I just ran an Agile Skills Workshop last week. It was great fun. We were asked for a description, and here it is.
(Jun 11, 2015)
Anger Considered Unproductive
Social ]
(Jun 7, 2015)
A brief um discussion about the Increment and how it might help you change culture.
(Apr 24, 2015)
I guess today I must write about the Scrum "Definition of Done", which is neither a definition, nor done. Is it a Scrum Artifact? I'd rather not.
(Apr 23, 2015)
Someone asked about comments on this site. I don't want comments on the site, but I am happy to discuss things, so I've set up a Google Groups forum. Here's some info about the forum.
(Apr 20, 2015)
I had occasion to look at a couple of articles from 2010, and things don't seem to have changed much. Should we be concerned?
(Apr 11, 2015)
Kate Oneal chats about testing with the Ann Arbor KALe Society.
(Apr 10, 2015)
All around us, Scrum and Agile are used, misused, and abused. How should we feel about that?
(Mar 29, 2015)
For success with Scrum, we need the basics, our expertise, and to improve our culture. To improve the culture, we need the Product Increment.
(Mar 27, 2015)
Development teams need help using the product increment as a center for making lives better. I resolve to work to fix that.
(Mar 27, 2015)
We're not blaming you when we say you're doing it wrong. We're trying to help you do it right.
(Mar 27, 2015)
We need to make Scrum and Agile safe for software developers. How should we proceed? (updated)
(Mar 25, 2015)
It's not up to Scrum or "Agile" or XP to make you successful or happy. It's on you.
(Mar 25, 2015)
We don't want just a "Product Owner". We want a Product Champion!
(Mar 23, 2015)
Impediments are there to be removed, not there to be recorded for posterity. Drive them out, don't log them in.
(Mar 22, 2015)
Historically, this was a category for shorter, more edgy articles. I might just bring it back into common use.
(Mar 16, 2015)
There's not much wrong with Scrum. Or is there? It depends what the meaning of 'wrong' is.
(Mar 16, 2015)
They shipped the software, therefore what they did was best. It ain't necessarily so.
(Mar 12, 2015)
Jonathan Rasmusson wrote an interesting article. I agree. It's not about unit tests. It's about skill and understanding.
(Mar 9, 2015)
Giles Bowkett invited me to discuss another article he wrote. For some reason I'm willing to do that.
(Mar 6, 2015)
The conversion from XProgramming.com to RonJeffries.com is essentially complete. Let's look at some learnings.
(Mar 2, 2015)
Many people assert that Scrum fails often. They say it's Scrum's fault. I'm still trying to understand.
(Mar 1, 2015)
Jeff Sutherland said today that it's not done if it's not tested. You won't believe what happened next!
(Feb 25, 2015)
My new book, The Nature of Software Development, has been released by Pragmatic Bookshelf. Check it out!
Nature ]
(Feb 24, 2015)
It is my practice to reconsider important topics. Certification certainly is such a topic. Here are today's thoughts.
(Feb 20, 2015)
Giles Bowkett has written some impassioned diatribes against Scrum on his blog. He raises some issues, which I shall try to discuss.
(Feb 13, 2015)
Content from XProgramming has been moved to this site. Some brief retrospective thoughts.
(Feb 8, 2015)
I was reminded by a lovely email of what happened during our SAFe training. Eliminate dependencies, don't document them or accommodate them.
(Jan 29, 2015)
Address given at the final meeting of the Agile Alliance, August 20__, by Ron Jeffries
(Jan 24, 2015)
As Tozier and I work on Scraper, I find the pairing to be quite difficult, though not unrewarding.
(Jan 20, 2015)
The Nature of Software Development will be released Real Soon Now. Pragmatic Bookshelf and I are looking for reviewers, who will receive a free copy. Inquire within.
Nature ]
(Jan 19, 2015)
Things will happen to us no matter what we do. That doesn't mean we can't influence what happens.
Social ]
(Jan 14, 2015)
Actions have consequences. It may be best to be OK with that.
(Jan 7, 2015)
Picking something stupid can break the log-jams.
(Jan 2, 2015)
A few thoughts in response to a discussion on the Scrum Development list.
(Dec 23, 2014)
Found the problem with Jekyll not auto-regenerating. No prize awarded.
jekyll ]
(Dec 22, 2014)
It's good to have people watching over me. Already got some feedback on this morning's article.
(Dec 22, 2014)
True to my word, for once, I'm learning RSpec. Follow along and laugh at my ignorance.
(Dec 18, 2014)
Coming soon to a bookstore near you!
Nature ]
(Dec 16, 2014)
top ]
(Dec 16, 2014)
A report on what's going on behind the scenes, with a bit of info on how we have built and used plugins and templates. Major errors within!
rj.com ]
(Dec 15, 2014)
Index of all site categories.
top ]
(Dec 13, 2014)
Here's what I've been reading lately. At least the ones I recommend.
reading ]
(Dec 8, 2014)
XProgramming will transition slowly over to ronjeffries.com. Be there or be square.
(Dec 6, 2014)
Channeling ELO. Also a Codea Diamond that you might find interesting.
(Dec 5, 2014)
A number of people have tried the Diamond Problem now. Let's look at their work and see what we learn.
(Dec 2, 2014)
This is the search page
top ]
(Nov 30, 2014)
The trouble with thinking is, you keep getting new ideas. I wanted to try this one. Turned out quite oddly.
(Nov 29, 2014)
Alistair Cockburn published an article about thinking in solving a problem with TDD. I'm all for thinking. Let's see how I do it. UPDATED.
(Nov 29, 2014)
Today is a big day for people tweeting how they deplore what other people are doing. Others retweet those tweets. I think that's a fruitless behavior and suggest something different.
(Nov 27, 2014)
Some questions come to mind about creating articles for a static site. In particular, what about trips with only an iPad?
rj.com ]
(Nov 26, 2014)
We come up with a block tag plug-in that lets us display most recent articles, sorted lists, and so on.
rj.com ]
(Nov 25, 2014)
We finally got some testing going on up in our house.
rj.com ]
(Nov 24, 2014)
Today we made some good progress, including a plugin!
rj.com ]
(Nov 24, 2014)
We've been working on the XProgramming replacement project since late September, so let's talk about estimation.
(Nov 23, 2014)
Doing simple things with Liquid templates is so awful it makes me want to ditch Jekylll just to get rid of Liquid.
rj.com ]
(Nov 22, 2014)
This is an NSFW rant regarding the whiny, mewling *bastards* who bitch, whine, and complain about Agile methods, Scrum, and similar topics.
(Nov 21, 2014)
A progress report, and some waffling. There's a lot of learning in a new project.
rj.com ]
(Nov 19, 2014)
Project Description as posted on github pages.
(Nov 17, 2014)
Progress report on the ongoing XProgramming rewrite.
rj.com ]
(Nov 16, 2014)
Report on working with page layout. Just notes.
rj.com ]
(Nov 2, 2014)
Martin Alaimo asked about the Manifesto Principle "The best architectures, requirements, and designs emerge from self-organizing teams."
(Oct 28, 2014)
Experience with Sinatra, and some thinking, cause us to look at a shift in approach. Martin Fowler was probably right.
(Oct 11, 2014)
Ignatz and Jmv38 on the Codea forums commented on the previous article. I had hoped to do more anyway so here's the next one.
(Oct 10, 2014)
Based on a simple example on the codea.io forums, I decided to write an article showing all the stuff I might do on a production calculator project. Wow.
(Oct 7, 2014)
Robin Dymond asked me to write about making stories small. Well, there's this.
(Sep 26, 2014)
A record of some of the stories for the system.
rj.com ]
(Sep 25, 2014)
Scrum top dogs announce combined site for Scrum definition.
(Sep 22, 2014)
Note on an issue with the new site. Odd formatting.
rj.com ]
(Sep 20, 2014)
A small progress report on the new site implementation.
(Sep 20, 2014)
XProgramming.com needs a new implementation. Want to watch?
(Sep 20, 2014)
XProgramming.com needs a new implementation. Want to watch?
(Sep 5, 2014)
Put makeup on your own pig, make it look as good as you can. Don't go around finding ugly imaginary pigs to stand it beside.
(Sep 4, 2014)
A report on the books, tools, and toys that have recently wandered through my life.
(Jul 30, 2014)
There has recently been a lot of noise on the lists, and questions at conferences, about putting refactoring "stories" on the backlog. Even if "technical debt" has grown up, this is invariably an inferior idea.
(Apr 2, 2014)
Recent Twitter conversations inspire me to pull out some of my concerns with SAFe and talk about them.
(Apr 1, 2014)
My friends and colleagues in the #NoEstimates circles have some good ideas, as I've commented elsewhere. I'm left, though, with a couple of concerns.
(Mar 27, 2014)
The Agile Manifesto says "Deliver working software frequently". Learn to do that. The rest will follow.
(Mar 5, 2014)
Kate's Gang chat about estimates, time, and cost.
(Feb 27, 2014)
I recently took the SAFe SPC training. My bottom line assessment is that it will be a marketing success, organizations trying it will see improvement, and some will see great improvement. And I don't like it.
(Dec 31, 2013)
Don't buy a brand. Seek out good ideas, and apply them to your situation.
(Oct 26, 2013)
The sky is blue on my planet. I live in the same real world you do, and have probably done so longer.
(Apr 29, 2013)
There’s a lot of interesting talk and thinking, going on under the heading of #NoEstimates. I think it's great, and I'm all for it. To do #NoEstimates, people will need some help ...
(Mar 27, 2013)
Robert Pirsig's protagonist "Phaedrus" said "Quality is what you like". We talk a lot about "value". My aim here is to suggest to you that value is what you like.
(Feb 25, 2013)
Are "manual" versus "automated" useful terms? As a matter of fact, yes, they are ...
(Feb 1, 2013)
Overcoming the Estimation Obsession
(Sep 5, 2012)
It's time to tell you a bit about the point of this little game we're working in.
(Aug 29, 2012)
In this episode, the code tells us to move toward a subordinate drawable object, the Polyline. We listen.
(Aug 25, 2012)
I'm starting to work on an application in Codea, a Lua system for the iPad. Here's the first spike.
(Oct 29, 2011)
Kate gives Dan Devlin, the company owner, an overview of Scrum.
(Jun 25, 2011)
Piers Thompson sent me a good question about my recent database articles. I suspect others would like to hear the question and answers.
(Jun 22, 2011)
Here's the current code, and some commentary, for the "But We Need a Database" article. UPDATED: Comments on Python style.
(Jun 20, 2011)
Last week Chet and I taught a delightful XP Experience class in Delaware. As often happens--where by often I mean always--the participants ran into trouble trying to apply Simple Design ideas when it came time for the system to demonstrate the ability to store and retrieve information. Let's talk about that.
(Jun 9, 2011)
Kate met Dan Devlin at the coffee shop on Main Street where he had originally recruited her. They shared the lovely weather and caught up to date on their lives. But Dan had a question.
(May 10, 2011)
Need a little help getting some data in and out of Second Life. World's most rudimentary scripting language, world's most ignorant scripter.
(May 10, 2011)
It is with some regret that I'm discontinuing my articles about J and about iLua on the iPad. Here's why. Also, I have a question.
(Feb 21, 2011)
I've downloaded the iLuaBox app for my iPad. This is a small but robust implementation of core Lua. Very interesting!
(Feb 21, 2011)
I did a bit more refinement on the Lua bowling example from last time. First, I package the rolls. Then a Frame appears!
(Feb 21, 2011)
A twitter pal has been working on bowling with a frame display notion, like at the bowling alley. Hmm ...
(Jan 12, 2011)
No, really. This is hard. People ask me why I'm doing it. There are reasons ...
(Jan 10, 2011)
Just recording random discoveries as I work through the EasyJ book. Read if all that interested in how I think ...
(Jan 8, 2011)
To do J, you must change the way you think. You must also learn many new words and other parts of speech. Working on part one today ...
(Jan 6, 2011)
J is doing strange things to my mind. I must report now, before my thoughts are too alien to communicate at all.
(Jan 4, 2011)
Chet and I are thinking of doing an app for iPhone / iPad. Can we do it on a shoestring? Advise us.
(Jan 3, 2011)
Alan Shalloway blogged on "Big Change Up Front", suggesting that it's not always the best thing to do. This made me think ...
(Dec 24, 2010)
"Why don't you believe in testing?" said Lanette Creamer, the Testy Redhead. Ah, but I do. I care about what, when, and at which end of the horse.
(Dec 12, 2010)
An odd anonymous article on "LearnTFS" purports to debunk Agile by moving closer to waterfall. Interesting, but not quite right.
(Dec 10, 2010)
I've had the privilege of observing He Jinbao, a martial arts master. He doesn't hurry. Maybe we shouldn't either.
(Dec 9, 2010)
Are there places where lower quality has less negative impact? Possibly. Except maybe on your soul.
(Dec 8, 2010)
No one I know can operate at their peak performance all the time. How do we know how hard to work on quality? Same way you get to Carnegie Hall.
(Dec 7, 2010)
You can always find someone to argue for cutting quality corners to "go faster". Is it possible to waste time cleaning code? Sure. Is it possible for code to be too clean? No.
(Dec 1, 2010)
Teams often want to write "technical stories" to cover things like testing and improving the design or infrastructure. There is rarely a need to do this. Here's why.
(Nov 6, 2010)
Alan Shalloway and I were tweeting about whether Scrum could be improved because it doesn't include some damn thing or other. Scrum is working as designed. We and the Alliance need to get to work.
(Oct 31, 2010)
Chet and I will be meeting with both the new and the outgoing Managing Director of the Scrum Alliance. I asked for input on Twitter, and have received some. Here, some thoughts.
(Oct 22, 2010)
Kate's team has noticed that their burn down chart shows trouble. The chart is right.
(Oct 20, 2010)
"Just tell us when you'll be done with all these requirements" is not how to guide an Agile project, be it Kanban, Scrum, or XP. Not remotely.
(Aug 27, 2010)
Some people have difficulty living up to the values and principles of the Agile Manifesto. Should we improve the Manifesto? Raise your game: we meant what we said.
(Aug 23, 2010)
At the Agile Developer Skills course at the Raikes School, I commented that we don't usually test accessors. But we test everything. Is this a contradiction?
(Aug 5, 2010)
Jon Bettinger has found a failing test! Excellent!
(Aug 4, 2010)
Philip Schwarz provided a nice-looking implementation. Let's look at it and try to build on his ideas.
(Aug 4, 2010)
My critiXXXXX advisors expected a more function-oriented solution. Here's something a bit better, perhaps ...
(Aug 3, 2010)
I've been working with Scala a bit, just to learn what it is. I've found it interesting, if frustrating. Here is a bowling experiment.
(Jul 28, 2010)
Just for something to do, I'm learning? Scala. Having deep confusion making JUnit suites run. Advise me in comments if you're up for it?
(Jul 15, 2010)
"His brand is bad: my brand is good." Isn't it well past time we got over that kind of thinking? I'll take a good idea from anywhere. So should you.
(Jul 13, 2010)
Should we ease into Agile, or jump in? How fond of being eaten by bears are you?
(Jun 29, 2010)
Let's consider two "dimensions" of a project, the extent to which it adheres to "Agile" values, and the extent to which it is an effective or successful project.
(Jun 10, 2010)
Susan said, “I can’t do it, Kate. No one could do it. There’s too much to do.” Kate paused until Susan seemed more steady. Then she said “Exactly. And that’s how we get done on time.”
(Apr 29, 2010)
Cut quality to go faster? It could happen. There's more to the story, however.
(Apr 14, 2010)
The thing about software development ...
(Apr 11, 2010)
There has recently been another discussion of Kanban on one of the Scrum lists. Kanban has some interesting ideas, and yet it seems to conflict with Scrum in some essential ways. The problem isn't Kanban: it's the notion of "essential ways".
(Apr 2, 2010)
It's time for the Scrum Alliance to stop using the C word, "Certified". It is holding us all back.
(Apr 1, 2010)
Chet Hendrickson
Some thoughts from Chet Hendrickson on the CSD program.
(Mar 31, 2010)
Why, anybody can have a brain. That's a very mediocre commodity. Every pusillanimous creature that crawls on the Earth or slinks through slimy seas has a brain. Back where I come from, we have universities, seats of great learning, where men go to become great thinkers. And when they come out, they think deep thoughts and with no more brains than you have! But they have one thing you haven't got - a diploma.
(Mar 22, 2010)
The Scrum Alliance is instituting a Certified Scrum Developer program (finally). Chet and I are involved. Here's why and how ...
(Mar 8, 2010)
Uncle Bob Martin comments on "Developer Certification WTF?" in a recent blog entry. Let's talk a bit about developer quality, and some things that are being done about it.
(Mar 6, 2010)
Choose your tools wisely, that they allow for the development of your skill.
(Mar 5, 2010)
Jim Shore has written a short item with the above title. Let's think about it a bit.
(Jan 4, 2010)
Author Matthew B. Crawford is a physicist, has a Ph.D. in political philosophy, and is a motorcycle mechanic. What's not to like? Recommended for practitioners, managers, executives.
(Jan 4, 2010)
After a failed iteration, the team regroups with a few new stories.
(Jan 4, 2010)
The team has fallen far short in the most recent iteration. What should they do?
(Dec 23, 2009)
There are essential practices in Scrum and Agile. Not because we say so. It's the nature of the beast.
(Dec 23, 2009)
Have all your desired features or make an exact date. What's so hard about that?
(Dec 21, 2009)
Agile projects very often seem to stall out after gaining perhaps twenty-five percent of the possible benefit. Why is this? What can be done?
(Dec 16, 2009)
Incremental and iterative development processes provide frequent opportunities for teams to "Inspect and Adapt". What should we inspect? How should we adapt? Is this part of the process?
(Oct 2, 2009)
I just thought I'd make a page with links that may be worth exploring. If you have some, let me know. I have not explored all of these, nor, probably, have you. That's why I'm listing them.
(Oct 2, 2009)
Here are a few links relating to collocation, thanks to Adrian Howard and others.
(Sep 10, 2009)
Scrum luminaries freely grant the necessity for good developer practices, and the Scrum Alliance is thinking about developer certification. Some important people in the community are involved, and so am I. Read on ...
(Sep 8, 2009)
There has been some discussion of late regarding the use of Test-Driven Development ideas in non-software areas. This is a really good idea and I would like to talk about it here.
(Sep 8, 2009)
When terms like Agile or Scrum or TDD get watered down, everyone loses.
(Jul 13, 2009)
(Jun 19, 2009)
Susan Prior drops in on Kate to talk about some new products she would like developed.
(Jun 16, 2009)
A pizza of radius z and thickness a has volume pi*z*z*a. That is all.
(Jun 13, 2009)
We humans like to take a very soft cloud of ideas and give it a name, and then to insist on how good our Named Cloud is compared to some other Named Cloud.
(May 31, 2009)
What should an iterative-Agile team do if it appears that not all the stories they signed up for will get done? Is Kanban the answer?
(May 28, 2009)
OK, let's talk about when to automate tests for the ten thousandth time. I'm patient, in a manner of speaking. I can keep doing this until you get it.
(May 22, 2009)
Scrum's job ends with the problem. Your job begins with the problem.
(May 20, 2009)
I don't believe this quite as much as I did when I wrote it. How about you?
(May 7, 2009)
Anything as hokey as this title needs to be preserved. Really.
(Apr 26, 2009)
(Apr 25, 2009)
(Apr 13, 2009)
(Apr 13, 2009)
(Apr 13, 2009)
(Mar 24, 2009)
You XP guys advocate testing, not inspections or program proofs. Everyone knows that testing can only show that errors exist, not that they don't.
(Mar 24, 2009)
We recently got some questions about the story "We'll Try". Send us your questions! The article assumes that the deadline is fixed and that the client should trade off the project objectives. It seems to ignore the possibility that there are other things the client might want to trade off such as cost and deadline or more complex issues like aspects of quality such as maintainability, flexibility, reliability, usability, etc.
(Mar 24, 2009)
We have Worst Things First, which tells us what to worry about. On the other hand, our division of responsibilities tells us that the customer decides which stories to work on. Does WTF only apply within the particular story we have in hand now, or do we somehow exercise programmer forethought in deciding what we need to worry about?
(Mar 24, 2009)
The Distributed Computing link lets you get a copy of the C3 team's famous article in Distributed Computing.
(Mar 24, 2009)
Article by Kent Beck and Dave Cleal offering an alternative to fixed-price contracts.
(Mar 24, 2009)
(Mar 24, 2009)
(Mar 24, 2009)
(Mar 24, 2009)
A very experienced QA manager recently emailed me some tough questions. Here they are, with are my answers. As always, comments and further questions are welcome!
(Mar 23, 2009)
(Mar 23, 2009)
Here, in order, are the online chapters of Annals of Kate Oneal
(Feb 19, 2009)
Ward Cunningham posted a video on Technical Debt, and Kent Beck and Ed Yourdon (and I) have been tweeting about it. Let me share some thoughts with you here.
(Feb 17, 2009)
Bad product? Bad customer service? Don't care.
(Feb 6, 2009)
In order to do Scrum or XP or any form of Agile successfully, you must refactor. Sorry, not optional. Necessary.
(Feb 4, 2009)
Let's talk about more about code improvement. Some people seem to think that code improvement has a high associated cost. I think it only has a high cost if we're not very good at it.
(Feb 4, 2009)
The traditional CSM course is only two days. That's not enough time to cover the things a ScrumMaster needs to know to help their team be successful.
(Feb 2, 2009)
Many teams seem to get in trouble because they do not have good technical practices. In Scrum terms, they can't get "Done". Is Scrum flawed because these teams do not "discover" such practices?
(Feb 1, 2009)
Some people think that there is a necessary trade-off between internal code quality, and getting things done rapidly. I believe they are quite mistaken.
(Jan 30, 2009)
The amount of context focus is too damn high!
(Jan 28, 2009)
Let's talk about the importance of pair programming.
(Jan 15, 2009)
How many times do I have to tell you this???
(Sep 22, 2008)
The statement means "I cannot refute your foolish and unrealistic argument but I don't intend to change my mind."
(Sep 22, 2008)
On the leandevelopment list, there has been a bit of a discussion on how long the "backlog" should be, and why.
(Sep 18, 2008)
Pressure only works if I get them done: otherwise it just frustrates me, makes me feel bad, makes me slower still.
(Sep 17, 2008)
When we make decisions based on any kind of "true faith" approach, be it religion, Waterfall, or Agile Zealotry, we know we are right. If things don't work out as we hoped, it's not our fault.
(Sep 17, 2008)
Some thoughts on always carrying a throw-down duck.
(Sep 2, 2008)
Burn stories, not tasks. Don't do tasks. Do stories.
(Aug 26, 2008)
Is a call for more principle behavior going to improve our performance? Frankly, I have my doubts.
(Aug 1, 2008)
As my old friend Charles Bair used to say, that's a two-part question. "How?" and "should user stories be written?" The answer to the second question is "No, not really."
(Jul 7, 2008)
Code that slows us down is bad design.
(Jul 3, 2008)
There's nothing like a bean counter when it comes to improving your shopping experience.
(Jul 2, 2008)
Test-Driven Development checks intention. Customer Acceptance Tests check desire.
(Jun 30, 2008)
Scrum works, when it does, because you do just two things.
(Jun 29, 2008)
A link to a gem of an article.
(Jun 28, 2008)
Michael Feathers asks: Are nested classes really a good idea?
(Jun 11, 2008)
Recent discussions on the lists inspire me to take a radical position. Or maybe it's my life. Or an accident of birth. Anyway: Agile Software Development requires software development.
(Apr 25, 2008)
MUCH LATER: Organizations certainly need good productivity. Sometimes they ask for improved productivity, and a way to show that we have improved. Is this always evil?
(Apr 24, 2008)
Carl is concerned about small releases, and catches Kate in the coffee room. They talk about why small releases matter to Kate, and they both learn a bit.
(Apr 21, 2008)
(Mar 28, 2008)
After Dan Devlin, President of Oak River Software, dropped in on her at the coffee shop, Kate agreed to consider helping with the proposed new Empire project. Empire was life or death for Oak River. Without Empire, they'd go under, and Dan couldn't afford to fund it.
(Mar 27, 2008)
The forum was set up as an experiment to see whether a self-sustaining forum-style site would work. This one, at least, has not. With regret, I'm shutting it down.
(Mar 1, 2008)
"Kate" puts a word in about how things really got started, and promises to come back and sort Ron out if he needs it.
(Jan 3, 2008)
(Dec 21, 2007)
Chet and I have decided that the thing to do is to build the software page using full-on Ruby generators and get it out of the way. Here we go again. This doesn't turn out at all as we expected. Project cancelled! Has XP failed???
(Nov 19, 2007)
We review cards and letters, and we finish our first elementary story. We think we will start over. Oh, and my computer is now fast again. Read on ...
(Nov 13, 2007)
We start on the first story, but get into some trouble with my machine. And you're probably wondering what we're actually up to anyway ... take a look!
(Nov 12, 2007)
We take a few moments to write stories and talk about what should be done. Who says we don't plan?
(Nov 5, 2007)
After a long hiatus, we're back! We're tired of Java and C# and decided to do something with Ruby on Rails. Come along for the train ride. Or wreck, as the case may be.
(Jun 14, 2007)
With a little time on our hands, we make our sketched story run and smooth out the code. Generality is showing up, almost by magic. Except it isn't magic -- you can do it too!
(Jun 12, 2007)
We move forward incrementally, improving the report generation by adding new paragraphs, observing missing ideas, and removing duplication. Could that be all there is to this? Is "all" a good word in that question?
(Jun 11, 2007)
In which our intrepid heroes leap fearlessly directly into a flaming pot of YAGNI. Will they surface? Will they be fried?
(Jun 7, 2007)
Our tests run, the code structure is good, yet we are not entirely happy. What's up with that?
(Jun 5, 2007)
Distracted by the Style and Grace planning and other things, Chet and Ron have been away from the Shotgun project for a while. They need to reload their minds and get back to it. Will our heroes prevail? You know they will.
(May 5, 2007)
After a lot of reflection on how things are proceeding in our favorite software community, Chet and Ron have decided to hold a public workshop to share and practice building software in teams, with an eye to helping all the attendees ... including ourselves ... sharpen software and team skills.
(Feb 2, 2007)
With great courage and at great personal risk, Chet and Ron attempt a new world's record in high-altitude pair programming.
(Jan 24, 2007)
We've been working for a couple of weeks of elapsed time now, we figure, so it's time to focus a bit more on end to end. How about a draft PDF report?
(Jan 23, 2007)
When we went to the unit square implementation of PatterningSheet and ShotPattern, we stopped after the FitNesse tests ran, but before we modified our image-drawing spikes. Here, we complete that implementation and clean up the code as we do it.
(Jan 15, 2007)
We get all the tests running after scaling to the unit square, and clean up the code substantially. Full listings in this issue, so stand back when you open the page.
(Jan 9, 2007)
A few more notes from our friends, and a solo pass over the code. Redneck's last words? "Watch this!"
(Jan 8, 2007)
Last time, we jammed our new density code into the system, adding some incompatible methods and values. Today we're going to begin to smooth out that code to get the design back closer to good. Will we succeed, or fall on our faces?
(Jan 5, 2007)
A little experiment for confidence, and we make our Customer's Density test complete, and make it pass. The world does not come to an end. (Updated: a remark on time.)
(Jan 4, 2007)
Much less effort, a step toward perfection. And perhaps we know why ...
(Jan 4, 2007)
We draw some density pictures, improve some code, and recognize at least some of our flaws.
(Jan 3, 2007)
Chet and I get together for the first time in 2007, to some useful effect. Also I try to provide a bit more insight into what we're doing, and not doing, and why.
(Jan 3, 2007)
Today's plan was to write the acceptance test for another story, and make it run. The best-laid plans ...
(Jan 1, 2007)
Here's the call for participation for the Agile2007 conference, August 13-17, 2007, in Washington, DC.
(Dec 30, 2006)
I was reading some interesting stuff on Andy Hunt's blog, and as it was 6 AM and I had nothing else to do, I took this test ..
(Dec 23, 2006)
There has been some interesting discussion of image processing ideas and such on the lists, owing to our discovery that the paper has some 1500 holes, and the picture only about half as many visible strikes. Here are some of the pictures, and some thoughts on what we're about.
(Dec 22, 2006)
All right, already! We break down and draw a visible picture, mostly because I wanted Chet to share in the discovery and I knew I couldn't hold off over the holidays. It looks cool. Does it tell us anything?
(Dec 21, 2006)
We combine the PatterningSheet into ShotPattern, and discuss the effects of doing so.
(Dec 20, 2006)
Today we think we'll work on consolidating pixels into actual hits, or an approximation thereof. Join us at Borders. If nothing else, you'll see a prodigious 18 minute spewing of code.
(Dec 17, 2006)
On the plane to Florida, I got an idea for how to clump adjacent pixels to represent a single hit. Apres moi, le rat hole. Here's a report ...
(Dec 9, 2006)
A new low! We're taken to task for thinking in our free time! I attempt an explanation, and add some random thoughts. Quelle surprise!
(Dec 8, 2006)
We've agreed to do this project the way that we think projects should be done, and that includes Acceptance tests. Today we'll try for the first one.
(Dec 6, 2006)
I have the day off, and I drew a nice picture for the previous article, so I decided to work on a spike for Chet's radial pattern density chart. Let's find out what happens.
(Dec 6, 2006)
We've been working for almost two full days now, and it seemed time to refine some stories. We found some conflicts between ourselves as programmers, ourselves as customers, and ourselves as advisors to projects
(Dec 4, 2006)
We've been spiking long enough to learn some key things, and it'll soon be time to create better stories and estimate them. Today we finish up the spike on density and learn a few things about those libraries everyone thinks we should use.
(Dec 3, 2006)
Input from a few readers, and our initial estimates for the shooting project.
(Dec 3, 2006)
Our first spike took a bit longer than we had hoped, but we successfully interpreted a BMP file. We worked to improve our code, while people wrote to us to tell us how ignorant we are. Fun all around.
(Nov 29, 2006)
While we wait for the estimates to come rolling in, and before I forget, here's a report on our work so far on the Shot Pattern Analysis program.
(Nov 28, 2006)
Estimation, simplicity, TDD, tracking. Chet and Ron undertake a project a bit larger than their usual run, to see what happens.
(Nov 16, 2006)
The Frame object in our Haskell-inspired Java program has an awkward interface. Let's take a look at it and see what can be done.
(Nov 15, 2006)
Let's proceed with making the Haskell-inspired Java version "better", focusing on writing tests for a new Frame object. The code gets odd, but turns out better after a while ...
(Nov 7, 2006)
The Haskell experiment we did at the Simple Design and Testing conference has led to some questions and some answers. I'd like to discuss some of them here, and start in a slightly different direction based on the learning.
(Nov 5, 2006)
The continuing saga of recursive implementations of Bowling, email from our fans, and a refactoring of my Java code.
(Nov 4, 2006)
Lots of fine feedback on the Haskell article. Alternative implementations in Java, Ruby, and even Haskell! Much fun! PLUS!! FATAL FLAW DISCOVERED IN RECURSIVE VERSIONS!!
(Nov 1, 2006)
At the Simple Design and Testing conference, Dan Mead bravely agreed to implement the infamous Bowling Game exercise, TDD style, in Haskell. It was fun and interesting. Here I present some discussion, his program, and a Java program in a similar style.
(Oct 20, 2006)
Dogbert teaches us all a management lesson. He's even offering a diploma. Is that better than a certificate?
(Oct 4, 2006)
During our Agile Experience session with a client a couple of weeks ago, Chet and I were helping them with FitNesse for .NET. We thought it would be interesting to get FitNesse working with Ruby, so we've begun to work on that. Here, the results of that trial ... Now! With new explanations and graphics! See the end of the article.
(Sep 8, 2006)
On a few of the Agile lists, Paul Arrowood asked: "How does Agile address a conventional Risk Log? I wouldn't call these 'blocked items' (aka issues). But more or less the [Scrum Master's?] watch list for things that could go awry (content not fabricated, new/unfamiliar technology, geographically dispersed team, interdependence with another project, etc)." I wrote an answer, and liked it well enough to put it here.
(Sep 4, 2006)
It is my pleasure to offer the Agile community a new resource, an Agile Forum. I'm hoping it will be a brand-neutral, consultant-neutral place, open to and shared by everyone who is interested in advancing him- or herself in Agile, or in bringing Agile to the world. I'm inviting you to help make it a place you'd like to be.
(Jul 13, 2006)
The code is beginning to ask for some help. We're processing a simple array of cells instead of an object, and the classes don't feel cohesive. Let's push some methods off to new classes and see what happens.
(Jul 9, 2006)
I've read a bit more about Sudoku, and even played part of a game. Plus, the ideas of others in the lists and in email have me thinking. Should I try some of these ideas ... or not? UPDATED: My strategy conclusion is wrong!
(Jul 8, 2006)
A little more explanation of what I'm up to, and a test of a method that actually figures out what could go in a cell. Whee!
(Jul 7, 2006)
A number of people on the tdd list have reported having a lot of fun TDD programming the game of Sudoku. I've not played the game, though of course I've tripped over the piles of books in the bookstores and at the airport. But discussion of the thing makes it sound like it might be fun to TDD on it, as people are saying. Let's get started.
(Jun 11, 2006)
The program reached an impossible state during the first test of the algorithm that I turned loose. I thought I had made a mistake, but it turned out I had not. Well, not a coding mistake.
(Jun 4, 2006)
A comment from Alan Shalloway, on the Lean Development group, points the way to fame and fortune!
(May 25, 2006)
Sure, test automation is a good thing. But we can't, and shouldn't, automate them all. Why then, ask people to "automate all tests"?
(May 3, 2006)
June Kim posted a J Language version of bowling that is very vector-oriented. As an experiment, I coded up a vector-style version in Ruby, TDD of course. It turned out to be kind of interesting.
(May 2, 2006)
An allegory? Sarcasm? Humorous pastiche? You decide.
(Apr 29, 2006)
Justin Gehtland, Ben Galbraith, and Dion Almaer bring us a valuable and enjoyable book describing Ajax. It is full of running examples, points out the major gotchas, and it's a good read too! Recommended!
(Apr 22, 2006)
Between the new book review page and a few other things, I just spent a few days in a painful, test-free update of my web site scripts. Here, a report on how much it hurt. Lessons learned? We'll have to see what I do. Like lots of folks I know, I haven't figured out how to do what I know I should.
(Apr 17, 2006)
Scott and Pramod have done an excellent job with this book. It's full of practical advice about how to improve your database design, when to do it, and even how to manage the transitions. If your project involves a database, this book can help.
(Apr 14, 2006)
More features will always bring more revenue, more customer satisfaction, other good things. Therefore there is always pressure for people to work harder, longer hours. This is demonstrably a Bad Idea. Here's some evidence, and some ideas about how to know if pressure is too high.
(Mar 26, 2006)
On the agile-testing group, there has been a little discussion about offshore testing. Herewith, some thoughts, cleaned up slightly from my comments there.
(Mar 16, 2006)
I was glancing at the delegates version of the code last night, and I have the impression that the frame status requirement will be more readily implemented there. So today we give that a try. The results are strikingly better than yesterday's!
(Mar 15, 2006)
Today we set out to finish the essentials of the FrameStatus implementation for the Kicker version of the Bowling Game. Things go in easily, without many surprises. But we have a lot of code, and it doesn't all feel good.
(Mar 14, 2006)
We have a very procedural implementation of the bowling game, and a very nifty OO version with classes representing states of a state machine. Which implementation is more responsive to new requirements? We'll find out soon!
(Mar 13, 2006)
We use the C# "delegate" feature to come up with a solution to the Bowling problem that is perhaps a bit less OO, but is also only 40 percent the size of the version with the Kicker classes. Fun exercise, but the proof will be in the next stories. [updated, see footnote]
(Mar 12, 2006)
I wrote this answer in response to a question on one of the Yahoo groups: "What is the list of documents produced when you are implementing a pure Agile project?" Martine Devos liked it, so I decided to preserve it here in hopes that someone else might like it as well.
(Mar 10, 2006)
We build some superclasses to remove the duplication from the Kicker classes. One false start sends us down an unpleasant path, and we decide to start over more cleverly. As for the end result, we have our doubts. The proof will be in the updating, later on. Right now, it's hard to see why five times bigger is better, just because it looks like Object-Oriented.
(Mar 9, 2006)
Chet and I get this version running all the way, by implementing the Strike functionality. We do some cleanup, and plan next steps. We can get a pretty good look at the OO-style version of bowling. Is it better? It's not clear.
(Mar 8, 2006)
In which our heros find a straightforward way to replace conditional logic in the Frame with series of Kicker objects. The design so far is quite "object oriented", and is turning out as was envisioned. But is it better? That remains to be seen.
(Mar 7, 2006)
Using a pinball "kicker" metaphor, Chet and I are going to try a version of the Bowling Game. We'll talk about the metaphor a bit, and then check our intuition that it will work out well.
(Mar 6, 2006)
A TDD demonstration of the Bowling Game suggested that there is material there worth mining. Let's start digging.
(Feb 23, 2006)
A poster to the CrystalClear list offered a classification of Agile methods, triggering these brief thoughts about integrating the ideas rather than dividing them.
(Feb 23, 2006)
Recently on the Scrum list, I characterized the practice of having designated "QA" people on the team as a "second- or third-class practice." Here's some expansion on that ...
(Dec 13, 2005)
The ScopeTransform experiment was a good one, but I think that scope transformation should be part of XSet, not a separate operation. We'll work on that ... and it turns out pretty nicely. More to do, of course, and things are a bit fuzzy, but I think we're on a good path.
(Dec 12, 2005)
Our previous work left me thinking about whether there would be lots of redundant Scope Transform bytes needed in all the records. I chatted with Chet about it, and thought about it a bit more, and I think we're OK. This article will bring you up to date on the thinking. No new code, but I will include the complete listings as of now just to keep you up to speed.
(Dec 9, 2005)
We're walking a narrow path bounded by theory and practice. This time we'll do some work on those records with holes in them, like the first-name set. In so doing, we'll try not just to hack in the code, but to keep it consistent with our understanding of the math. We don't really understand the requirements, or the theory. Can we possibly succeed?
(Dec 4, 2005)
We'll push forward with Scope Transformation ideas. First step will be to make the :restrict operation return a ScopeTransform set. That part will be easy. Then we start thinking about just what that :contents method means. Still, good progress for a little time in an airplane.
(Dec 3, 2005)
We need to look around a bit, to decide where to take this project. To do so, we need to get a bit more clarity on the big picture, and the small one.
(Nov 30, 2005)
Some cleanup efforts lead us to a theoretical idea, and to a successful spike. Out of chaos, order.
(Nov 28, 2005)
There's this hack where we return the elements of a set as if they were sets. Nothing like theory to fix a hack, is there? Naturally there are some stumbles along the way, mostly involving the tests. Remember who you're dealing with.
(Nov 25, 2005)
I did an offline experiment to figure out what to do about this :each thing that returns two items instead of the usual one. Based on that, we'll create a new little object, wire it in, then clean up the tests a bit. Join us ...
(Nov 23, 2005)
Just for a little something to do, let's add iteration capability to our XSets. [Added: Clarification of something that threw at least one reader off.]
(Nov 20, 2005)
A small experiment, implementing "restrict" in Ruby. As usual, warts and all.
(Nov 19, 2005)
Some friendly folks have been making suggestions and asking questions. I'm still in the mode of figuring out what to do and how to do it. For those who are interested ...
(Nov 17, 2005)
For some reason, I'm thinking -- at 2 AM -- about Extended Set Theory. An interesting topic, to me, even at this hour. But should I build something? I don't know; help me out.
(Nov 10, 2005)
It seems like every development project begins with the date, and we're held responsible for "making the date". Making the date is a management responsibility, not a development responsibility. Here's why.
(Oct 21, 2005)
Delivery of the running, tested, features the customer wants is the purpose of the development team. Sometimes the work we signed up for won't quite fit into the iteration. What should we do?
(Aug 6, 2005)
Chet and I got together at Borders in Brighton yesterday, and talked about teams going "off the road" and what a process should do to address this concern. We recorded the chat and have put it up as a sort of podcast. We hope you enjoy it, and request your help.
(Jul 29, 2005)
There's a recent thread on the Scrum list about how an executive or highly-placed manager could get Agile going. I've been one of those guys, and I know a bit about Agile, and here's how I'd proceed. First, focus management attention on cyclic delivery of running tested software. Second, provide the resources to learn how to do that.
(Feb 24, 2005)
Chet Hendrickson
Ron and I have been doing some Smalltalk lately. He has been writing about coding the bowling game as an exercise to help get our chops back, so I thought I should do something to help us catch up with the current state of Smalltalk development.
(Jan 16, 2005)
To really take an important role in practice, ideas need to get built into people's heads. Since most practitioners don't read much, they get most of their ideas from people they talk to, things they can read quickly, and most of all, from ... practice.
(Jan 15, 2005)
Our mission, should we choose to accept it, is to "spike" a map drawing program. We know nothing about maps or drawing, and very little about programming. How might we proceed?
(Jan 2, 2005)
Harald Mueller and I have been having a little mailing list debate about documentation. I've been taking the position that we want understanding, not documents. He's been saying that documents are one good way to get understanding. So far, we haven't gotten on the "same page" yet, but I trust that we will if we keep going. In the light of that conversation, though, here are some thoughts on documenting this little product we're working on.
(Dec 28, 2004)
These questions were recently asked on the XP group, in the context of a review of Mike Cohn's User Stories Applied. The answers are a function of the whole project, not just User Stories.
(Dec 27, 2004)
Based on a suggestion, I'm going to build the BowlingGame in yet another way: based on a Stream concept. This will be more fun for me than what I should be doing: I hope it's the same for you.
(Dec 25, 2004)
A famous author also refreshing his Smalltalk proposes a single method solution. Going where no man dares to tread, I'm going to try to refactor it into the style I consider to be "good". You decide.
(Dec 22, 2004)
I had this cool idea for another way for Bowling to work. I'm snowed in, so I tried it. The results were good ... and very thought-provoking.
(Dec 22, 2004)
Some discussion of style triggered by reader input. Then on to another "improvement", followed by discussion of whether it's an improvement, and why we did it.
(Dec 21, 2004)
Let's try some more incremental improvement to the objects. Meanwhile, some people think I'm taking bites that are too big. Let's think about that as well.
(Dec 20, 2004)
Let's reflect a bit on the Smalltalk bowling experiment so far. And then ... I've got an idea!
(Dec 19, 2004)
In the previous article, we made our first test run, and sketched a bit about how Smalltalk helps us. Let's make some more tests run.
(Dec 19, 2004)
After a long time away, I had occasion to start using Smalltalk again. To get my chops back, I started with the Bowling Game exercise. My experience quickly reminded me why Smalltalk rocks. (Updated: includes changes and remarks about "==" vs "=".)
(Dec 7, 2004)
(Oct 27, 2004)
To paraphrase Red Green, if the audience doesn't find you informative, they should at least find you entertaining. Chet and I addressed the XP West Michigan group recently, and here's an article from the Grand Rapids Business Journal that resulted.
(Oct 20, 2004)
It's time to revisit the topic of Big Visible Charts. Display important project information not in some formal way, not on the web, not in PowerPoint, but in charts on the wall that no one can miss. [Updated: Velocity Charts]
(Oct 4, 2004)
Brian Marick, in a blog entry that is quite interesting on its own, points to a very provocative article about group think, German philosophy, and the old Saturday Night Live gang. It got me thinking about Extreme Programming and the "Agile" methods. Have I mentioned passion lately?
(Oct 1, 2004)
I was wondering what would happen if I injected a Frame object into the bowling example, early on. What happened is that I got in a bit over my head. Come along and point and laugh.
(Sep 24, 2004)
It's important to take grammar seriously, even if she has been dead for years.
(Sep 21, 2004)
To every Card, turn turn turn, there is a season, turn turn turn, and a time for every Suit under heaven. It's not the Suits, it's the Game.
(Sep 19, 2004)
Programming can't be successful without design. But I begin my projects with very little design and seem never to do any. On the contrary, I'm designing all the time. That's what makes incremental delivery possible.
(Sep 19, 2004)
We need a test. We discuss why we work that way, then we write the test and make it run. In so doing, we learn something very important: maybe we don't want ArticleList to be a typed collection after all!
(Sep 17, 2004)
Inspired by an example from Jonathan Pierce, I typed in a walkthrough of the .NET CollectionBase, a base class used for building typed collections. Chet and I talked about it at Borders today, and it inspired us to look at the ArticleList in the blog software. We tweaked it to make it more like a typed collection, and it's definitely better.
(Sep 14, 2004)
In which we set out to drain the swamp, encounter some alligators, and quite possibly add a little water to the swamp in the process.
(Sep 7, 2004)
I've got a little time here, and there are those tests set to Ignore. Let's fix them so we don't have to ignore them.
(Sep 6, 2004)
Inch by inch, step by step, we work on improving the internals of the ArticleFiler. No master plan, no grand design. Just gently polishing until the object is visibly better. A good way to proceed? You decide.
(Sep 5, 2004)
When I'm programming, I work very incrementally, almost intentionally with no grand plan other than my stories. I pay attention to the design, but I'm not working toward a planned design. When the code starts pushing back, I make it better. This feels to me like a course of discovery rather than bringing about some carefully thought out transformation.
(Aug 23, 2004)
This book includes some really excellent examples of pair programming sessions with XP superstars such as Chet Hendrickson and Paul Friedman. Author Ron Jeffries has chosen some great partners. It's too bad they couldn't be with him more often. (New note inside review.)
(Jun 14, 2004)
Nearly every metric can be perverted, since up- and down-ticks in the metric can come from good or bad causes. Teams driven by metrics often game the metrics rather than deliver useful software. Ask the team to deliver and measure Running Tested Features, week in and week out, over the course of the entire project. Keeping this single metric looking good demands that a team become both agile and productive.
(Apr 12, 2004)
The irony of Extreme Programming is that while detractors continue to explain why it cannot work, software developers all over the world are having success with it.
(Jan 19, 2004)
Bill Bryson writes a delicious book that lives up to its title. The cosmos, the earth, atoms, geology, life, homo sapiens -- it's all here.
(Jan 15, 2004)
And thirdly, the Code is more what you'd call guidelines than actual rules. -- Captain Barbossa (Pirates of the Caribbean)
(Nov 20, 2003)
Object aficionados worldwide are concerned that the procedural bowling solution presented last time is just not robust enough. They want to see how we would make it score the frames incrementally. Frankly I haven't the slightest idea.
(Nov 18, 2003)
Here's the Bowling Game again. This time I'll take a simpler approach, along the lines I usually follow when I do a Test-Driven Development demonstration. The result is strikingly simpler than the preceding 'object-oriented' solution. What does this tell us about TDD and how to use it?
(Nov 17, 2003)
TDD on the Bowling Game (article lost and now found again)
(Sep 11, 2003)
I can put off anything except procrastination. When I make a "ToDo" list, a card is too small and they get all bent and dirty before everything is done. Wait! I'm an XP guy. I'm trying separate "ToDo Story Cards" to see what happens.
(Sep 10, 2003)
This isn't just one of those self-improvement books. It asks us to dig deeply into our own feelings about people and situations. Reading this with an open mind will ask some hard questions that need answers.
(Sep 5, 2003)
This book is painful to read for anyone who understands what XP is, because it goes to such pains not to understand, to take out of context, and to distort. It is dangerous to read for anyone who does not understand what XP is, because it goes to such pains not to understand, to take out of context, and to distort.
(Sep 4, 2003)
Beta testing is a common final check on system content and accuracy. When feature or defect problems come back from beta testing, that's bad news, and we might have to freeze the code. Therefore, treat beta testing as "business as usual". Plan to have no problems come back.
(Aug 19, 2003)
Barry Boehm and Richard Turner have produced an important and balanced book about agile versus plan-driven methods. Unfortunate title, perhaps, and a few things to disagree with, but highly recommended.
(Jul 28, 2003)
With the best of will and effort, sometimes things still go wrong. When that happens, the way we deal with the problem can make the difference between an unhappy customer and one who is actually happier than he was before the problem happened. This letter tells about such a time.
(Jun 23, 2003)
The YAGNI principle says that we should not build any code that we do not currently need. But some parts of our systems benefit from being built from data rather than from code. Therefore if we follow YAGNI we could never build such code. But wait? What about the rules of simplicity?
(Jun 12, 2003)
I'm been struggling for years with notions like having empathy with our mistakes, Kerth's Prime Directive, and the like. Springing from a couple of notes on the extremeprogramming group, and a blog entry from Dale Emery, here's my latest rant.
(Apr 2, 2003)
Frank Gannon
Frank Gannon wrote this column for New Yorker, if I'm not mistaken, back in 1987. I think it deserves another run. I wrote a year ago for permission to publish, but so far cannot find the copyright owner. It's about flowers and gardens, so perhaps it's appropriate for this Valentine's Day. (Frank found this page somehow and has kindly granted his permission to post the article, which appeared in Atlantic, not New Yorker. Thanks, Frank!)
(Nov 21, 2002)
The Logitech io Personal Digital Pen remembers what you write or draw and then uploads it to your computer when next you plug it in. It must be good for something. How does it work? The paper has coordinates built in!
(Oct 9, 2002)
Jeff, an experienced XP coach, takes a hard look at Pete McBreen's book, and finds it to contain good questions. He feels that the answers fall short -- perhaps due to Pete's inexperience with XP.
(Oct 8, 2002)
Wyatt Sutherland
Wyatt provides a detailed, exciting, and valuable diary of a project moving towards Extreme Programming. Highly Recommended.
(Oct 1, 2002)
The authors show us how they use aspect-oriented programming in AspectJ to facilitate isolation of testable units, without hand-crafting Mock Objects or using a specialized Mock Object generation tool.
(Sep 5, 2002)
We're often afraid that if we don't do enough design up front, our program may bog down and become hard to maintain. This will cause expensive rework, or worse, project cancellation. Simple design with refactoring isn't rework. You may proceed without fear.
(Aug 22, 2002)
Some of the XP practices may be things we want to do all the time. Some we may wish to do only part of the time. When we are really skilled in use of a technique, we're best equipped to decide when to use it. Here are some exercises that may help build skill. And make up your own exercises. Let us know about how they work. Added: Planning Etudes.
(Aug 13, 2002)
Using a simple deck of cards, examine how Extreme Programming gives you a new and better way of managing software.
(Aug 2, 2002)
All too often, they change the priorities and our project gets cancelled, or put on "hold", before it's done. This is frustrating, demoralizing, and wasteful of resources. Ship it before they can stop you! This maximizes the value of your work, and reduces stomach acid, all at the same time.
(Aug 1, 2002)
When you're in a group that serves many customers, your backlog list tends to become infinitely long. You're not sure whether to report on things that aren't being done, or to pretend they are being done, or what. Don't keep a backlog list at all. The result could be greater clarity for your customers, and far less hassle for you.
(Jul 8, 2002)
I was recently invited to write a new introduction to the Korean edition of Extreme Programming Installed. What a rush! International fame and glory. Thanks to Ann and Chet for making it possible. Here's what I wrote
(Jun 29, 2002)
A recent discussion on the Extreme Programming mailing list addressed whether there is an "80-20" rule in software development. Let's take a look at some numbers.
(Jun 24, 2002)
Feedback helps a developer know he needs "something". No process will help us notice that mathematical proof is needed if we have never heard of mathematical proof. Some processes choose to list all possible techniques. XP does not.
(Jun 23, 2002)
SonicBlue (Rio) has built a device I've been wanting for years. It eats your CDs and plays them back digitally: 40gig worth of them! Here's an early review of my experience with this new toy. Update: It has a bit of XP in it!
(Apr 2, 2002)
I have no excuse for this material. It just came out of my pen. And Wyatt Sutherland's.
(Mar 25, 2002)
On the "Agile Testing" mailing list, Michael Bolton asked for an example of XP-style testing and programming. This example was the result. It represents about 90 minutes of work, counting two phone calls and doing the original writeup.
(Mar 20, 2002)
It is said that by meditating on the words and actions of the masters, we may be enlightened. Sometimes it's just entertaining.
(Feb 8, 2002)
If you are serious about your profession, if you are serious about teamwork, if you are serious about success, please read this book.
(Feb 5, 2002)
Updated to include our first review of Java Tools for eXtreme Programming. These books are all about agile software development, even those written before the term existed. They're all worth having and reading, more than once. Dig in!
(Feb 2, 2002)
Chet and Ron have been working with Ruby, because it's the nearest thing there is to Smalltalk. Here are the books we use.
(Jan 28, 2002)
Chet Hendrickson
Chet looks at some humor and some ancient architecture. We leave it to you to figure out which is which.
(Jan 28, 2002)
A detective in puce, mentoring, massive parallel processing, and two books on writing. What more could you want?
(Jan 25, 2002)
Sean Shubin
Sean Shubin has begun using Test-First development. He wanted to share these ideas and guidelines with us.
(Jan 21, 2002)
Maybe it's just the name: Extreme Programming. Maybe it's something we said. Whatever the cause, there are lots of misconceptions about XP. From time to time we'll try to correct some of them here.
(Jan 20, 2002)
This is the first of a regular series of book reviews. We'll only review books we have read, and we'll call them the way we see them. This time we look at five books, ranging from XSLT to the world of Dream. Updated to add a sixth on time management
(Jan 20, 2002)
Fear is good if there's a tiger in the room. Not so good if there's a bug in the software.
(Jan 20, 2002)
Bryan Dollery
Bryan Dollery reports on an interesting conversation between Achilles and the Tortoise. This one is about design, or the lack of it, in XP. Thanks, Bryan
(Jan 20, 2002)
People work together to get what they want. One thing that everyone wants in one form or another is knowledge. How can we share knowledge about XP?
(Jan 16, 2002)
Ellen Ferlazzo
Ellen Ferlazzo, of Sprezzatura Systems, took my rant on documentation seriously. Ellen says that if you do it right, you can deliver the documentation at the same time as the software. I was willing to give the writers an extra iteration. Rock on, Ellen!
(Jan 1, 2002)
In this review, Extreme Programming Installed, Planning Extreme Programming, Extreme Programming Explained, The Humane Interface, and Adaptive Software Development.
(Nov 21, 2001)
"Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read." --Groucho Marx Outside your extreme programming project, you will probably need documentation: by all means, write it. Inside your project, there is so much verbal communication that you may need very little else.Trust yourselves to know the difference.
(Nov 21, 2001)
Here's a bit of a rant I wrote some time back, talking about how to write the manuals for an XP project by using writers as part of the team. It's a serious proposal, written with tongue a bit in cheek.
(Oct 26, 2001)
One of the most common raps against XP isn't even true. People think we say that documentation is a bad idea. XP is focused on conversation for maximum effectiveness. Our recommendations on documentation follow from that simple fact.
(Oct 21, 2001)
Test everything; eliminate duplication; express all ideas; minimize entities:These few simple rules, applied locally, can help a high quality global design to emerge.
(Oct 8, 2001)
One of the most common failings of XP teams is insufficient testing. XP asks for more testing than many teams are used to. But what about projects that need reliability at a substantially higher level? Are they out of luck?
(Oct 7, 2001)
Kent Beck has described XP as designed to go with people's natural instincts. In this short series of articles, we'll take a look at how XP accomplishes goals without a need for lots of discipline or management pressure. In this article, the topic is documentation.
(Sep 30, 2001)
XP seems to be made up of a lot of practices. They might be good, but what's the bottom line for a business person? The acid test for XP isn't what the team does, but what they deliver. Here's what you should get from your XP team.
(Sep 29, 2001)
Pair programming might be useful between peers. But it seems like an inefficient use of a "senior" person's time to be tied down to a "junior" person. Experience shows that pairing almost always pays off for both parties. However, not all readers are convinced: how about you?
(Sep 24, 2001)
(Sep 5, 2001)
People ask whether they have to do the XP practices to be doing XP. In some environments, some of the practices are difficult or impossible. You don't have to do the practices to be doing XP: You have to have done them. Practice makes perfect.
(Aug 30, 2001)
The XP Circle of Life helps keep projects alive. A key aspect of this cycle is the Acceptance Test. Acceptance Tests are critical to communication among team members, especially between customer and programmer.
(Aug 21, 2001)
When unexpected defects arise, it can take a long time to isolate the problem. This can have large and unpredictable impact on the team's progress. Extreme teams release software frequently, keeping their unit tests at 100 percent. The result is smoother progress toward completion, fewer unhappy surprises, and continuing improvement in quality.
(Dec 13, 2000)
Chris Morris
A pre-introduction to XP from the perspective of the average corporate developer.
(Dec 5, 2000)
Chet Hendrickson
Let's try to get a sense of what is good process and what is not, without a lot of rigmarole about the specific practices.
(Dec 4, 2000)
An XP approach may deliver more value throughout the entire project.
(Dec 3, 2000)
Michael Feathers
Building a C++ Dependency Analyzer Test-First.
(Dec 2, 2000)
Here's the C3 programming space!
(Nov 30, 2000)
Bill Pyritz
Bill discusses the benefits of test first programming in an instrumented C++ telecommunications application.
(Oct 1, 2000)
Mario Contestabile
Experiments with XP in a difficult environment.
(Sep 1, 2000)
Michael Feathers
Building a C++ Dependency Analyzer Test-First.
(Sep 1, 2000)
Business analysts should work as aides to the customer, not as an interface between customer and programmer
(Sep 1, 2000)
Michael Feathers
Growing an application one test at a time. From a Series.
(Sep 1, 2000)
Alistair Cockburn
Alistair says that XP does not flatten the exponential cost of change curve.
(Aug 1, 2000)
Houses aren't software. You can build software incrementally.
(Jul 1, 2000)
We build a simple alarm clock object, applying the XP rules of simplicity, just to see how it will turn out.
(Jan 1, 2000)
How do XP and CMM relate?
(Sep 1, 1999)
Pete McBreen
How can we approach a project with a very limited analysis phase.
(Sep 1, 1999)
A somewhat hokey tale about the XP variables, Resources,Scope, Quality, Time.
(Sep 1, 1999)
The overly complex cards once tried on C3. Don't try these at home.
(Sep 1, 1999)
Let's get some data about XP!
(Sep 1, 1999)
Repeated estimation and tracking results in improved ability to estimate.
(Sep 1, 1999)
An introduction to some of the key XP practices
(Sep 1, 1999)
Modeling the cost and return of anticipation shows that it may not be as valuable as we think.
(Sep 1, 1999)
Peter Gassman
Questions about how and when to do some XP practices.
(Jul 2, 1999)
"Of all the words of tongue or pen, the saddest are these .. it might have been."
(Feb 1, 1999)
The STQE link provides access to Ron Jeffries' less famous article in that magazine.
(Apr 10, 1998)
They're not XP's rules, they're the team's rules.
(Apr 8, 1998)
(Mar 24, 1998)
The C3 project team has voluntarily adopted a large number of practices. Every team member follows these practices closely. We have found that designing, coding, and testing in a consistent way means that the team becomes quite well integrated and that team members know just what they can expect from each other. Software quality is kept more uniform, and at a high level.
(Mar 23, 1998)
We all code to the exact same standards. We name our classes and methods the same way, we format code the same way.
(Mar 23, 1998)
We call the combination of frequent release with tests at 100%: continuous integration, relentless testing. The result is rapid progress and a system that always works better than it did the day before.
(Mar 23, 1998)
A few times during the project, a team took on a task and did not complete it within the iteration. They wanted to complete the task and kept it for the next iteration. This generally turned out to be a mistake.
(Mar 23, 1998)
We use CRC card design almost exclusively. Developers, managers, and users are all comfortable with the cards, since they are non-threatening. Moving the cards around makes it easy to describe how classes work, and it is easy to throw a couple of cards away and create new ones if the design isn’t working out.
(Mar 23, 1998)
In general, we do not comment our methods. Beck teaches that a comment is used to indicate that a method is not yet finished. That’s how we use them.
(Mar 23, 1998)
Simplicity + Communication + Testing = Aggressiveness
(Mar 23, 1998)
Here are a few of the key code formatting patterns we use. The names and some of the examples are from Kent’s book.
(Mar 23, 1998)
There is some written documentation for the software, more commonly interpreting requirements than documenting design. Sometimes we document an approach to some particularly difficult area. We "never" document code.
(Mar 23, 1998)
We do use class comments to describe what a class is for, and sometimes how it works. We probably don’t do this often enough, and we probably don’t keep them as up to date as we should.
(Mar 23, 1998)
Never underestimate the power of inspecting and changing things with Inspectors. Perhaps your GemStone database is messed up: a bunch of People have excess Parts in certain Bins.