Central to efficient, agile development is a fast build: the sooner developers and QA have testable bits the more productive the whole team becomes. In an age of multicore systems, virtual machine labs and large build farms, ensuring that your software can be built in parallel is a requirement, not a nice-to-have. But too often parallel build results are disappointing: the performance doesn’t scale, it introduces dangerous instability, and it’s extremely difficult to troubleshoot, analyze and optimize. This technical review of the most valuable lessons I’ve learned working with a variety of embedded development shops on how to — and more importantly, how not to — design build scripts and Makefiles for maximum parallel performance.

Attendees will learn:
How to and how not to design build scripts and Makefiles for maximum parallel performance
What doesn’t work, why, and how to make things better today without starting over.

Anders Wallgren, Chief Technical Officer
Anders Wallgren is Chief Technical Officer of Electric Cloud. Anders brings with him over 15 years of in-depth experience designing and building commercial software. Prior to joining Electric Cloud, Anders held executive positions at Aceva, Archistra, and Impresse. Anders also held management positions at Macromedia (MACR), Common Ground Software and Verity (VRTY), where he played critical technical leadership roles in delivering award winning technologies such as Macromedia’s Director 7 and various Shockwave products. Anders holds a B.SC from MIT.