First, I'd like to apologise for not updating my blog for just over a month now. It's been a very busy time for me with work and lecturing a course (which is what this blog post is about). I plan to continue updating my blog at least once a week from now on regardless of how busy my life gets. 

Well, as I've already indicated, I've been lecturing on a topic of Windows Forms Development in .Net 2.0 at the UTS (University of Technology Sydney) for just over a month. This is something that I've never done before....lecturing in front of 25+ students and all of whom I see as my peers. It was and still is a daunting task to get up in front of this class and talk.

The first night was quite a buzz but it wasn't like that for the entire night. At the start of the session I was so nervous that I was having difficulty talking due to my mouth being so dry. After about 30 mins. I began to realise that the people I was talking to were actually listening to me and that I was 'meant' to be there for them to listen to. It was the revalation that I needed for me to start to relax.

Yes, after that first 30 minutes of stressfully forcing out my words I began to relax. I can tell you that the first 30 minutes felt like hours and looking directly at the faces listening to me wasn't helping. Eventually I noticed that some of those faces were nodding, some had puzzled looks about them and others were just listening....just listening. It was then that I understood that I was simply talking and passing on knowledge to others prepared to listen. I began to look at each of those faces as individuals instead of as a crowd. What I mean is that each face I saw was to me a single person that I was having a conversation with (a one-on-one chat with a co-worker). I started directing my words to just a couple of people and that really helped me to focus and relax. As the night progessed I expanded my horizons by including many more faces into the conversation. By the end of the night the students were asking some really great questions and it was a great feeling to be asked those questions and even better to be able to answer them. I was on a high by the end of the night and was really looking forward to next week's session (could this be my True Calling?). To date I have lectured only 6 classes and each time I have had some initial jitters but nothing like the first night. I have found each subsequent class easier to do and each experience has been unique and enjoyable.

Each session has required me to do A LOT of study and research into what the lecture is going to be about. It's not that I don't know anything about the topic itself but more of a refresher and surprisingly, during these periods of study, I too learn a great deal more. Researching a topic, especially one that you already know quite well, can be very eye-opening as more and more people write their experiences up on the web.

The course has so far covered topics including ClickOnce, Security, Threading, Better Forms Design, ADO, Inheritance, Classes and DataBinding. There are actually two parts to this course so that not only Windows Forms is covered but also Web Forms. Windows Forms is covered by myself and Web Forms is covered by a fellow work colleague. I'll be attending the Web Forms lectures to assist in the practical lab when students need a hand. It'll also give me an opportunity to brush up on my Web Forms development skills

In addition to the Windows Forms lectures I'll be assisting with other lectures or filling in for someone when required. So far, I've only had to cover for one other lecture about SQL Server 2005 Full Text Searching.

I hope that what I've written here helps you to overcome your own fears about standing up in front of a group of people (it that's what you're here for). I can tell you that I plan to continue lecturing whenever the opportunities present themselves.

Until next time....

Recently I was asked to participate and prepare a Specification Review for a potential new client. There were just two of us involved in the analysis and we only had a week to review the client's in-house application.

The client is preparing themselves for growth and expansion and came to SSW to determine if their intranet web application, developed using ASP, can be migrated to ASP.Net before the end of the financial year (which is about 5 months away). There are many modules to this application covering all areas of the business including purchasing, client / supplier details, client orders, manufacturing, etc. etc.

We were able to succeed in obtaining the contract despite the fact that the two of us have less than 8 months of combined experience with SSW. So, I decided to share with you the strategy we used that worked for us.

When negotiating a contract for new business it's important to keep in mind that the people that you are selling yourself to are not generally going to be in IT. This one point alone is the key to success. Let me explain a little about why IT plays a lesser role in winning new business.

If you walk into a business with an IT mindset and make recommendations about how you and/or your company can improve their systems you are most likely to be dissapointed when you walk away empty handed. The reasons are simple and yet a lot of people just do not understand why and/or how to go about winning new business. The key is to apply what I call the 3 L's. Look, Listen and Learn.

You Look through the client's system AND more importantly you Look at their business. It's crucial to identify how the business is run and how the internal processes interact with each other. This is made easier if you already have the first-hand practical experience behind you. Without this experience you cannot be expected to ask relevent questions outside of your knowledge of IT. Textbooks are a great source of information about how businesses operate but that is all they are, textbooks. Each business is different in how they work and operate and knowing the basics is a good start but actually knowing the processes from experience is better.

You Listen to everything that the client tells you and read between the lines. Often a client will tell you more than you may at first realise and being alert to this will give you an advantage. Ask questions about their business, how it got started, where it's been and where they would like to take it. This has some nice side benefits in that you get on side with the client by taking an interest in their company. You also need to concentrate on how the business is operating internally and if required how it interacts with the outside world. This is where an understanding of business processes really comes in handy. You are now working out how the business operates and your knowledge will allow you to see where there are potential issues within the client's processes. Asking questions about why they do things the way they do and providing other real world scenarios gives the client the confidence in your abilities in understanding their business.

Have you noticed anything about what I'm trying to tell you here? There's nothing about IT yet....NOTHING. We're gathering information and we want as much information as we can get. IT matters are the last thing that you want to be pushing out to the customer until you understand their business. I find that IT professionals THINK in IT. This is a bad thing to pocess and is only really useful when you are working on their systems. ie. If you cannot think outside of IT then you are better off cutting code and leave the initial analysis to those that can.

Next, you Learn what it is that your client is wanting to change / add / remove about their business. This step is really a concept that is applied to the first two L's (Look and Listen). When you have an understanding of the business rules and processes then following the client's requirements by comparing them to what you now already know makes this step a lot easier. ie. You'll be better equipped to understand what the requirements are and you'll also be able to foresee potential issues before any work is performed.

Sounds a lot harder than it really is...trust me! :)

As part of your investigations into the client's system you should document the screens/forms and grab screenshots along the way. Make a note of any errors, badly formed messages, complex forms etc. etc. You'll be needing this later as 'proof' to support your analysis of their system.

During your interviews with key staff members take notes about their concerns and ideas. Document the processes that they need to perform to complete a task. If you can see an easier way to do something then make a note of this in your documentation and also explain your thoughts to the client. Ask lots of questions and challenge why they do things that way (be polite when you do this as you don't want to annoy anyone). Ask if you can try entering unusual data in an attempt to cause an error. What you're really trying to do here is identify areas where improper data entered into a field could cause the system to break. eg. enter alphas into what should be numeric fields, or decimal values into integer fields (quantity fields are a good place for this). Document any unusual side effects that this causes.

Use SQL Auditor (providing that the client is using MS SQL Server) to get an idea about the queries performed. Time how long a query takes to return a result. Perform a quick analysis at the database and note how many tables there are, what relationships have been established, if there's any indexes etc. etc. The information gathered here might provide some immediate relief to the client by way of introducing indexes. All of this should be included in your findings. If performance gains can be accomplished by the simple introduction of an index then do a before and after timing test to prove your point and add this to your findings.

When you prepare your findings keep it at a high level. Don't put too much emphasis on the IT aspect. Remember, a client loves to hear about themselves and how good their systems are. Your findings should effectively praise the client for their good work while at the same time showing where the system can be improved along with the client's requirements.

If you're worried about your findings not having enough IT content then don't be. After the client agrees to give you the all clear to commence work then you can provide further documentation with more details relating to IT.

One last thing before I finish up, the client has brought you in to go over their system and in their eyes you're a professional. Act like a professional, be confident in your own abilities and always be honest to your client.

I hope that you find this information helpful in your own projects, it certainly works for us. I've used a similar technique before and mostly with success.

A couple of months ago I noticed that Windows Explorer, on my Vista machine, was crashing whenever there was a VOB file listed in a folder.

At first I thought it was some software that I had recently installed and immediately set about uninstalling the software. It made no difference at all and this led me to believe that the software I installed had also installed something else ... like some nasty piece of spyware or the like. So, I scanned my machine using my anti-virus software and found nothing, then scanned it with a 'free' version of Spyware Doctor that subsequently found some spyware/malware and may be the cause of my problem.

I was more than a little disappointed with Spyware Doctor at this time and I was getting frustrated as Spyware Doctor will not remove potential threats unless it's a paid and licenced copy (the 'free' version will prevent future threats but not allow you to remove existing threats - nice one). I caved in and spent the money on a licence and removed the existing threats. It still made no difference to my Windows Explorer crashing and upon further reading turns out that I've practically wasted my money on Spyware Doctor as the security in Vista makes it difficult for spyware and the like from getting their grubby little hooks in. Oh well, lesson learned there.

I also noticed that after installing Spyware Doctor my Vista machine began to slow down very noticeably. I've had to uninstall the software as it was causing my system to slow down in much the same way as the spyware/malware it's designed to block does...the irony of it all.

Searching Google resulted in not finding a solution to my problem. I was getting nowhere with this and I was about ready to do a format of the system and re-install Vista. But wait!! Vista is supposed to be a lot better than this! There has to be a solution to this problem!!

And there is solution. I looked through the options in Windows Explorer and changed the settings from 'Show preview and filters' to 'Use Windows classic folders' and BINGO no more crashing.

You get to this option from Windows Explorer. Click on Tools in the menu and then click on Folder Options

I've been trying to find out why this fixes the issue but with no results. If any of you are aware of why this fixes the issue then please share it with the rest of us.

I hope that this bit of info is of some help to someone and also saves a lot of time and effort.

I have recently accepted a new position at another company. As part of the new job I'll be required to work directly with clients. In order for me to do this I'll need a notebook that I can take just about anywhere with me. There are so many different brands, models and configuration options to choose from that I almost found it impossible to choose.

The notebook I will need must meet certain pre-defined requirements:

1. be under $3,500AUD 
2. have at least a 17" display
3. have a minimum resolution of 1680x880
4. a minimum of 4 USB 2.0 ports
5. support 4GB of DDR2 memory
6. Wireless Networking support
7. 250GB HDD
8. Vista Ultimate

The above first 6 requirements are MANDATORY as I'll need every one of those to be able to do my work comfortably. As you can see from my list the demands are not that great but would you believe that there are so few notebooks currently on the market that can meet those demands? It's true! Sure there's a wide range of notebooks that meet some of the requirements. But what I need must be in a single notebook and not several notebooks.

I eventually found 3 notebooks that met all of the above requirements and they are the ASUS G2S-A1, HP Pavillion dv9500T and the Dell Inspiron 1720. Now wait, only 3 notebooks? Yes! There were others but they didn't satisfy the first requirement - PRICE!

So, I looked at the ASUS online and it looked really good. I started looking around to find out who would have one so I can place my order. I had heard a lot of good reports from friends that swear by their own ASUS notebooks - I was SOLD!! Then one day I just happened to walk into a department store (David Jones) and there was the model I was after on display. It was a thing of eye-catching beauty ... to someone with a vision impairment. I was horrified at the look and style of the 'sports interior' design that would be more suited to a cheap, no-frills sports car. It was also large in depth but the width was ok. The look and style of this notebook had me rethinking about spending my money on an ASUS. Don't forget, I have to lug this thing out to client sites too. I needed something that was a little more on the conservative side.

The ASUS G2-S with it's 'Sports Interior' didn't appeal to me. Notice also that the keyboard is set way back close to the display, which was another thing I noticed that I didn't like. ASUS has a solid reputation for reliable notebooks and I did take this into account. The reason for not going for the ASUS was purely aesthetics.	The HP dv9500's more elegant design and style is much more appealing. It's quite a bit slimmer than the ASUS and the black/silver design gives it a nice 'retro' look.	Dell's Inspiron 1720 looks a bit bland which is probably why it's available in several different colours. The downside, for me, is that I wasn't able to view the exact model that I was interested in. Besides that, I have decided to go with the Dell purely because of positive after sales service experiences.

However, sitting right next to the ASUS was the HP. It was wider, thinner and the depth was also narrower than the ASUS. It was silver, not black with Red Trimming, and looked neat. I was not turned away from its visual looks so I was off to a better start with the HP. I wasn't convinced yet that I needed to spend my money on an HP until after I had a chance to check out the Dell.

I have to admit that Dell almost completely lost me when I realised that I couldn't actually physically feel, see and try one of their notebooks. I know that Dell have only just released their notebooks to some stores in the U.S. but I'm situated in Australia. It wasn't looking good for Dell. I went back to work the next day feeling like I had not actually achieve my goal in finding a suitable notebook. Sitting on a desk in the server room was a Dell Inspiron notebook that had been brought in to have the display replaced (looks like someone kinda maybe did put their fist through the display while possibly but not conclusively testing the notebook's ability for gaming). The Dell looked neat, small and lightweight. I was impressed. I then found out that one of my fellow peers also has a Dell Inspiron that's just a couple of years old and they've not had any trouble with theirs....'excellent' I thought.

So, I've now seen both the HP and the Dell (although the Dell was not exactly the same model ... but close enough) which one would I choose. It really came down to which company had a better support service. I haven't had any prior experience with HP's after sales service so I'm relying on the feedback given by other people in various forums. I have, however, see the after sales support in action from Dell. Going on the feedback from forum members and my experience with Dell I'm leaning towards Dell. HP users have indicated that their after sales support is not quite up to scratch. Not all HP users were stating this as their experience but a fair majority did.

I'll put my order in for the Dell Inspiron 1720 in Midnight Blue. When I've had a chance to have a play I'll come back to this entry and provide some feedback.

Until then....

December 15, 2007
I have now had an opportunity to see the Dell 1720 first hand. There was a Dell stand in the Westfield at Chatswood where they had one on display in Matte Black (my preferred colour).

The keyboard is nice and feels 'light' to the touch...I'm actually looking forward to getting my hands on mine now!

One thing that I didn't like about the online ordering for Dell is the apparent lack and inability to order a second battery. I was also dissappointed about not being able to include a back-pack carry bag (seems they have sold out and therefore don't offer what they don't have). If you need to order additional batteries then you need to phone Dell with your order.

Aside from the online ordering, I'm keen to get my Dell and so far, reasonably happy that I have made the right choice. I still plan to let you know how things go with the notebook after I have spent some time using it.

January 4, 2008
Finally ordered the notebook last Friday (January 4, 2008). It should arrive in 10-12 working days according to Dell.

I just can't wait! I've been using a loan notebook at work and it's a bit old, slow and has some issues with running Vista. At least I have something to use for the moment.

January 14, 2008
It's HERE!!
My first impression is that the Jet Black doesn't look as good as I imagined...should have stuck with the midnight-blue. Aside from that it's very cool. The screen is clear, bright and awesome. The sound is ok but I haven't begun to check that out completely just yet. The Keyboard has a nice feel to it but alas, I'll be using a wireless keyboard/mouse combo (I prefer a 'real' keyboard any day) like the one I raved about in my post How's the keyboard shaping up?.

I've installed a Vista image that SSW have put together that contains all of the software pre-loaded. This is to reduce the amount of time required to install the many software packages I require to work both on and off site. There's an article about Vista images on the SSW web site titled Do you know the best way to deploy Windows Vista across your organisation that goes into some detail about how to create an image to simplify the deployment of Vista and save huge amounts of time as well.

In fact, SSW have rules for just about everything including project management, software/application development and web site design (and that's just a fraction of the topics that is covered). If you have a project of some kind in progress and would like some rules/guidelines on how to improve on it then I do encourage you to take a look yourself at SSW's Rules.

Well, that's all I have right now until I have a chance to try out my new toy a bit more and give it a good run. I will let you know shortly what I think.

January 30, 2008
I thought it was time to finally tell you what I think about the Inspiron 1720 from Dell. It's a Wee Ripper!

It's been performing without any issues, it's fast, the display and resolution is crisp and as it's name suggests True To Life, the keyboard is real nice and the separate keypad has come in handy on several occasions already. Battery life is not too bad considering the resolution and size of the display and having 2 hard disks. So far I've only had the 1720 on battery for almost 3 hrs and the battery indicator suggested that the battery capacity was down to 42% charge.

If you're considering buying one for yourself then don't let me stop you :) However, there is one minor point that may need to be taken into consideration and that is the dimensions provided on the Dell web site are for a notebook NOT fitted with a 9 cell battery. If you intend to use the 9 cell batteries then add another 25mm to the depth (about 1"). This little oversight on the dimensions can mean the difference between having a carry bag that will be big enough to carry your new notebook to one that is not big enough.

I purchased a backback for my notebook and I based my decision by using the dimensions listed on Dell's web site. Fortunately, the notebook bag that I bought is only just big enough carry my 1720 and it really is only just big enough (that is with the 9 cell battery installed).