Quinn Gil

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

Hmm... Fluent types vs Type Types awaiting vs method As part of the Principle of MicroObjects, Represent ALL Concepts, we still need to manipulate the data; at some point; or pass data to 3rd party libraries as primitives. We need to get the raw

I typically code a lot. With a recent role change, not so much at work. To compensate, because I need to code, I have a side project I'm working on. While working on various aspects of this, I've found a recurring theme. I don't

Uncle Bob has a post on his blog from a while back called "The Dark Path". I've personally had an interesting journey with this post. It's taken another turn as I read about the new programming language "V". Unlike Uncle

I've had this sitting in my queue for over a year. Waiting for some day when I have some thoughts on it. Is today that day... Ehh... Probably not. I'm going to try anyway. I'm writing this the same day I wrote the "

Represent All Concepts Let's continue our exploration of how the MicroObjects technical practices support the principle of representing all concepts that exist in the code as objects in the code. In the last post we covered some benefits of applying the practices for this

Represent All Concepts Let's continue our exploration of how the MicroObjects technical practices support the principle of representing all concepts that exist in the code as objects in the code. In the first post we covered the same practices my hour long presentation covers.

Represent All Concepts Let's continue our exploration of how the MicroObjects technical practices support the principle of representing all concepts that exist in the code as objects in the code. In the last post we covered No Getters / No Setters if Only as a

I had a fantastic chat with a colleague about the MicroObjects technical practices at lunch yesterday. Well... yesterday for writing this. Probably a week ago when it goes live... and no idea how long ago for you reading this. :) She wanted to know more

I presented twice at XP 2019! One of them was about the MicroObjects technical practices. Which was fantastic! It's a great opportunity to share what I've found useful! This post is about the second presentation; the experience report. I promote the MicroObjects technical practices

I met Suzanne Fortman from Cincom at XP2019 and had som great conversations about SmallTalk and the community. I decided to download ObjectStudio to play with the product and maybe actually get to write some smalltalk. The experience was not what I was expecting.