No meeting in April

Due to several scheduling conflicts, there will be no UG meeting in April.  We are really sorry about that.

The next meeting will be probably Mai 15^th.  We will inform you as soon as we know something for sure.

The results of the polls are that Wednesday is the most popular day, the language should be adapted to the audience, and domain-driven development is the topic with the most interest.

First C++ User Group meeting in Wu5

After quite some advertisement in industry and academia, we met in the Wu5 and heard a inspiring talk by Peter Gottschling (pictures will follow suite). We had an overwhelming attendance of about 40-50 people which actually didn't fit into the club anymore (we apologize to those, that couldn't hear or see the presentation. Wu5 has offered us access to a larger auditorium.). Peter gave the talk in English (thanks). 

However, after the UG meeting is before the next one. So there are some questions to answer by our community. Please click your way through the following polls until Easter Monday (April 1st, 2013) :

1) Which day of the week suits the majority best?

http://doodle.com/6t7fdmg6u9f9g7sk

2) Which language should this event be held in (concerns the website and presentations)?

http://doodle.com/877nehbq664bc58c

3) What are topics of interest to you? (Please sign up, if you can offer to give a talk. Contact us, if you are interested in something but unable to present it. Then we can see if we motivate someone to give a presentation.)

http://tricider.com/brainstorming/lGS3

4) Your Feedback is important! Get in touch with us and tell us how you liked the event last night, how you like the webpage, how you feel about possible topics, ...

Hope to see you at the next C++ UG meeting.

Erstes Treffen: C++11 Style

Das erste Treffen unserer C++ User-Group in Dresden findet am 13.3.2013 um 20.00 Uhr in der Wu5 (zur Webseite) statt. Der Sprecher ist Dr. Peter Gottschling (TU Dresden, Simunova). Peter wird einen Vortrag von Bjarne Stroustroup in eigener Interpretation wiedergeben (Beginn 20.15Uhr, mit Erlaubnis des Erstautors). Je nach Besucherwunsch wird der Vortrag auf Englisch oder Deutsch gehalten. Danach wird es Gelegenheit zum Erfahrungs- und Meinungsaustausch geben. Hier ein kleiner Inhaltsabriss:

We know how to write bad code: Litter our programs with casts, macros, pointers, naked new and deletes, and complicated control structures. Alternatively (or in addition), obscure every design decision in a mess of deeply nested abstractions using the latest object-oriented programming and generic programming tricks. Such code is incomprehensible, unmaintainable, usually inefficient, and not uncommon.
But how do we write good code? What principles, techniques, and idioms can we exploit to make it easier to produce quality code? I will make an argument for type-rich interfaces, compact data structures, integrated resource management and error handling, and highly-structured algorithmic code. I will illustrate my ideas and motivate my guidelines with a few idiomatic code examples including C++11 features.

[Wir wissen, wie wir schlechten Quelltext schreiben: Wir vermüllen unsere Programme mit "Casts", Makros, Zeigern, nackten "new" oder "delete"s und komplizierten Kontrollstrukturen. Alternativ (oder obendrauf) führen obskure Design-Entscheidungen zu einem Wirrwarr von tief-eingebetteten Abstraktionen mittels der aktuellsten Tricks aus objekt-orientierter und generischer Programmierung. Solcher Quelltext ist unverständlich, unwartbar, oftmals ineffizient und leider nicht selten.
Aber wie schreiben wir guten Code? Welche Prinzipien, Techniken und Faustregeln kann man nutzen, um leichter Quelltext hoher Qualität zu erzeugen? In diesem Vortrag werde ich den Standpunkt pro Schnittstellen reich an Typen, kompakten Datenstrukturen, integriertem Ressourcenmanagement und Fehlerbehandlung sowie hoch-strukturiertem algorithmischen Code vertreten. Diese Ideen werde ich durch typische Code-Beispiele u.a. mit C++11-Eigenschaften illustrieren und motivieren.]

Zahlreiches Kommen, Ratschläge, Tipps und konstruktive Kritik würden wir uns sehr freuen.