Your current filters are…
by Dietmar Kühl
C++ 2011 is now officially adopted and compiler vendors are adding support to implement the standard. There are many changes to make programming with C++ more effective. This presentation concentrates on the many features useful in everyday programming, excluding changes primarily targeted at better support for generic programming: although templates are certainly part of my usual toolbox it seems many people stay away from them. There is still plenty to talk about: constexpr, final, overridden, defaulted, or deleted functions, inherited or delegated constructors, strongly typed enums, new integer and character types and their literals, uniform initialization, r-values and move semantics, noexcept declarations and expressions, automatic types, decltype, new-style function declaration, and lambda functions, and range-based loops. Each one of these changes is intended to make C++ simpler in some form although the mere presence of them makes C++ bigger. Most of these extensions can be used in isolation i.e. you can choose to only use those parts which make your life easier. The presentation will introduce the various features with their objectives and explaining how to use them. Where applicable it will point out known pitfalls. Knowing about the many new aspects increases the toolbox available allows you to make an informed choice of what you want to use. C++ 2011 is coming: get ready to take advantage of it!
by Dirk Haun
Triggered by my employer's hand-wringing search for C programmers, I was wondering: Where do new C programmers actually come from?
C itself is still very much in use in many areas, yet CS students only seem to be learning higher level languages at university these days. While a competent programmer will be able to pick up pretty much any language in a short time, C does have some peculiarities - like pointers - that no other programming language has and that are a common cause of problems.
So what can we do to ensure a steady supply of experienced C programmers well into the future? Not claiming to have all the answers, I'd also like to invite the audience to help in brainstorming.
by Dirk Haun
While open source applications are widely accepted and used, both at home as well as at work, using open source components as part of their software is something that companies still seem to shy away from. Why is that?
In this talk, we're going to look at some of the reasons for that reluctancy, e.g. legal reasons or fear of the GPL, and check if they're valid and how much of a problem they really are in practice.
As a counterpoint, we’re going to look at the benefits of having open source components. Also on the agenda: How to find an open source component that fits your requirements and some thoughts on giving back to the open source community without having to give away all your company’s secrets.
How often do you deploy new versions of production code? Once per quarter? Once per month? Just as agile software development methodologies bring short iterations and always-working code, Devops methodologies and techniques such as infrastructure automation and continuous deployment can enable a business to release production code as often as several times per day. Frequent releases of incremental functionality mean lower risk at each release, and functionality being delivered to customers more quickly.
The DevOps movement is changing the way tech companies manage their infrastructure. Code is put into production faster and more safely by breaking down the barriers between Developers and IT Operations.
To achieve frequent safe releases one of the key things you need is automated, repeatable infrastructure. Open source tools like Chef and Puppet enable scripted, testable, repeatable server configuration every time, on physical hardware and virtualised or cloud services. Checking your infrastructure configuration into source control brings reproducibility, traceability, repeatability, brings developers and operations closer together
In this talk we will discuss the principles, methods and practices for achieving a state of continuous deployment, including developer testing, CI, integration testing and infrastructure. We will see how automated configuration management tools such as Chef can enable teams to accelerate their deployments and launch new services in minutes. I will highlight specific examples from my own experience of building a robust, automated data collection and analysis service for the insurance industry, using Chef and AWS in a startup.
24th–28th April 2012