There is a guy I’m working with who is trying to wrap his head around design principles. He’s been watching a lot of PluralSight videos. As he was processing information about Inversion of Control, he asked the natural question I’ve never actually considered before. “Why is it called Inversion of Control? Normally, when you talk about ‘Inversion’ you are talking about reversing something or negating something. That isn’t what we are doing here.”
Way back in the day when lines were first being painted on roads. The early lines were painted by hand. In those days, a painter was hired and given a stretch of road to paint. The first day he got on very well. In fact, he was one of the best line painters they had ever had. His lines were perfectly aligned, there were no unpainted areas in the space where there should be paint, and he managed to get 500 yards of road painted. The average line painter normally did 250 yards in the first day. The managers who had hired him were quite pleased.
I’ve been asked to train a group of developers in the use of SpecFlow so that they can use it to write Selenium Tests. So, in an attempt to “kill two birds with one stone” I thought today’s post would cover how to get the SpecFlow environment setup. Not only will it help me prepare for the training session I will be leading, but it will help me when I need to set this up the next time because it tends to be a bit confusing when you setup a new project. You’ll see why in a bit.
A long time ago, in a galaxy far far away, we were forced to name variables and methods with very short names. When I started my career, I was programming Clipper and C. Clipper was a dBase compiler, so it only had 10 characters available for variable names. You could write longer variable names if you wanted, but only the first 10 mattered. I think at the time, C gave us 32 characters. But now, we aren’t so limited. And so the argument goes, if you use long variable names, you shouldn’t need to comment your code. I’ve argued as much.
Of course every time you bring this subject up, you will inevitably find someone who will say, “But don’t we need comments to at least explain what the code was supposed to do? After all, code is generally hard to read.” Well, yes I guess it is if you are new to the language. But should every foreign movie have subtitles? Would you want native language movies to have subtitles because other people in the room might not understand it? Must we dumb everything down to the lowest common denominator? If so, where will it stop?
Several comments this week contribute to this week’s post.
The first, and the one that pushed me to write this post, is a discussion over at Simple Programmer on a post called “Cracking the Coding Interview” where I made the following statement,
For the purposes of this post, I’m going to assume that you already have the NUnit Test Runner installed. The question you are looking to get answered is, “How do I run NUnit from Visual Studio” or even more importantly, “How do I DEBUG NUnit test from Visual Studio”. The following step by step should help you.
Right click on the project in Solution Explorer that represents your test project.
From the resulting menu, select “Properties.” In the resulting window, select the “Debug” tab from the left-hand side of the window.
You will want to select “Start external program” and point it to the UNnit runner that got installed when you installed NUnit.
Now, whenever you run this project, with or without the debugger, NUnit will start up.
Note: there is no reason to pass parameters telling it what DLL you want to run because it will load the last DLL it had up.
But, if you wanted to do that, you could pass the location of the DLL as a parameter to the GUI runner.
There are other parameters you can use.
When I was in college, there were some guys I hung out with who played this game called “Questions” which they got from some book. Actually, it was a play. Anyhow, the basic rules are:
There was also this podcast at DotNetRocks where they were talking about a beer app and how they had added game elements to the app by adding badges for various types of beer to get you out of your comfort zone. Maybe there is one for “My first beer that I liked” because I’ve yet to find something I like. But give me a good Merlot! All of this got me to thinking about how we might turn Test Driven Development into something of a game. There are several people who have already addressed the Gamification of TDD
As you advance in your career, you will inevitably want to improve as a programmer. And as you search the Internet and read various web post on the subject you will also inevitably end up with a bunch of task you should perform that will make you better. For example, if you’ve been following this blog lately, you’ll notice that I’m a big proponent of Test Driven Development. You would naturally expect me to state that to be a better programmer, you should practice Test Driven Development. There has also been a lot of emphasis recently on good basic programming principles like DRY and SOLID. The list could go on. Here are a few you may be interested in experimenting with:
And while all of these and more are good ideas, none of these ideas will actually MAKE you a better programmer. Why? Because becoming a better programmer is mostly about becoming a better person.
At the risk of making half of my audience think I’ve gone off the deep end, I’m going to address a topic that I’ve only recently REALLY begun to understand, in part thanks to Soft Skills.
When I’ve heard the topic of “Limiting Beliefs” come up, it has almost always been in the context of something along the lines of “What the mind can conceive and believe, it can achieve.” Which is easy to disprove. At least it is out of context! I mean really, if I can conceive and believe myself to be a butterfly, it just isn’t going to happen! However, the opposite is pretty easy to both accept and believe. And that’s what I want to talk about today. But even then, it probably isn’t what you are expecting.
Several weeks ago now, I started learning Node.js. Why? Well, for a couple of reasons. First, all the cool kids are using Node.js. Second, I wanted to use Istanbul to get an idea of how well my javascript code is covered by test and that runs under Node.js. Third, Node.js is going to show up in the next version of Visual Studio. And finally, I just like to learn new stuff.