Beneficial Results - Testability Testability - The only way to not have legacy code. If the code you're working in doesn't have tests - it's legacy code. The more tests you have the less legacy it is. I say this coming from the many conversations I've had about
As a Software Engineer As a Software Engineer, what's our job? As a Software Engineer, what's our responsibility? As a Software Engineer, what do we do for the company? I assume we all have a job description - Is that what we do? Design, Write, Test, and Debug
Technical Practices: if only as a Guard Clause ifs only as a guard clause is one of the most impactful things that can be done to reduce complexity in code. I'm a very strong advocate for a lot of Object Oriented Practices. Most of them, really. I'm not great at all the
MicroObjects to Technical Practices MicroObjects is a fantastic way to write OO code. There's very few pain points that I've encountered. The teams using MicroObjects deploy confidently and have near zero bugs. New functionality and features are quick and easy to implement. The practice is vastly different than
My Disagreement With Elegant Objects We don't have to agree on everything to learn and grow from each other. This is exemplified for me with the Elegant Objects by Yegor Bugayenko. Elegant Objects being a book read about 6 months after an OOBootCamp from Fred George crystallized a few
Getting Started With Unit Testing - VS & C# I was at a the FlatIron Seattle open house where I met many great people. I had a great time talking with people about testing and Test Driven Development. It's something not as heavily emphasized as I think it should be in the education
Book Review: Clean Code I'm going to start this with saying that Clean Code helped me a lot early in my career. It also hindered me a lot. Clean Code places so much emphasis on things so trivial... I was misinformed about what is actually important to writing
Technical Practices: Trust Your Code There's a few ways I've talked about this historically. One of the biggest that is probably well recognized in the industry No Nulls Do not let nulls into your code. Clean Code touches the idea All it takes is one missing null check to
OOP Technical Practices: Low Coupling Low coupling can mean a few flavors of things depending on your context. My general definition of Low Coupling is "Not knowing what it is, just what it does". This allows us to interact with objects without knowing the underlying implementation, and
Technical Practices: Switch and Else always evil No Getters We've covered why we don't use getters. This reason is the fundamental principle driving all of Object Oriented Programming. Encapsulate Behavior. Encapsulating behavior allows changes to that behavior with a guarantee it is changed across the system. We need to encapsulate the
OOP Quick: MicroObjects and Json A question on twitter has moved forward doing an example of serialization and deserialization. This is gonna be a pretty quick example and blog post as this is being done so that I can provide a code sample as my answer to the asker!
Quick: BookEnd for HttpClient At a GREAT [Seattle Software Craftsmanshi meetup where David Bernstein gave a talk, there was a question at the end that really piqued my interest. The question was, paraphrased: How can we get tests for something using the HttpClient? This is a C# specific
OOP Technical Practices: High Cohesion I see High Cohesion as a key component of getting single responsibility into code. Hopefully it's clear from my blogging that there's far more to it than just one thing, but a class that is does not have High Cohesion cannot have a single
OOP Technical Practices: No Primitives No Primities. My idea with not using the default data types centers around them being data storage. Working on object oriented langauges, we don't need to be concerned about the raw data storage mechanism. We deal with objects that communicate with each other, not
OOP Beneficial Results: Code Reuse I don't remember exactly where or who, but writing re-usable code was impressed upon me as an important thing I now completely disagree with that. Do not write reusable code. One of the worst things you can do when writing code is to make
OOP Teach Yourself MicroObjects: Output the Data Encapsulation - it's a huge part of what allows us to be highly effective developers. It's what MicroObjects is about. Encapsulation is the highest thing to strive for when striving to write good code. If we encapsulate our data so effectively that we can
OOP Teach Yourself MicroObjects: Add Two Ints I'm working on ways I can share the practices and mindset that allows me to create MicroObjects. One of the suggestions I've gotten from a co-worker, John, was to create as simple of a project as possible and show my steps to breaking it
SoftwareAsACraft Book Review: Java by Comparison I got Java By Comparison from Amazon a while ago. I wasn't impressed with what my initial page flipping showed me. I skimmed it and largely evaluated based on name
OOP Fantasy Grounds Module Maker - It Works Some friends and I play D&D through Fantasy Grounds. It's a great app, we have a lot of fun playing through it. While we start getting used to it; there's been interest in being able to make custom things. From a couple
NoEstimates #NoEstimates - My Rambling NOTE: I'm hoping this serves as my reference point for answering questions about my thoughts on NoEstimates. I'll probably expand it over time as I get more data. 2018-07-05 - Initial Writing 2018-07-09.A - Clarifying the lack fo seeing arguments. 2018-07-09.B -
TDD UWP HackerNews Reader - OOP The HackerNews Reader app is a project I'm using to practice and beat new concepts into my head. It's not quite proof of concept level - because I understand the concepts; it's a playground of sorts. Originally it was a place to practice TDD
Refactoring UWP : Spike The List NOTE: This was written about a year before posting. Churning I've been putting off working on the UWP app for a while. Part of it is routine change due to summer. The larger part is that I don't really know UI Widgets in UWP
TDD HackerNews UWP - Partial Item; Not a collection NOTE: This was written about a year before posting. As mentioned in the last UWP post; we're going to reset a little and get just a single item going through the entire pipe. Losing the idea of Items for now and focus on just
UWP UWP Cleaning Up - Refit Black Magic NOTE: This was written about a year before posting. 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 loss of
TDD Kata - Game Of Life NOTE: This was written about a year before posting; months before I stumbled on the MicroObject style. 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
