Sessions

Not Interested
Interested

Saturday, 5 PM Room 302, Lot 1  Map

READ MORE
Speaker

PICK TAGS

  • .NET Framework
  • ActionScript
  • Ada
  • Ajax
  • Algorithm
  • Android
  • AppleScript
  • ASCET
  • ASP
  • ASP.NET
  • ASP.BASH
  • BPEL
  • Multi-threading
FINISHED

Wakanda is an open-source platform for developing business web and mobile applications in Javascript.

READ MORE
Clean Code - Design Patterns and Best Practices
by Theo Jungeblut
Agenda Not Set Yet Room Not Assigned
Why writing Clean Code makes us more efficient Over the lifetime of a product, maintaining the product is actually one - if not the most - expensive area(s) of the overall product costs. Writing clean code can significantly lower these costs. However, writing clean code also makes you more efficient during the initial development time and results in more stable code. You will be presented design patterns and best practices which will make you write better and more easily maintainable code, seeing code in a holistic way. You will learn how to apply them by using an existing implementation as the starting point of the presentation. Finally, patterns & practices benefits are explained. This presentation is based on C# and Visual Studio 2012. However, the demonstrated patterns and practice can be applied to every other programming language too.

I have been designing and implementing .NET based applications, components and frameworks for more than 9 years, and I am currently working as a Senior Software Engineer at AppDynamics, one of the leading application performance management solutions for distributed application for web and cloud. My special interests are software architecture, framework and platform design, and writing Clean Code applying craftsmanship principles.

Theo Jungeblut I have been designing and implementing .NET based applications, components and frameworks... www.designitright.net /Presenter/2013/Theo-Jungeblut-1405 CA https://twitter.com/#!/theojungeblut True True
6 C#
225 Design Patterns
392 Clean Code
454 Best Practices
624 Decoupling
Details
Clean Code - Design Patterns and Best Practices

Why writing Clean Code makes us more efficient Over the lifetime of a product, maintaining the product is actually one - if not the most - expensive area(s) of the overall product costs. Writing clean code can significantly lower these costs. However, writing clean code also makes you more efficient during the initial development time and results in more stable code. You will be presented design patterns and best practices which will make you write better and more easily maintainable code, seeing code in a holistic way. You will learn how to apply them by using an existing implementation as the starting point of the presentation. Finally, patterns & practices benefits are explained. This presentation is based on C# and Visual Studio 2012. However, the demonstrated patterns and practice can be applied to every other programming language too.
Clean Code: Homicidal Maniacs Read Code, Too
by Jeremy Clark
Agenda Not Set Yet Room Not Assigned
There's no such thing as a write-once application. The world is constantly changing, and our code needs to change with it. We'll think in small pieces and take a look at some principles and techniques that will keep our code manageable and understandable. Think about the developer who will come after you. Now, imagine that he's a homicidal maniac who knows where you live. Examples will be in C#, but the principles apply to pretty much every programming language.

Jeremy Clark is an application developer, technical speaker, and Microsoft MVP with over 13 years of experience in all aspects of the development lifecycle. After hours, he puts together demos and technical articles for JeremyBytes.com, a website focusing on .NET technologies. Other times he can be found shredding on a plastic guitar (or playing a real guitar fairly badly). He lives in Anaheim, CA with a seedling redwood tree and his cats, Amanda and Toby.

Jeremy Clark Jeremy Clark is an application developer, technical speaker, and Microsoft MVP with over... http://www.jeremybytes.com /Presenter/2013/Jeremy-Clark-8502 CA @jeremybytes
21 Refactoring
143 Agile
392 Clean Code
454 Best Practices
Details
Clean Code: Homicidal Maniacs Read Code, Too

There's no such thing as a write-once application. The world is constantly changing, and our code needs to change with it. We'll think in small pieces and take a look at some principles and techniques that will keep our code manageable and understandable. Think about the developer who will come after you. Now, imagine that he's a homicidal maniac who knows where you live. Examples will be in C#, but the principles apply to pretty much every programming language.
The Future of JavaScript Language Tooling
by Ariya Hidayat
Agenda Not Set Yet Room Not Assigned
It is inevitable that future JavaScript applications will grow to be more complex. Keeping the quality of such a complex system is far from trivial. Unfortunately, our JavaScript tools recently still move at a glacial speed. Many code analyzers scream at you when a semicolon is omitted, yet they are totally oblivious to a copy-paste mistake. This talk will discuss the development of emerging JavaScript language tooling designed to solve: * code inspection: autocomplete, code outline, API harness * static analysis: code metrics, API harness, cyclomatic complexity * dynamic analysis: code coverage, execution tracing, run-time scalibility * source transformation: coding style, language extension (module, class, macro, …)

Ariya is a passionate engineer interested in bleeding-edge technologies. He has been involved in various large projects, from KDE to WebKit. These days, his focus is mostly on software craftsmanship around web technologies.

Ariya Hidayat Ariya is a passionate engineer interested in bleeding-edge technologies. He has been... http://www.linkedin.com/in/ariyahidayat /Presenter/2013/Ariya-Hidayat-8299 CA ariyahidayat
2 AJAX
16 JavaScript
392 Clean Code
446 NodeJS
536 CI
662 Algorithms
Details
The Future of JavaScript Language Tooling

It is inevitable that future JavaScript applications will grow to be more complex. Keeping the quality of such a complex system is far from trivial. Unfortunately, our JavaScript tools recently still move at a glacial speed. Many code analyzers scream at you when a semicolon is omitted, yet they are totally oblivious to a copy-paste mistake. This talk will discuss the development of emerging JavaScript language tooling designed to solve: * code inspection: autocomplete, code outline, API harness * static analysis: code metrics, API harness, cyclomatic complexity * dynamic analysis: code coverage, execution tracing, run-time scalibility * source transformation: coding style, language extension (module, class, macro, …)

SPONSORS List


PLATINUM



GOLD



SILVER



COMMUNITY