align-toparrow-leftarrow-rightbackbellblockcalendarcamerachatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditfacebookglobegoogleimagesinstagramlocation-pinmagnifying-glassmailmoremuplabelShape 3 + Rectangle 1outlookpersonplusImported LayersImported LayersImported Layersshieldstartwitteryahoo

Preparing Applications for Production Environments

  • Jun 24, 2013 · 6:00 PM
  • Microsoft Silicon Valley

Preparing Applications for Production Environments

 

Description:

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

 

Speaker Bio:

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.

Join or login to comment.

  • Mason B.

    My company UpCounsel is a venture backed startup looking to hire ASP.NET MVC 3 Full stack Web developers. The position includes great benefits, an A+ team, a $100B addressable market and an undeniable problem space: the US legal industry. You're too good to NOT be surrounded by rockstars! Don't settle for a mediocre team, contact me for details.

    June 24, 2013

    • Karthick G.

      Hi Mason, please share the opportunity details. I am looking for job. Please let me know the contact details
      Thanks
      Karthi

      June 25, 2013

  • Peter C.

    It was a good presentation. After a slow start, it got into come real APIs that are powerful, but under-used, especially ETW, WMI and WER. These are all heavily used within Microsoft, but not heavily promoted to the developer community.

    What was missing was specific links to example code and documentation, which is probably out there, but will take some searching. It would be great if the presenter had some links gathered together into a BLOG post to go with the talk. I'm going to email the presenter and ask if he has some resources to recommend.

    June 25, 2013

  • Joe C.

    Great meeting! Gad walked us through the process of constructing an application to reveal the longest and most costly portion of the application lifecycle; Operation and Maintenance. Most enterprise applications take 1 to 2 years to get to deployment and then stay in operation for 7 to ten years. How Operations lives with the application depends on how much they were involved in the developement process (unfortunately and typically not much) and how well the application is "instrumented" to expose data when an issue becomes apparent. Gad discussed how many instrumentation API's and tools are already in the OS and within easy reach from Microsoft, e.g. Event Logging (using published standards), EWT (Event Tracing for Windows) and Logman scripting, Performance Counters and Custom Providers, WMI (Windows Management Instrumentation) and DTMF.org, WER (Windows Error Reporting) and Private Reporting, MMC, Powershell, the importance of DevOps, and lots more. You should have been there!

    June 25, 2013

    • William L.

      I wish the meeting was recorded.

      June 25, 2013

  • Paul M.

    Can't make it down in time.

    June 24, 2013

  • baltostar

    Sounds so dramatic :)

    1 · May 10, 2013

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy