Critical developer skills in 5 minutes or less.
Half my own learning journey, half experiment to improve software education. These posts attempt to extract best practices from, and connect readers to, leading software literature.
Continuing the event storm explorations, I tested out several approaches for translating event storms into system designs.
Event storm sticky notes capture high-level process flow, but different actors in that flow often have specific expectations of each other. This is where high-level data modeling shines.
A key challenge working on the Ionide test explorer was merging data from various sources into one view. It was good example where the fundamental challenge wasn’t technical, but defining useful assumptions.
I contributed debug support to the Ionide (F#) test explorer for VS Code. Here’s the quirks I encountered.
I managed to re-teach myself about always measuring first when considering performance.
Information Hiding is a critical, but tricky principle to master. This post continues a worked example of Information Hiding based on my Ionide test explorer contributions.
Information Hiding is a critical, but tricky principle to get familiar with. My work on the Ionide Test Explorer presented some good examples of refactoring to limit scope (Information Hiding). I’ll try to recreate them as worked examples.
I contributed to the Ionide (F#) test explorer for VS Code. I’m proud of the work, so please pardon a bit of show and tell.
Basecamp created hill charts as a novel way to view project progress and outstanding risk. The goal is to give managers a feel for progress without having to ask, but it also addresses key communication issues caused by uncertainty in creative work.
I think small teams are an underemphasized key element of the Shape Up approach to project management.