Jun 24, 2013 · 6:00 PM
Microsoft Silicon Valley
Preparing Applications for Production Environments
Developers are often ignorant of what happens to their code after it leaves their machines (and no, we are not shipping your machine). Developers naively program in a sterile environment, and then toss the code over the fence for the end users or the server farms, while expecting that magically the app will work just as it did on their machines or the lab. Sadly, production environment are hardened, and are anything like a development environment, and is run by dedicated administration programs and their masters. The last thing those IT supervisors and Help Desk people care about is the elegance of the algorithm. Instead the care about mundane aspects such ease of operation, deployment, maintenance, control, instrumentation, telemetric, the ability to pinpoint problems and fixing them all on-site. In this session developers will get a rare look into the characteristics of production environments and learn what they can or even must do during development to transform their code to be production-environment-friendly and save significant cost and heartache. You will see how to manage, monitor and debug the application in production environments, the key performance elements of the application available for the operators and for the automatic management tools used in production environments.
Speaker: Gad Meir
Gad is an associated of Juval Lowy and is comming to the Bay Area for the Build Conference and has agreed to make a special presentation to the Baynet members.
Note meeting has been moved from the normal wednesday night time to monday night to avoid conficting with the start of the Build Conference
Gad Meir has worked in the computer industry since 1975. His main expertise is troubleshooting production and end user environments for the root cause of failures. Since the root cause of failures is either architecture, process and (rarely) abuse of technology, Gad uses MSF (Microsoft Solution Framework) principles to identify faults in development or deployment processes/procedures. Gad's main task is to pre-empt problems in the project-planning phase. Unfortunately, he is usually summoned at the last minute, either when the system crashes or when the project is about to die or for post mortem analysis of failed projects. Dealing with failed projects is directly connected with Gad's second specialty which is analyzing dumps, blue screens and other low-level plumbing tasks.