It's official; there's a release for the IMock tool I've created. The first actual release being available on the repo Releases isn't enough for me. There's a few components to this project right now. OK... really just 2 components. IMock There's the core pieces that make up the IMock framework.…
THE END IS HERE!!! Hopefully not from COVID-19.... I've scheduled this on April 4th... Who knows where the world will be in a month... ANYWAY.... last video for the first set of requirements for the pizza shop. I'm not 100% happy with everything; the TODO's can show that. It's good.…
Getting close to the end... Just some touchups; better supporting classes. Breaking things out into explicit concepts in the code.…
I can hear you - HOW LONG IS HE GONNA DO THIS!!!... A while. There's 8 video's total. ... For the intial set of requirements.…
There is a stupid amount of time put into doing this when I've been able to do it in about 20 minutes with 20 lines of code. This is what I do with code. I take time to represent the concepts that exist in the code... If it's not explicit,…
Just getting the functionality in place is not enough. We have to clean and care for our code. While metaphors and analogies only go so far; I still really enjoy the gardening metaphor. We must care for the code like we must plants. Just getting it planted isn't enough to…
There's story mapping. I've written about Feature Mapping. Now; let's talk about Intent Mapping. Intent Mapping I know this isn't anything unique that I've come up with. Mostly because it's just pulling together observations from mobs I've observed. I know Llewellyn does similar things. I call it intent mapping based…
Continuing the work - Video 3 of the initial requirements. I've done this same functionality in 20 lines of code... It wasn't very flexibile though.…