This is the second installment in the series “Do you know what else Sean hates?” Today’s topic, F@#$wad Drivers.

Sean’s words (more or less)

You know what I really hate? I hate f#$@ers that think just because they are on the *on* ramp that they have the f#@%ing RIGHT to merge!! Oh- oh, but you know what I hate even more are those f*#$wads that get into the off ramp lane, pass 5 cars and then try to push their fat asses back into the flow of highway traffic!! f&@#!ing f@$%@wads *I’m* not letting you in! I’ll drive my Suburban right up your fat ass you f#@$ing a#@holes!

And that’s what else Sean hates.

Here’s a useful little re-build and run macro the 4Guys came up with for the .NET IDE.

If you’ve been developing any ASP.NET applications, you may have run into the same frustration that we have with the Application cache. We’ve discovered that the Application cache is not cleared until you rebuild your application (which when you think about it is kind of what you should expect) so often when you are expecting the cache to be empty, it isn’t, leaving you scratching your head until you once again remember, Oh, that’s right I have to rebuild before I run to make sure the Application cache has been cleared.

So since no button exists to rebuild a solution and run in just one single click and we could not find anyone else out there who had already done this work, we created our own Macro in VB.NET and assigned it to a button on our toolbar.

Just add this code to a Macro Module and then add it to a button on the toolbar in .NET and enjoy the one button click to re-build and run a project!


Imports EnvDTE
Imports System.Diagnostics

Public Module UserCreated
    Public Sub ReBuildAndRun()
        ‘Add an event so that we can detect when the solution has completed the rebuild process
        AddHandler DTE.Events.BuildEvents.OnBuildDone, AddressOf AfterBuild
        ‘Rebuild the entire Solution
        DTE.ExecuteCommand(”Build.RebuildSolution”)
    End Sub

        ‘This sub is called once the solution has completed the rebuild process
    Public Sub AfterBuild(ByVal Scope As EnvDTE.vsBuildScope, ByVal Action As EnvDTE.vsBuildAction)
        ‘The Event Handler must be removed to prevent eternal looping since
        ‘the Debugger.Go call causes another build which would then raise the event again and again and again….
        RemoveHandler DTE.Events.BuildEvents.OnBuildDone, AddressOf MyMacros.UserCreated.AfterBuild
        ‘Run the project
        DTE.Debugger.Go(True)
    End Sub
End Module

The Code Room pilot episode was recently released from Microsoft. It is a program designed to show the social, teaming, and technical aspects involved in writing software. Basically, the program takes three developers, places them in a room with a single laptop with limited battery power, hands them a sheet of program specs and turns them loose. The challenge to the developers is to work as a team to turn out a finished project that meets all the original specs provided.

I watched this show fairly excited about the possibilities but came away disappointed and a little angry and the portrayal of developers.

However, I don’t believe in just whining about why I didn’t like something so on my drive home tonight I tried to think about ways I would improve the Code Room (because of course I’m conceited enough to believe that my ideas would be terrific I am an ego maniac after all).

1. Force the developers to be more professional. I don’t want to see sloppy programmers. I work with them everyday and I want to choke them to death with their own crappily written modules. I don’t want to hear jokes about “What! They expect developers to read specs!” That’s not a programmer, that’s a problem and I don’t want a developer like that working on one of my teams.

2. Force the developers to actually use teamwork or at least showcase more of the teamwork. In the pilot episode the use of teamwork was not readily apparent. They did take turns at the laptop but it was not clear what each person was bringing to the project in the form of teamwork. They didn’t argue (much), but it wasn’t apparent, since we can’t read thoughts, how each person was adjusting his or her own personality to work with the other. Maybe add some segments where each developer is pulled away to discuss how they are making themselves more or less useful as a team member and why they are doing that. That way we kind of get a more in depth look at what’s going on in the mind of each developer.

3. Add an external review of their progress from professionals in the field. I think getting the input from industry professionals would be extremely useful and add a more professional feel to what is being accomplished and I think the threat of that analysis might put more of a push on the developers to turn out a little better end product.

4. Evaluate the developers on the end for more then just meeting the specs. Add more categories and have experts in each category critique the work. This would give more insight as to what qualities a professionally developed project should contain. Grade them on interface design, being team players, leadership, design, extra enhancements, usability and low level testing as well as meeting the specs. Let’s see what developers can REALLY do when pushed.

I’m sure I can think of more, but I think those 4 would be a dramatic change for the show and would really transform it into something I would find interesting and beneficial to watch as a developer (plus it’s kind of fitting that 4 Guys From Viewpoint would come up with 4 points isn’t it?).

Anyway, those are some of my ideas. I would love to hear some of yours or any comments as to why my ideas should NEVER be implemented.

Sorry George, I will have to break in on your reign of blogs from afar.

I’ve been hesitant to post as the feelings of loss are so profound since my move. I sigh when I recall the walks, the chess and the overly long but entertaining conversations.

I recently was in the toy section of a local retailer and there, innocently on the shelf, were the very juggling balls that Sean has. I sobbed right there in the isle. They now sit proudly on my desk so others can annoy me as I did so often to Sean (not really, but I wish I had bought them, those are cool!).

I even mirrored Sean in buying a new gas-gorging V8 vehicle. I went one better and bought a spacious new home that is perched on a hill where I can survey the earthly dwellings below. (although there are other homes higher on the hill that do the same to me).

I regularly read 4guysfromviewpoint.com com and neopolean.com to keep tabs on George’s continuing infatuation with Rory. I also have said “that’s stupid” or “no” (with contempt) in meetings when others voice their ideas, always to my fellow employees benefit.

All this in an effort to bring me closer to what I once had. Alas, I am no longer surrounded by such such enviable personalities to emulate and therefore grow….

…ah what the heck, I’ve gat a new house and truck, I see the sun more, and my wife is happy as ever. I guess I will make do living vicariously through the web as the Lost Guy from viewpoint.