A flow app, one that steps the user through an acyclic graph, typically gathering info at each stage, can be built to provide iterative user value by gradual refinement. Let’s look at how that’s done. Before we get into it, for me, and maybe for you, too, geekery right now is not the most important […]
Iterative User Value in Flows Read More »
Real Programming S01E02: Look, Ma! A Test Last time we did a rapid-fire model/view split, just so we could test. Now we gotta test this bad boy a little! If you want to follow along in the code, the project is https://github.com/geepawhill/yz Hey, it’s GeePaw and I still have Wally, and Molly’s off camera, and
Real Programming S01E02: Look, Ma! A Test! Read More »
The correlation principle says that our productivity is tightly correlated with the internal quality of software. The two go up together, and they go down together, and you can’t trade away the one to get more of the other. Let’s talk it over. I remind us that geekery isn’t the main story right now, though
The Correlation Principle Read More »
How do we iterate user value? How can we follow the "more smaller steps" approach and still deliver a positive experience for the user? Today let’s look at some ways to approach this problem. It’s important for me to remind you that, for me and many others, working for equity in the world is far
Iterative User Value Read More »
(Video: https://vimeo.com/448155181) Real Programming S01E01: Getting Started Hi Folks! In this first episode we lay the groundwork for a simple desktop Yahtzee application. If you want to follow along in the code, the project is https://github.com/geepawhill/yz Transcript Hey, folks. It’s GeePaw sitting out here on my deck, where I do most of my work in
Real Programming S01E01: Getting Started | Video Read More »
I do "pathing" when I project my work into the future: laying out a sequence of work steps, where each step ends with the code in a shippable state. More than design, and more than planning, pathing is a kind of work-style, and it brings me several benefits. Here in the US, citizens are out
Pathing: A Style of Laying Out Work Read More »
"Embrace change" is the modern geekery catchphrase for our most basic idea: We change software, therefore we want everything around us to support that: code, technique, tools, controls, tracking, planning, infrastructure, and above all, culture. Before we start, remember, geekery’s not the main story right now. The real embrace of change is happening out there
Embrace Change: Modern Geekery Practices Read More »
I want to start talking about teaching in the geek trades. Today in particular, I want to talk about "emphasis", what our style & materials stresses or underlines about the path to mastery for our up and coming geeks. Black lives matter. Here I sit writing geekery, a sideshow, while my siblings are out there
Pedagogy In The Trade: Changing Emphasis Read More »
I strongly recommend high variation in both format and facilitator of retrospectives. I don’t hear this take often, and I certainly don’t see it at a lot of shops, but I think it has tremendous merit. Let’s talk it over. I don’t wanna be pro forma, & I know I’ve mentioned this a lot, but
Retrospectives: Variety is Key Read More »
My standards for TDD microtests are the same standards I have for shipping code, and I follow them in microtests for the same reason I follow them in shipping code: they make me faster. This geekery muse is comfort food, for me and maybe for you, but I want to keep stressing: I fully endorse
TDD Tests Are First-Class Code Read More »
