Less than 10 people came to listen, mainly because we failed to compete with a very important football game that was played concurrently. So I would like to extend my special thanks to the professionals that came to listen to me. As I said many times, it is quality that counts rather than quantity.
The slides of the event are available for download here.
The facility was at 7P Solutions & Consulting AG. A large meeting room with about 10 attendees who formed a very interactive group. We diverted to subjects that were not strictly on the agenda (Like why BSOD is the best proof that your computer is functioning OK).
The slides of the event are available for download here.
The Subject of production environment is not considered very sexy, at least not by common developer. It takes time and experience to understand that the program you develop is part of a much larger system. About 17 people came to the meeting to listen to two aspects (out of many) of the fascinating production world.
The facility at Comma Soft AG was comfortable. The subjects were new to most of the attendees. There were many questions, which is always a good sign.
The slides of the event are here for anyone who wishes to download.
Well, My vacation just gets better. I was invited to speak about my favorite subjects (“Debugging .NET and Native Applications in the Field” and “Preparing Applications for Production Environments”) not just by the “Bonn-To-Code.Net” User’s group in Bonn on the 29/11/11, but also by the “.NET Usergroup Rhein/Ruhr” in Ratingen on the 30/11/11 and by the “DotNet UserGroup Ruhrpott” in Essen on the 1/12/11. I am looking forward to meet new people, share my knowledge and have lots of fun in my vacation.
My wife decided that I need a vacation, as far from home as possible, but not on the other side of the globe. After analyzing the requirements I came to the conclusion that Germany is a good choice. Since it is my vacation I decided that I must really have fun. So, on the 29.11.11 I am speaking in the Bonn-To-Code.Net User’s group in Bonn, about my favorite subjects: “Debugging .NET and Native Applications in the Field” and “Preparing Applications for Production Environments”. I can tell right now, that it is going to be a very good vacation, since there is nothing more rewarding than talking at user’s group meeting thereby getting to know new technical people.
Thanks again to everyone who attended my four lectures at SDWest 2008.
The code samples I used in my presentation "Adding Traceability to an Application", are available for download here.
Please feel free to email me with any questions regarding any of the subjects I talked about.
Many IT professionals and developers are surprised to find out that A BSOD doesn't "just happen" but is the result of an intentional call from a kernel level programmer to a system call. There is nothing coincidental or surprising in a BSOD.
There are two system calls used to create a BSOD: KeBugCheck and KeBugCheckEx (surprisingly enough these calls don’t return any value).
The purpose of these calls is to shut down the computer as fast as possible leaving enough evidence to enable you to get the precise state of the operating system at the time of the call. Considering the purpose of the call, you can conclude that if you got a blue screen then the call functioned according to the specification and it's actually solid proof that your computer is functioning properly.
There are many reasons for calling these subroutines and they are all documented in the WDK and WinDbg documentation. The common denominator of all these calls, is when a kernel programmer discovers a problem, which is so critical, that leaving the operating system running in this state, might cause critical damage to the system or to the data. In this case, all that's left to do is to push the red button, activate the air bags and halt the system ASAP.
This strategy is called "falling to a safe place" and is used by everyone dealing with emergencies. It's the ABC of mitigation and contingency planning.
This year I am going to attend WinHec 2007, I decided, it’s about time to go and learn what's new in the Windows Internals/Windows Device Driver development arena.
The introduction of WDF to the Device Driver Development world has had the same revolutionary effect as the introduction of MFC had on the traditional C++ programming world (for good and for bad).
Things have changed a lot in the old WDM DDK world with the introduction of WDK and WDF and there isn't a better place to get the information than WinHec.
C U there.
I must admit that now and again I find it hard to explain what I do for a living (and for fun). So after considering the problem for some time, I decided to sit down and design a business card to explain clearly what I do.
Every day I am called in to solve a different challenge in this endless world of software development and deployment. Armed with my toolbox of hammers, pipe wrenches, life experience, creativity, MSF and PTD, I unclog bottlenecks, clean blockages from rusty procedure pipes and analyze dumps and blue screens.
It is never just a blue collar field job, because after I find the root cause of a problem, I can't really solve it effectively without on-going management involvement. So I always keep a set of white collar clothing with me to wear when I want to bring them on board.
Why don't you join me in my adventures, traveling in IT and development project landscapes and backyards.
More Posts