Kim has over 30 yrs of experience building and shipping commercial and enterprise level software solutions from initial release to multiple release cycles. She has worked both in the start up sector as well as large corporations. Risk reduction is key to successful product launch and the long term viability of your company.
Let’s face it…every time we start a new job we have to figure out a new code-base, and that code-base is usually only new for us. Thousands if not millions of lines of code…where do you start?
<p>There really isn’t any “beginning” place. As a manager and team lead I’ll start new folks on easy bug fixes to help them get up to speed. But what I like to see are people taking the initiative to understand the larger picture. </p>
So…how do you do that? I’m going to walk you through my process. A process that I’ve used successfully as both a consultant and an architect. When you leave this session you’ll have some tools/techniques you can use to quickly learn a new code-base and help you have more confidence in the modifications you make. </p>
There is something for everyone in this talk. The software development community is being actively encouraged to embrace concurrent software development to better realize the full potential of multi-core machines. No more “free” performance enhancements handed to us by the hardware and firmware folks, now it’s up to us to figure out how to maximize our usage of the available hardware. Threads are a major tool to accomplish that. In this talk I will discuss what threads are, how they work, why they are dangerous, and some tips on what you can do to protect yourself. A properly threaded application can be a thing of beauty…a poorly threaded application a money pit. It’s up to the architects, developers, QAs, and managers to ensure that threading adds measurable value and not just pain.
Sample code is done in C# but all concepts are applicable across languages and OSs.</p>