Sunday, June 24, 2018
I can't remember where I came across the quote, "Make it work, make it right, make it fast." Using my Google-fu I can see that it's been attributed to Kent Beck, which I believe came from his book about Test-Driven Development. I haven't read the book, but as I have become more experienced as a software developer, I found that this way of thinking makes sense. Of course, I would be remiss to say that this way of thinking should always be applied. Also, we need to determine the definition of "make it work." Context is important.
In the context of someone who is experimenting in a "lab", we can add the phrase, "make it." Making something moves us towards making it "work." Of course, depending on the context you may not want to show someone something that isn't working. I've done that before, and pity is what almost always follows with me saying, "You have to understand, Mr. T., it's not finished."
Making something work, may mean having minimal or no error handling. It could also mean, that error handling should be fully implemented and complete, because then it doesn't always "work", it only "works" some of the time. So by induction (which one of my past professors thinks is, and I quote, "s---"), the definition for what is "right" and what is "fast" must be defined, as well.
For this blog, this post is the definition of "make it work" relative to all my other posts. I'm short on time right now, so that's how it's going to be. On a side note, I'll have to add the previously mentioned TDD book to my reading list.