Thursday, May 22, 2008

I had a chance to see David Chappell speak at the Microsoft offices in Downers Grove this past week. If he is coming anywhere near you to talk on Software + Services, I recommend that you go see the talk. I've got a summary of what he covers here, but you've got to see him in person to get the talk. The man is an amazing communicator and helped me connect some dots that I hadn't quite connected in a while—whether that was due to sloth on my part of great speaking on David's part, I don't knowJ.

Anyhow, here's a few hundred words explaining some of what I got out of it.

Training Date: May 20, 2008, 1-4 PM

Location: Microsoft offices, Downers Grove, IL

Presenter: David Chappell, http://www.davidchappell.com/

Summary

The reliability of the Internet, relatively low cost of connectivity, and widespread presence of high bandwidth connections has provided a path for application architectures to evolve. Specifically, this set of changes allows application vendors to provide common applications to end users. Today, these common applications include e-mail, CRM, storage, web site hosting, mapping (ex. 1 Main St., Mundelein, IL), and database hosting. Providers host these services on the Internet, also called the 'cloud' by the software services community. These services commonly provide the following features:

  • Data mobility: Consumers own their data and can change providers or move the data in house as needed.
  • Application integration: The service in the cloud is part of a larger application used at the enterprise.
  • Application customization: The service in the cloud may allow the consumer to customize the application to handle special business needs.

Two terms describe the different business models for the services in the cloud: Software as a Service, SaaS, and Software + Services, S+S. SaaS offers a complete software package in the cloud. SaaS instances may allow for integration and customization. SaaS does not provide much of a role for corporate IT departments outside of application development. S+S describes a hybridization between today's common model of self-hosting applications and the SaaS world. SalesForce.com offers an example of a SaaS application. SalesForce.com manages all the data, the application uptime, etc. An S+S example is a bit more involved, but probably more common for businesses as it allows for control of the perceived competitive advantages of a business.

S+S includes the types of applications that use cloud services as well as custom, in-house services. For example, a business could host Exchange Server locally but make use of a service provider to handle advanced Exchange functionality such as Outlook Web Access, web calendaring, or discussion lists.

With terminology and ideas covered, what else does a business need to look out for? The business should evaluate the service provider in the same way that they would evaluate a packaged, installable software. Beyond that the consumer needs to decide if the service meets their needs.

In both packaged software and services, one must look at how the vendor is trying to lock in the consumer. This lock in happens in different ways. They may lock down data, making it difficult to move to a new vendor. They may also create a platform type of lock in. The platform lock in can cause many different kinds of problems. If the lock in is through the tooling and programming languages, a consumer may find it difficult to port customizations to equally good platforms. Likewise, it may prove difficult to find reasonably priced developer talent. For example, SalesForce.com uses the Apex programming language. Apex is specific to SalesForce.com and isn't commonly available elsewhere. Other tools, like Microsoft Dynamics CRM and Google Apps, use common extension languages, allowing for a larger developer pool. Microsoft Dynamics uses .NET based languages and Google Apps uses Python.

5/22/2008 7:35 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Tuesday, May 13, 2008

I have a friend who teaches Computer Science. One of the things we've discussed is the need for students/entry level hires to really understand basic data structures. This is true even though most popular languages do the basic ones quite well (linked list, hashtable, queue, stack). A consequence of these things being in most languages is that many of today's students aren't being required to actually build these data structures as part of their education. Many problems in the work place involve situations where one needs to know the characteristics of the data structure in order to implement the most efficient algorithms. One acquires this knowledge through actually building the data structures at least once.

I believe that many of the folks who grew up programming for the web are getting to a point where their script skills will need to fill in these gaps in their education. Browser apps are approaching desktop applications in terms of presentation, interactivity, and capability. The next step in the evolution of browser applications will require developers to have knowledge of the basic data structures and their variance implementation options. The reason: unlike the desktop languages we all use, the browser's programming language, JavaScript, doesn't have any of these. (If I'm mistaken, let me know!)

Right now, I'm reviewing the data structures and algorithms that I learned during the first two years of college. I'm also trying to bring myself up on my level of understanding JavaScript. I think that some of these diversions might prove interesting to the world at large. Today, I've implemented a linked list. A linked list has the following characteristics:

  1. Add at the front or end of the list takes O(1) time.
  2. Extraction of the nth element takes O(n) time.
  3. Insert at a given position, k, takes O(k) time.
  4. Delete at a given position, k, takes O(k) time.

Linked lists are effective when typical usage of the list is in scanning all elements. A linked list is 'nice' to memory management. That is, the room needed for the list + one more linked list node is:

Z = (size of node) = ((size of data) + (reference to next node))

(total memory in use when adding a node) = Z x (number of nodes + 1)

This is an improvement over the typical JavaScript Array type whose worst case characteristics for adding one more element to the list is

Z = (size of node) = (size of data)

(total memory needed when adding a node) = Z x ((2 + growth size) x number of nodes)

In many algorithms for array growth, the algorithm calls for a doubling of the array's allocated memory. The reason that so much memory is required is that arrays require contiguous memory in order to maintain O(1) lookup time at any given element.

A Doubly Linked List Implementation

A doubly linked list is a list that one can use to go both forward and backward from one node to the next. To accomplish this, I've created three classes:

function LinkedListNode() {

}

 

LinkedList.LinkedListNode = {

Data: null,

Next: null,

Previous: null

};

 

LinkedListNode keeps track of the data, the Next, and the Previous nodes. The algorithms involved all assume that the linked list Next and Previous members will only be other LinkedListNodes or null.

function LinkedListIterator(){}

 

LinkedListIterator.prototype = {

_current: null,

Current: function() {

var retval = null;

if (this._current != null)

{

retval = this._current.Data;

}

return retval;

},

Next: function() {

if (this._current != null)

{

this._current = this._current.Next;

}

return this._current != null;

},

Previous: function() {

if (this._current != null)

{

this._current = this._current.Previous;

}

return this._current != null;

},

HasData: function() {

return this._current != null;

}

};

LinkedListIterator allows one to go forward and backward within a LinkedList. The iterator can become invalid when it runs off the front or back of the LinkedList.

function LinkedList(){}

 

LinkedList.prototype = {

_head: null,

_back: null,

_length: 0,

Add: function(data) {

var newNode = new LinkedListNode();

newNode.Data = data;

if (this._head == null)

{

this._head = newNode;

this._back = newNode;

}

else

{

newNode.Previous = this._back;

this._back.Next = newNode;

this._back = newNode;

}

++this._length;

return newNode;

},

RemoveAt: function(index) {

var currentIndex = 0;

var nextNode = this._head;

while (nextNode != null && currentIndex < index)

{

++currentIndex;

nextNode = nextNode.Next;

}

if (currentIndex == index)

{

nextNode.Previous.Next = nextNode.Next;

if (nextNode.Next != null)

{

nextNode.Next.Previous = nextNode.Previous;

}

}

return nextNode;

},

Length: function(){

return this._length;

},

InsertAt: function(index, data) {

var currentIndex = 0;

var nextNode = this._head;

var newNode = new LinkedListNode();

newNode.Data = data;

 

if (index == 0)

{

// Insert at head

if (this._head == null)

{

this.Add(data);

}

else

{

newNode.Next = this._head;

this._head.Previous = newNode;

this._head = newNode;

++this._length;

}

}

else if (index >= this._length)

{

// Add to the end.

this.Add(data);

}

else

{

// Insert in the middle

while (nextNode != null && currentIndex < index)

{

++currentIndex;

nextNode = nextNode.Next;

}

if (currentIndex == index)

{

nextNode.Previous.Next = newNode;

newNode.Previous = nextNode.Previous;

newNode.Next = nextNode;

nextNode.Previous = newNode;

++this._length;

}

}

return nextNode;

},

GetIterator: function(){

var retval = new LinkedListIterator();

retval._current = this._head;

return retval;

}

};

Finally, this is the linked list data structure. It allows you to insert at a given location, remove a given item, add an item to the end of the list, and can create a bi-directional iterator to allow you to walk the list from front to back and to the front again. Since I'm a Windows guy, I tested out the structure using cscript.exe.

function DisplayList(list)

{

var iterator = list.GetIterator();

if (iterator.HasData())

{

do

{

WScript.Echo(iterator.Current());

}while(iterator.Next());

}

}

 

 

function TestLinkedList()

{

var list = new LinkedList();

list.Add(15);

list.Add("Hello, World!");

WScript.Echo(list.Length());

DisplayList(list);

WScript.Echo("---");

list.InsertAt(1, new Date());

DisplayList(list);

WScript.Echo("---");

list.RemoveAt(2);

DisplayList(list);

WScript.Echo("---");

}

 

TestLinkedList();

If you need a refresher on linked lists and their variants, Wikipedia has a good write-up that I won't repeat here.

 

5/13/2008 10:19 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Thursday, May 01, 2008

In case anyone in Lake County, Illinois/Kenosha County, Wisconsin reads this blog, I'd like you all to know that the LCNUG group is already gaining momentum. To give some people an idea of how fast things can move, I'd like to take some time to explain what is going on. I'll post (when I remember to do so) about what is going on with the group and how we are doing as we go through our gestational phase.

The first thing I did was pick a 'dream venue'. In this case, I wanted a local location with great parking, centrally located, and with space to host a largish group. The local community college was my first choice. I sent a message to the head of the CLC Computer department who put me in contact with their .NET instructor, John North. John and I talked about what a .NET User Group is, when they meet, etc. He then worked with his department and got us a location. CLC has a charter that includes working with the community. His department used this reasoning to get approval for the LCNUG to meet on the last Thursday of the month for every month except November and December (dates are November 20 and December 18 in these cases). Once this was done, I set out to contact the local developer community so that we could have some attendees at our first meeting.

In the process, I found out that another local programmer, Tim Stall, had just started meeting with his coworkers for the same reasons as me—driving to downtown Chicago or Downers Grove is a bit far for folks who work in Lake County. Tim and I found each other by contacting our local Developer and Architect Evangelist. At this point in time, that's Dave Bost and Larry Clarkin. Dave and Larry made sure that Tim and I got on the same page. They also looped in Keith Franklin, who runs CNUG, so that we could get linked from their site. This all happened over the course of a few hours. I've also got people sending me messages and asking to help out.

Why do I bring this up? I thought that anyone else looking to start a .NET Users Group would be interested in finding out what does it look like from the time one says 'we need a group in this area' to actually getting a group together. I started the process when I contacted CLC on April 17, 2008. At this point, I've got the following things 'done':

  • Scheduled a venue through the end of the year
  • Contacted Microsoft
  • Setup a web site
  • Setup an account on CodeZone.
  • Setup an account on INETA. FWIW, their 'register a .NET user group' form is busted. I'm looking for alternate ways to register. Fortunately, I have some avenues to investigate.
  • Have some feelers out for sponsors.

Doing this isn't too hard. Like I said, I'm also starting to get help from others. I don't want this to be the 'Scott Seely' show. I want a group where I and other like me can learn and socialize.

I'll let you know how everything works out.

5/1/2008 8:36 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Monday, April 28, 2008

I want to take a few moments to announce the formation of a .NET Users Group in Lake County, Illinois. Our first meeting will be at CLC in Grayslake, IL. I'll be the inaugural speaker giving a beginner level talk on Windows Workflow. For details, please visit www.lcnug.org. If you plan on attending, are interested in sponsoring, or have questions, feel free to contact me (scott at scottseely.com).

4/28/2008 7:04 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Wednesday, April 16, 2008

Today, I had to debug a strange problem. We have a web application that does some fancy printing. The main application server is a Unix machine, the print component lives on Windows. The network between these two has all sorts of fun firewall rules that HTTP type requests can navigate so long as the proxy on the machine is setup correctly. Unfortunately, the Windows test box didn't have the proxy setup correctly and I didn't have easy access to the one account that runs the service. To make the proxy set for all users, I had to ask my good friend, Google, how to do this. Google answered "Change the default connection policy for all users." Google didn't explain how to do this very nicely (what a jerk!).

I then thought that maybe Google didn't have the whole answer in one place. (not a jerk!) So, I asked Google "How do I set the local policy on a Windows 2003 server?"

Google answered, "Start-->Run-->gpedit.msc". Cool, gpedit.msc is the name of the Group Policy Editor and it is a Microsoft Management Console plugin (yeah, you can get all that info from the filename if you live in Windows long enough-- I've in some sort of Microsoft DOS/Windows mode since 1984).

From there, I just figured things out. So that you too can benefit from my digging, here is the info:

  1. Navigate to User Configuration-->Windows Settings-->Internet Explorer Maintenance-->Connection
  2. Double click on 'Proxy Settings'
  3. Set your proxy.

These settings then get applied to all users, including those whose passwords you can't recall:) For what it's worth, this also works on Windows XP. I haven't tried Vista, but I bet the results are the same there too.

4/16/2008 12:40 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Thursday, April 10, 2008

I was checking out the ads for the local office supply and electronics stores during my lunch hour and I saw that Office Depot was selling the ViewSonic VX2235wm for $259-- the same price as I paid for the hunk of junk Samsung. I plugged it in to my laptop and IT JUST WORKED! Everything is crisp, clear, perfect!

The installation experience went like this: I plugged in the monitor to power and my laptop. Vista asked me if I wanted the display on the left or right of my primary display (right) and then I was in business. This is NOT what happened this weekend with the Samsung.

So far, I've adjusted nothing on the monitor. I'm so HAPPY that this thing works. ViewSonic is just a better monitor manufacturer.

One other thing-- my 1st grader, Angie, introduced me to Pivot. Here's a nose picking, butt scratching stick figure that I created tonight to get a laugh out of the kids.

4/10/2008 6:28 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 

This last weekend, my wife bought a 21.6" Samsung SyncMaster 223BW monitor for me for my birthday (happy 36th to me!) so that I could bask in dual monitor goodness when working on projects at home. I attached the monitor to my PC over the analog hookup (because I don't have an digital port available on my laptop). I know this port to be very good for other projectors. I used this laptop to teach at a number of locations over the past few years and have never had a problem when connecting to a fancy overhead projector. It worked great on several projectors at Microsoft when I worked there, it worked fine when I taught for Wintellect last year, so I know this wasn't the issue (though I did think 'hmm-- could the port be goofy?').

The images I got from the monitor were crap. I tried every adjustment, got the latest drivers for the monitor, etc. I just couldn't get the monitor to generate clear, crisp text. For someone who processes lots of code when sitting at a machine, this was an absolute deal breaker. If you do get one of these monitors and plan to use an analog (D-SUB 15) connector, then just pick something else. Right now, you can pick these things up at Sam's Club for about $260. Mine goes back today.

I think I'm going to go with a ViewSonic-- I've always been happy with their stuff though I never like the fact that I have to pay extra. Hopefully, I'll have a good experience to post about for that one tomorrow.

4/10/2008 9:59 AM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Monday, April 07, 2008

Florin Lazar has an interesting post on using C# 3.0 to make writing transaction blocks a little 'pithier'. In 'A Simpler TransactionScope', he suggests using a delegate and a lambda expression to accomplish his goals.

transacted(()=>
{
   using (SqlConnection connection = new SqlConnection(connectionString))
   {
      connection.Open();

      SqlCommand command1 = new SqlCommand(commandString1, connection);
      command1.ExecuteNonQuery();

      SqlCommand command2 = new SqlCommand(commandString2, connection);
      command2.ExecuteNonQuery();
   }
});

delegate void TransactedCodeDelegate();
void transacted(TransactedCodeDelegate txCode)
{
   using (TransactionScope ts = new TransactionScope())
   {
      txCode();
      ts.Complete();
   }
}

The thing that bothered me about this is, can't I approach this using C# 2.0? And, yes, I can!

transacted(delegate()
{
   using (SqlConnection connection = new SqlConnection(connectionString))
   {
      connection.Open();

      SqlCommand command1 = new SqlCommand(commandString1, connection);
      command1.ExecuteNonQuery();

      SqlCommand command2 = new SqlCommand(commandString2, connection);
      command2.ExecuteNonQuery();
   }
});

In case you are missing the change, Florin suggests using ()=> (4 characters) and I suggest using delegate() (10 characters). Otherwise, these are identical. They both use an anonymous delegate to get the job done.

I'm not suggesting that Florin's method is flawed. I'm just suggesting that folks who still use VS 2005 in their day to day job can pick up this trick without an upgrade.


4/7/2008 9:24 AM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Sunday, March 16, 2008

I just want to test the Windows Live Writer.

Some code:

   1:          static void ListEm<T>(IEnumerable<T> vals) 
   2:          {
   3:              new List<T>(vals).ForEach(a => Console.Write(a.ToString() + ","));
   4:              Console.WriteLine();
   5:          }
3/16/2008 2:50 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Thursday, March 13, 2008

Scott Hanselman put up a post showing some nifty LINQ code. I've been dabbling with it a little here and there, trying to see what it gave me. I like the new way of declaring member variables:

int _age;

public int Age

{

get { return _age; }

set { _age = value; }

}

 

is fairly verbose, and it doesn't add any real value for readability. So, I'm a huge fan of this:

public int Age { get; set; }

 

which is identical in the eyes of the compiler, but way better for doing a code review.

I also like the vanishing need to add properties and appropriate constructors. I like being able to write

new Person(){Age = 11, Gender=Gender.Male, Name="Vince"}

without needing to write something like this:

public Person(int age, Gender gender, string name)

I also like the simpler lambdas and other expressions. So, tonight I finally put together all the different basic features and had this running:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Collections;

 

namespace LinqStuff

{

enum Gender

{

Male,

Female

}

 

class Person

{

public int Age { get; set; }

public Gender Gender { get; set; }

public string Name { get; set; }

 

public override string ToString()

{

return string.Format("{0}: {1}: {2}", Name, Age, Gender.ToString());

}

}

 

class Program

{

static void Main(string[] args)

{

var people = new List<Person>(new Person[] {

new Person(){Age = 11, Gender=Gender.Male, Name="Vince"},

new Person(){Age = 6, Gender=Gender.Female, Name="Angeline"},

new Person(){Age = 5, Gender=Gender.Male, Name="Phillip"}

});

var boys = from a in people where a.Gender == Gender.Male orderby a.Name select a;

people.Add(new Person() { Age = 37, Gender = Gender.Female, Name = "Jean" });

 

ListEm<Person>(boys);

 

people.Add(new Person() { Age = 35, Gender = Gender.Male, Name = "Scott" });

ListEm<Person>(boys);

}

 

static void ListEm<T>(IEnumerable<T> vals)

{

new List<T>(vals).ForEach(a => Console.Write(a.ToString() + ","));

Console.WriteLine();

}

}

}

 

The coolest thing here? My wife is learning C#. She took one look at the code and was able to instantly see that boys would automatically update as the people collection changed. The syntax passes the 'is it instantly grokkable' test for my sample audience of 1. I do like the fact that this syntax does focus more on what I want done instead of having to prescribe how to do it.

3/13/2008 9:43 PM Central Daylight Time  #    Disclaimer  |  Comments [0]  | 
 Wednesday, February 27, 2008
Did you know that you could run a simple, effective home with your Web surfing, telephone calling, TV watching, machine backups, book writing, code editing, music listening, game playing life, all on Microsoft products and all for a reasonable price? Over the next several posts, I want to cover how my family is using Microsoft technology to make our lives better. Today, I want to give a brief description of the home network.
2/27/2008 9:08 PM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Friday, February 15, 2008
Just some random thoughts while reading the news over lunch. Nielsen Rating apparently released their numbers for websites for January 2008. According to the numbers reported at http://blog.seattlepi.nwsource.com/venture/archives/131937.asp, Google got the most eyeballs in January. What I find interesting is that the numbers for time spent on the web site implies a different ranking. I whipped out Excel for some simple analysis. The results? The top 4 companies in terms of eyeball hours are in the exact wrong order. Companies are presented in order of unique audience #s, measured in thousands (000). I added the 'Person Hours/1000 people' and 'Rank on Person Hours' columns.
2/15/2008 12:33 PM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Tuesday, February 05, 2008

Usually, FSB is entertaining. Today, the guy running the FSB blog is hilarious. The post isn't much until the last line. I won't spoil this for you but, if you have 30 seconds, go here now and read. Hilarious!

2/5/2008 8:11 AM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Monday, February 04, 2008
I don't think that buying Yahoo is a good thing for Microsoft. Instead, they should continue to out innovate their competition. One thing that has been a weakness for Microsoft recruiting has always been that they can't get many great developers. Really, really good developers can work wherever they like. If they prefer to live near family over Redmond, they typically tell Microsoft 'no' when asked to join the firm. Others, like me, say yes and then eventually decide to leave because one can't develop Microsoft product outside of their core development centers (Shanghai, China; Bangalore, India; Cambridge, England; Fargo, ND, USA; Silicon Valley; and Redmond, WA, USA). They avoid the many big cities that have first rate developers. My short list for new development centers in the USA is as follows:
2/4/2008 9:39 PM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Wednesday, January 30, 2008
I have had the pleasure of spending the last few days improving application performance. Specifically, my job is to improve the 'speed' dimension of the application. In doing this, I've been getting reacquainted with some well used tools: SQL Query Analyzer and dotTrace Profiler. (For those of you familiar with when SQL Query Analyzer was last available under that name, I'm working with a completely functional, happy, SQL Server 2000 installation.) It's been quite a few months since I last did this. Given that not many people get a chance to do performance analysis and improvement on a regular basis, I think that now might be a good time to rehash some common mistakes and the way to fix those mistakes.
.NET | Performance | SQL
1/30/2008 7:15 PM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Sunday, January 20, 2008
I have a sickness. My illness causes me to skip sleep, to skip meals, and to allocate no time to play video games. Occasionally, enablers have given me money to encourage me to indulge in this illness. I have no interest in getting ‘help’. I am an author and I write about technology topics. ...
1/20/2008 9:45 PM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Monday, January 14, 2008
Tony Baer has an interesting post at http://www.onstrategies.com/blog/?p=251, 'SOA in a Recession?'. The question here is 'what will SOA investments look like during a recession?' Having been a part of the big client server moves of the mid to late 1990s, web deployments of 1997 to the present, and someone who has done training on SOA across the country for Wintellect, I have to say that SOA feels different from the previous two items. For client server, we had to start thinking about our applications differently. Bits of the application lived in different processes on different machines. Here, we had to rearchitect applications to deal with a new security model and to deal with the greater latencies involved in method and database calls.
SOA
1/14/2008 6:07 AM Central Standard Time  #    Disclaimer  |  Comments [0]  | 
 Saturday, January 12, 2008

My blog is back up and running. Expect lots of stuff on WCF, .NET, and other things that interest me.

1/12/2008 7:55 AM Central Standard Time  #    Disclaimer  |  Comments [0]  |