Change I can achieve in

 

Well, this post is more of the personal variety, but it may affect future posts in one way or another (however, not like this).  In short, a season of change is upon me.

Big change #1.  I'm getting out of the consulting world for a while.  It's been grand and I've learned a ton about people, business and technology.  But I felt it was time for something different.  Because of the types of consulting firms I've worked with the past 3 years, the one thing I haven't liked is that I never got to work on a team long enough to really get to know the folks I was working with very well.  Seems like just when my team and I were really getting productive together, we'd all get thrown to different projects, usually with folks we hadn't worked with before.  Obviously some of this has to do with the nature of consulting in general, but I'm sure some firms see the value in keeping teams together as much as possible than others.

Big change #2.  Like Chad, I also started a new job this week, for a great product company.  The company is small, which I really like, especially when talking about small development teams.  I'm hoping to learn a lot (drinking from the firehose this week) and be a good contributor along side the other couple developers on the team.  It's an interesting product with some pretty unique challenges to tackle, from what I've seen so far.  I'll be doing mostly ASP.NET work, with maybe a little mobile device stuff thrown in for good measure.

Big change #3.  I'm joining the world of web workers!  Yep, I'm now working from home exclusively.  This might be the biggest change for me in all of this, but I'm very much looking forward to adapting to this type of lifestyle/work environment.  I'm sure I'll have some things to learn, specifically about how to keep things balanced, but so far it's been enjoyable.  Not to mention, it'll help me kick the "eating out" habit that I was stuck in during my traditional office jobs.  :O

So far I'm finding that my reliance on tools like IM, Skype and SharedView (which is pretty decent) just grew exponentially.  I'm looking forward to possibly trying out some remote pairing as soon as I get settled.

To make this post at least somewhat productive, here are a couple tools and a bonus tip that I've been introduced to over the past couple days that you may find useful.

Bonus Tip: I've been a huge Pidgin fan ever since it had that weird Gaim name.  I use it for everything.  AIM, Yahoo, GTalk, IRC, Twitter.  One tip that I learned today is how to set up Pidgin to "auto join" you to a particular IRC channel as soon as you login into Pidgin.  Here's how to do it...

  1. Click Buddies > Add Chat
  2. Choose your IRC account/server from the Account drop-down
  3. Type the name of the channel you want to join
  4. Give the chat an alias (I just used the channel name)
  5. Click Add
  6. Now find that new chat in your list of buddies, Right-Click > Auto-join
  7. That's it!

So now when you fire up Pidgin, it'll automatically join you to that room.  Most of you may already know about this, but I thought it was pretty cool.

Anyway, until next time.  I have a lot of things to blog about in the hopper.  Hopefully I can get around to them sometime soon.  *sigh*

Scribbish Skin - For Subtext

 

This is long overdue, but Nick Parker asked me a long time ago (sorry Nick) where I got the skin I use for my blog and I told him I'd make it available.  I actually ported it myself from the existing Scribbish theme that was already available for Mephisto, Wordpress and others.  I really liked the simplicity of it so I just grabbed the CSS and hacked away at it myself until I got it looking close enough as a Subtext skin.

I submitted it to the Subtext skins showcase, but it may take a bit for it to get approved.  So for now, you can just download it from here.

I kind of put this together in a hurry, so please let me know if you find any problems with it.

Enjoy!  :)

ActiveSupport.NET - Namespace Overhaul

 

Figured I'd try and get this nailed down as early as possible.  So after some recent feedback, I decided to change the namespacing so that it focused more on "behavior/concern" rather than "types".  What this means is...

Instead of:

  • using ActiveSupport.Core.Extensions.String;  // containing string extensions for access, conversions, etc.
  • using ActiveSupport.Core.Extensions.Integer;  // containing integer extensions for access, inflections, etc.
  • ...

It's now just this:

  • using ActiveSupport;  // just basic extensions
  • using ActiveSupport.Access // all accessor-based extensions for ALL types
  • using ActiveSupport.Conversions // all conversion-based extensions for ALL types
  • ...

I'm pretty much thinking the accessor based stuff will probably get used the most.  But either way, by grouping this way, I'm hoping they'll be a bit easier use.  And of course when our R# 4.0 EAP shows up next (right Ilya? :) all of this namespace'ry will must magically work for us.  :)

What do you think?  Is this a better approach to keeping things clean and organized?

ActiveSupport.NET - Update

 

So it seems there is some interest in getting something like this up and running.  I went ahead and did some of the basic "project setup" type tasks.  Here are some links of interest...

I look forward to some more discussions about the best way to structure things to make it easy to use.  On the google code project site you'll find a brief description of the project as well as a wiki page I've started to give some basic info on how the code base is structured (tools, build targets, etc...).  I'm sure all of this will change/evolve as things progress.

And thanks Joe (for already submitting the first patch) and others that have said they want to get involved.  Should be fun...  :)

Introducing ActiveSupport.NET

 

To my surprise, none of my googling seemed to come up with anyone doing this.  So I figured I'd start it off (please let me know if you know of any other efforts already underway).  As some would say, taking extension method abuse to a whole new level.  :D  But, I see these little utility methods to be a good fit as extensions methods to make the syntactic sugar that much sweeter.

One of the many great things about working in Rails is the core extensions in the ActiveSupport library.  It just *becomes* part of the Ruby language as you work with Rails.  And I wanted to get that same feeling when working in C#.  So this is my attempt to start porting over the core extensions from Ruby's ActiveSupport Library.

So far I've just ported over a few string access and conversion extensions, but check 'em out and let me know if you'd find something like this to be useful.  Here are some examples of what's currently supported...

 1: // some accessors
 2: "blah".At(2) // 'a'
 3: "blah".First() // 'b'
 4: "blah".First(2) // "bl"
 5: "blah".From(1) // "lah"
 6: "blah".Last() // 'h'
 7: "blah".Last(2) // "ah"
 8: "blah".To(2) // "bla"
 9:  
 10: // couple simple conversions (still needs lots of work)
 11: "1/4/2008".ToDate() // DateTime
 12: "01:15:35".ToTime() // DateTime

You can grab the source at its google code repository.  You can just do a "build test" from a command line in the trunk to run the unit test suite.

Enjoy.  :-)

CIFactory.Create(RichmondDNUG);

 

Jay Flowers came down to our humble Richmond DNUG tonight to talk about Continuous Integration and his rockin' open-source product, CI Factory.  It was a great demonstration of how to get a very robust automated build server up and running in literally minutes.  Having set up quite a few automated build and CI environments myself over the years, I have a great appreciation for all the hard work that's gone into a product like CI Factory. 

So I'm looking forward to leveraging CI Factory in my future CI server implementations (which will hopefully be soon!)

Oh and some of the cool stuff he's done in extending CCNet and NAnt was pretty impressive as well.  Not to mention the extension of NCover to drive and generate code coverage for WatiN tests.

So if you need CI (and trust me, you do), then download CI Factory and check it out.

I Do What?

 

Ok, so I know I'm crazy late on this one, but things have been a bit hectic recently.  And I'm not even talking about holidays.  But since our newly knighted member at LosTechies has chimed in, I guess it's about time I did too in response to Jason tagging me.

A Little History

Yeah, I know.  I always hated history in school too, but bear with me.  I'll just give a brief (hopefully) paragraph on the past couple years to help illustrate what I'm currently doing and why. 

It's April '05 and I've got a really good corporate job as a lone software developer managing and building intranet-based ASP.NET web applications.  Decent salary, great benefits, short commute, generally low-stress.  Well, I had pretty much hit the "technical" glass ceiling (not wanting the "management" track) and had the desire to work with teams of other, more experienced, developers.  So I took a pay cut to go work for a small, but well established software consulting firm in May '05.  (BTW, make sure you always factor in health insurance costs when weighing a decision like this.  That was stupid mistake #1 which ended up costing me dearly.)

So there I was in the consulting game and learning and growing by leaps and bounds.  I had already long embraced OSS as a viable alternative to the Redmond standard.  Which made for some interesting internal debates and experiences considering they were a "Microsoft Certified Managed Gold Partner".  Anywho, I cranked away at various internal and external client projects for a couple years, getting to work with some great folks including my boys DP Bullington and Paul Laudeman.  With their help, I tried to help introduce some agile engineering practices onto our projects (TDD, CI, DDD, etc.).  We all spent a year on-site with a particular client trying to introduce Scrum on 4 projects simultaneously, which turned out to be quite a mess, and in my opinion, an overall failure.  I mostly attribute that to poor leadership and lack of experience on our my part (only speaking for myself).  Nevertheless, in the 2 years I worked at that consulting firm I learned a TON technically, but more importantly, personally in how to deal with people and some of the ins and outs of the software consulting business in general.

Ok, so maybe that wasn't as brief as I thought.  Sorry.

Here And Now

So, ironically, in April of '07 I found myself once again at a kind of crossroads.  After a year of spending ~2 hours a day on the road back and forth from the last client for which I worked, along with the fact that I was just generally not happy with how things were going, I accepted an offer from another, much larger, consulting firm.  This new firm, which, among other things, had much better benefits, shorter commute and was a "hybrid" shop (unlike the previous firm, which was 1 Microsoft Way or the Highway).  So overall, I felt pretty good about the move.

As I've continued down this path as a software consultant, I've grown more and more passionate about delivering quality, maintainable software to clients.  I know, who would disagree with that, right?  Well, in words, probably no one.  But in deeds and practices, that's another story.  Suffice it to say, I'm continuing to try and raise the bar, both for myself and for those I work with to ensure that we are serving our clients in the best way we know how.  Which is by giving them solutions that benefit the business and that don't break and doing so without working crazy amounts of hours.  Sometimes I wonder if I take my job as a consultant too seriously, which is perhaps due to my passion for the craft of building software.

What's Next?

Well, so far, I'm finding Richmond to always be playing catch up with some of the other markets like Austin, Calgary and Philly with regards to adopting a more lean development process and engineering practices.  But this is where the Lord has us right now and that's all I need to know.  I am looking to possibly start accepting some presentation opportunities, first internally at my current firm and also at Code Camps, DNUG meetings and screencasts.  I'm still new to all of this, but hopefully the more I do it...well...you know.

Oh, almost forgot to mention my recent interest in Ruby (and of course Rails).  I was really fired up a few months ago and even started "chapter blogging" my way through my first Rails book.  Unfortunately, that was somewhat quenched by my work load at the "day job".  I still have an iron in the Ruby fire, and am hoping to get that ramped back up again soon.  Along with helping to build the LosTechies community and possibly help out on an OSS project or two.  Yeah, not sure where I'll find the time.

On a side note, I'm hoping to start distancing myself away from the "dotnet" part of my persona, if you will, of "joeyDotNet".  Mainly because I believe in choosing the best tool for the job at hand and sticking my name to a particular technology was probably a naive move on my part in the first place.  Anyone have any thoughts on how to actually go about doing something like this?

Tools Of The Trade

Looks like other folks are listing out some of the tools they use.  Well, of course, ReSharper has to be at the very top of my list.  I honestly will NOT use VS without it.  And you probably already know of my fondness of MonoRail which I've used for almost a couple years (I think) on various projects, back when ASP.NET MVC still meant Make Views Chief (Which sadly, most legacy projects I have to work on still embrace).  Of course others like MbUnit, Rhino Mocks, Windsor, TDD.NET and NAnt are also important tools in my box of goodies.

Wrap It Up, Will Ya? *yawn*

Ok, so that's probably more about me than you ever wanted to know.  But if you want to contact me regarding presentations, work, or just to say hey, you can find me here as well as LinkedIn, Facebook and occasionally Twitter.

Just like being there...almost.

 

Unfortunately I haven't been able to make it to any of the jazzy conferences in 2007.  There are a few that I would've really liked to have attended; altnetconf, DevTeach, RailsConf and RubyConf to name a few.  Luckily, you can find quite a bit of the content from some of these kinds of conferences online.  Just tonight I watched a really good presentation from RubyConf 2007, Behaviour Driven Development with RSpec.  There are many more I'd like to watch from RubyConf if I can find the time.  And of course the awesome MVC video from ScottGu himself at altnetconf is a must see.

So for those of you, like me, who for whatever reason can't make it to some of these conferences, here are a few good places to start:

  • Confreaks (these guys do an awesome job, giving you widescreen videos with the slides/code side by side with the presenter)
  • ScribeMedia (where I originally watched the RailsConf 2006 stuff)
  • Parleys (saw an awesome DDD video here once)
  • Google Videos (of course)

I'm sure there are many more, so leave a comment with some more good post-conference resources if you know of any.

(Hopefully my ability to join in the conference goodness will be a bit better in the coming year)

MonoRail Quickly - Screencast

 

Update: Zip file links have been updated due to the first one being corrupt!

Well it was bound to happen at some point.  My first screencast.  It's a quick walkthrough on how you can get a baseline MonoRail solution up and running.  Yeah, I know.  Everyone's talking about MS MVC these days, and I'm certainly just as excited about it as anyone else.  But MonoRail is still a very nice MVC framework that can be fully leveraged now. 

So I thought this screencast along with its accompanying zip file might help folks interested in MonoRail, or just ASP.NET MVC frameworks in general, to get one up and running quickly with everything you need (including an automated build script).

Let me know what you think!

(Thanks to my fellow LosTechies crew for hosting the screencast for me.)

Happy Coding!

Random Thoughts On Humility and Perfection

 

(Sorry for the recent codeless posts, but these are just some of the things I've been thinking about and dealing with recently)

As I continue down this road as a software consultant (still with a consulting firm), I find myself working more and more with other consultants who are considered "senior", which for some reason includes myself.  I'm starting to see that this can be one of the biggest roadblocks to change and one of the biggest producers of fear on a team.  At least speaking for myself. 

"We're 'Senior', We Don't Need No Stinkin' Code Reviews"

This is the kind of mentality that, though common, is pretty unfortunate.  We all know code reviews have been abused over the years, but does that really mean there is no benefit in "having a 2nd pair of eyes", as they say?  Isn't this still a powerful way to learn and grow a team's skills? 

But this post is not about specific practices like code reviews.  The greater point I'm trying to make is this:  Is it possible for us all to put down our "senior" statuses and strive for perfection as a group of passionate developers without the fear of offending each other?  I'm not sure this is completely achievable as long as we're all allowed to have opinions, but it certainly sounds like a nice goal. 

Even though perfection is unachievable, I want to get as close to it as I can.  Both, in my walk with the Lord and in my craft as a software developer. 

One of the main benefits I see to all this ALT.NET stuff is that when a group of developers (notice I didn't say "senior developers") can get together and critique each other's ideas in a constructive way that actually leads to overall improvement and learning, then I'd say that's a huge leap in the right direction.

"Now Let's Not Get Crazy And Actually Try To Improve Our Code"

Fear quenches the ability to improve.  If Joe Developer is afraid to make a suggestion to another developer or his team because he's afraid of either a) someone getting offended and/or b) someone biting his head off, then chances are that the team's overall skills are pretty stagnant and their ability to improve is severely limited.  Fear can also come from working with unwieldy code bases.  When everyone on the team is afraid to change anything because they don't want to break something, then you've got some serious changes to implement.  I'm starting to go through this process now on a couple of my current projects.  One baby step at a time.

"We're Too Busy To Learn Fundamental OO Principles And Practices"

Well, like a good friend of mine told me recently, "you're gonna pay for it somewhere".  Either through lots of pain in the ongoing maintenance of poorly designed software or in the investment into your team to learn/teach better ways of building software in the first place.

Now that I've pretty much "settled in" to my new consulting firm, I'm going to really start spreading the knowledge that I have (what little that is) to try and build up the teams I work with as much as I can and perhaps encourage others to do the same.  Because I know that ultimately by doing this, I'll end up learning much more from other folks that I could possibly teach them.

The end goal of course being that the clients we serve are getting the highest quality work possible.  But more on that in another post...  ;)