It has been confirmed that the new Developer Lead will start working with us next month.  It should be interesting as neither myself or our other two application developers have met the applicant, so we are not sure what skill level he will have.

The other two developers have come up through the company and gained their skills along the way. Our senior developer (JA) came through the buying and merchandising department, starting with VBA in MS Excel, then VB6 and on to VB & C#.Net, while (PB) has come through from Logistics and I'm not sure his precise skill route, but he also codes in VB & C#.Net. Myself, I came into the company two years ago with basically only classic ASP and a whole lot of keeness to learn. I believe the other senior developer we had before he left also learned on the job too at another major uk clothing retailer, before joining NewLook.

As JA has so rightly pointed out, when the new guy turns up it will be good to see how our self taught standards and practices and skill levels stack up against a true professional from the industry. He has been programming in an OO approach for a fair few years and is very methodical and tends to follow some strict practices. For myself and PB it's only been a couple years that we have been programming in an OO approach. As a team, we have recently started to look into dependency injection and inversion of control, and JA is keen for our current project to utilise Spring.Net. We are hoping that the new chap can shed some light on if our intended development path is where the industry is going or if we are missing the point be a country mile.

Hi and welcome to my blog...

Although I am employed as an application developer and have developed / co-developed a number of Windows and Web applications for my employer, NewLook Retailers, I wouldn't concider myself as any more than a meer beginner in the big picture of things! One of the biggest driving forces for me as a programmer is that fact that I know there is still a hell-of-a-lot that I still don't know!

This blog will not attempt to show best practices, or ingenious ways to overcome obscure problems; it will be nothing more than a log of my personal development as a programmer and no doubt an expression of some of my frustrations as I come across problems while writing applications and libraries for both NewLook and myself. It may not be factually correct all (or any) of the time but it may end up of use to anyone else who experience any of the issues that I post about.

Please feel free to offer advice and / or criticism regarding anything I post on this site.

Best regards,
Duane.

p.s. There is a real risk of me not completing posts on this blog. I can only apologise now, and hope it doesn't happen too often!!!