Sessions at GOTO Amsterdam 2011 about Code Quality

Your current filters are…

Thursday 13th October 2011

  • Solution Track: Quality through Tools

    by Stefan Kohler

    In Software, every customer and manager is expecting a high quality product, but that is proving to be harder than it sounds. We put a lot of time and effort in writing tests to prove the software is correct and analyzing its metrics. But do we have the right tools for the job? Are we focusing on the right type of quality and can we do a better job, supported by the right tools?

    During this talk we will go into what quality means and how we can categorize quality. Per category we look at the different tools, what they can offer us and why the tools have an important role in our quality-focused infrastructure. Afterwards you will have an impression of the tools on the market which can help you achieve higher quality in your products and you will have an understanding of the purpose of those tools.

    Keywords: Quality, Process, Tools, Development Infrastructure, Continuous Integration,
    Target Audience: Senior Developers, Architects and IT Managers

    At 1:20pm to 2:10pm, Thursday 13th October

  • .NET for Experts: Developers have a mental disorder

    by Greg Young

    We as developers have many biases that often we need to take a step back from in order to gain perspective. This session will deliberately go after many of our sacred cows and show how they are really just us over-optimizing a belief. All of these lead to a single generalized rule and a strategy for how to avoid these situations.

    Keywords: IOC, DRY, Patterns, Frameworks, Insanity

    At 2:30pm to 3:20pm, Thursday 13th October

  • JavaScript: Application design, techniques and tools for large(r) JavaScript applications

    by Karl Krukow

    On the server we often speak about so-called "non-functional" requirements of a program or an architecture, e.g., maintainability, extensibility, robustness and performance. We also have technical requirements that focus more on code structure e.g., separation of concerns, modularity, loose coupling, avoiding duplication.

    On the client side, the situation is often shockingly less ambitious: often we just hack until it works (in Firefox and then we ship it). Most of the time we can manage because there is only so much JavaScript code, but as the project scales in complexity our productivity quickly declines as does quality .

    Why are there so large differences in our mindset on the front- and back-ends?

    The goal of this talk is to motivate and help you improve the technical quality of your JavaScript projects. We consider one set of techniques, design patterns and tools that this speaker has successfully used to tame the complexity beast in several large and medium scale projects.

    Keywords: JavaScript, Application Design, Complexity, Technical Quality, Model-View-Controller
    Target audience: Developers that have some experience with JavaScript programming.

    At 2:30pm to 3:20pm, Thursday 13th October