UWP UWP Cleaning Up - Refit Black Magic I've spoken highly of the project Refit and that it's a nice port of Retrofit. I still stand by this; but... I'm wondering; do I need it? I'm getting HttpResponseMessage back. There's the
TDD Kata - Game Of Life This kata is Conway's Game of Life. It's a simple set of requirements. The universe of the Game of Life is an infinite two-dimensional orthogonal grid of square cells, each of which is
TDD Design & Development Principles - XP - Quality Circle - Part 2 This is the second post of the Quality Circle. As a reminder; CIRCLES! This post is going to talk about the Green Circle. Another reminder is the tight interconnection between all of the
TDD Design & Development Principles - XP - Quality Circle - Part 1 As a reminder; CIRCLES! This post is going to talk about the Green Circle. Another reminder is the tight interconnection between all of the components. I posted about the blue Keyboard Circle a
µObject : Battleship At Agile Open Northwest, I had the opportunity to explore µObjects through a battleship kata. I felt the environment and process doing it during the mobbing session were a bit more contrived than
TagAlong TagAlong: ReSharper Plugin This is my first attempt at creating a plugin for ReSharper. It seems very daunting at first. It's taken me a few hours to actually figure out the base of what I wanted
BestPractices Technical Practices: Never Return Your Data No Getters That's the normal form of this technical practice. No Getters There's some uncertainity around what "No Getters" means. OK, there's two versions of it. Yegor Bugayenko in Elegant Objects
TDD µObjects: Unit Testable UI Interactions This is a follow up to the Hotel Pattern which I've pretty much abandoned, though it's concepts and ideas have evolved into my current practices. It ties into the Interface Overload mechanism I
XP Patterns: Null Object I've covered never having nulls and that's what the NullObject pattern is here to help us with. The NullObject pattern is one that I tried to implement earlier in my career (mostly after
microoop My Thoughts: Pass through vs Base class A conflict that has come up a few times is using composition and a pass through or a base class I favor pass through; I write it that way Everytime. The other engineer
BestPractices My Thoughts: 'Interface' isn't harmful My thoughts about Object Oriented Programming has evolved over the years. Especially in the past 6 months. My development of MicroObjects has caused a lot of thinking about Object Oriented Programming and how
µObjects: Single Style One of the things I've noticed working with multiple devs doing microObjects is that the code generated tends towards a single style. A module can be built in as many ways, or more,
Book Review Book Review: The Nature of Software Development TL;DR: I loved the book. Go read it. Over the past few years working with a team of XP devs who've been using the XP practices for well over a decade each
UWP UWP: Signing and Verifying Recently I had the joy of busting open the cryptographic documentation to figure out how to sign a file, and verify that signature. There are a lot of documentations for .NET Framework -
microObject µObject Poker: Scoring a Hand I found I'm not a huge fan of the video. I don't tend to put a lot of time and effort into each post; it's an opportunity for me to share research and
µObjects: Class creation dilemma! Working with µObjects at work and in the examples I've been experimenting with; I've found a recurring conflict of principles. In the early days of learning actual Object Oriented Programming with Fred George
µObjects M:TG Game - Event Bussing I've been pondering how to do some µObjects in a more intelligent system for a while. I'm going to try to use Magic: The Gathering for this. Much like the poke one; the
microoop µObjects: Fluent Types I expect us all to be aware of the anti-pattern Primitive Obsession. If not - there are some quick resources available. Now that we have an idea of Primitive Obsession; I'll give my
µObjects: Code Free Constructors One of the big practices I got from Elegant Objects is the concept of a code free constructor. Your constructor should have zero logic. Let's see why! Always born My favorite reason for
BestPractices µObjects: Being CLEAN Beyond Legacy Code's CLEAN I've read David Bernstein's Beyond Legacy Code and clearly enjoyed it. :) One of the concepts he expands on in the book is "Clean Code". He takes this
TDD µObjects: Being Nonredundant Redundant code is code that changes at the same time for the same reason. Part of object oriented programming is limiting change to a single place. If it changes, it should change in
TDD µObjects: Being Assertive Being assertive is about being self-responsbile. Being assertive is about an object being lazy. This also has the object doing all behaviors for the state it holds. It follows from encapsulation that an
µObjects @ AONW I went to Agile Open Northwest. IT WAS AMAZING! I don't go to a lot of conferences; but this was a wonderful experience. Super friendly, super welcoming, super supportive. I've been developing the
TDD µObjects: Being Encapsulated Encapsulation for objects is, IMO, how well the data is hidden. Encapsulation is only acting via behavior from an object. Never getting data and doing something. A well encapsulated object is also a
TDD µObjects: Being Loosely Coupled Loose coupling is about how much a class knows about the objects it's using. The less a class knows about the components it is using; the better the decoupling. Or they are loosely