Quinn Gil

While working on some Object Oriented training, I found myself in some cognitive disagreement. I was flip-flopping between two implementations. One used inheritance, one used composition. If you follow along much, you'll know that I'm very strongly on the use composition side. There are

Shu Late 2016 I joined a team that was, essentially, an XP team. Over the next 2 years we adapted and morphed our practices. We were very big on the experimentation. There were a couple practices that we held onto through all it all

I've been 'aware' of an awesome feature from using the NullObject pattern since I really started using them. I didn't realize what that feature was until I had to explain it to a colleague today. I say it a lot, maybe not here, but

I'm writing this a few days ahead. It's a holiday week. I'm going light this week. No post planned. I mean... i'm writing... So whatever. Represent the Concept This is my war drum, hammer, and dead horse. I see the value, the simplification, the

There's a few common patterns in software development that I consider an antipattern to highly effective code. Mostly it's Factories and Builders. Guess what this ramble is about? Builders are an Anti-Pattern There's more than one reason they are an anti-pattern. My favorite goes

I've written about my approaches to the UI before. The one that shows an example is The UI Does NOTHING!. It takes a UWP example and transforms it into what I'd do. I haven't really done a more exhaustive look at this process, or

I'm working with teams to become more familiar with Git. We're a Micrsoft shop and used TFS exclusively up until a few years ago. One of the challenges faced is how to get familiar with using Git. That's a huge hurdle I keep hearing.

Got to green last time, now it's time to refactor and get it flowing!!! Patterns have started to show themselves; we extract it. We make similar things more similar so that we can extract the general form. If you have an idea; try it.

We refactored last episode, so we can do a new test! I'm lazy, 23 reflects that. Time to hack away and get 23 working! Largely based off of the code for 10. Make it work, then refactor it. With our modifications to the copied

Following up from our failing test for 10... Let's get back to it I don't have to step through code often. It's fun to do it sometimes. While stepping through, I try to express what I expect and then my surprise when I get

I talked a lot - Now to see things happen! We want to use the discussed indexing approach! I almost screw up and go off the rails with a failing test!!! The HORROR!!! Almost. After getting everything green; we dive into refactoring into the

Let's get to MULTI-DIGIT ... dig...its... Yeah! 0-9 are done - MULTI DIGIT TIME! Let's go to 10! I've gone into the multi-digits with an idea, and ... it's the wrong idea. This is my favorite video of the entire set for this series. I

Let's get to digit 6! This is just following the pattern we've followed established in the first 5 digits. Despite my habit of going top-down to modify the tests before I rename; I life the bottom up approach. When I get to the top,

Live coding, hehe... pre-recorded. Gotta keep the code resharper green! Hell yeah! At the start here I decide to do all the digits first before moving onto multiple digits. Was it a good idea? I don't know - it was an idea! That's all

An LCD Kata from Cyber-dojo.org. I went into this with no plan of attack. I have some ideas, but nothing planned or expected! How will I solve the Kata?! Oh... right... who cares! Watch me code!

This is a book I highly recommend. It's slightly below Beyond Legacy Code. It's added a lot of words for concepts I've been using without good descriptors. The biggest of these is "cognitive load". I'm sure it's a well known concept; this

The complete set of videos! Enjoy

The final episode of FizzBuzz TDD'd! Before we dive in; we do a refactor to improve the clarity of the intent of our tests. It's a pretty quick jump into following the practice of triangulation as we did for the first three requirements. Continue

First two requirements complete. Time to start the 3rd! Write tests, not just to drive the code; but for safety in the future! Don't modify existing behavior when making a test pass. I really like the Elvis Operator "I know what the test

MORE TDD FIZZBUZZ!!! Let's start the SECOND requirement... We may be going slightly slower than I've seen FizzBuzz done... Maybe... I can't think of any additional tests that will fail for the first requirement, since we have a general solution - We can move

Hello and Welcome to another edition of TWITTER RESPONDS! From a post announcement on twitter https://twitter.com/TheQuinnGil/status/1166730201826549761 Our tools can kill maintainability. My thoughts on how Frameworks can be a negative to our products. Tool Impact On Developer Discipline -

TDD FizzBuzz! Welcome back! I'm trying a smaller video window - showing just the code, no IDE. With Live Testing turned on, we can still see the test status. One of the techniques I use to help myself when copy/pasting tests is to

Something that's been brought up to me, repeatedly, is if I can show how I do things. My style of coding is something that isn't common. It's well recognized by experienced developers as something they used to great success in the past. It's not

OK - Take number 5? I think this is take number 5 at working with SmallTalk. I'm using Cincom VisualWorks. It was demo'd by [Carl Gundel] at a Seattle Software Crafter Meetup. I tried Object Studio previously to ... frustration. I'm still expecting some trouble.

I'm at Agile 2019. I don't have a post written up for this week; so I'm pre-planning this no-op post. Since January 2018, I've gone from knowing zero people at conferences to having had face to face conversations with 31 of them. Multiple conversations