Community News

Automatisierte Testausführung mit NCrunch

.NET User Group Bern Event

Montag, 1. September 2014 (18:00 bis 21:00 Uhr)

Automatisierte Testausführung mit NCrunch - mit Yannik Steiger

Nach der Sommerpause beschäftigen wir uns wieder mit einen Thema aus der Methoden-Kompetenz ;)

NCrunch unterstützt Entwickler bei der automatisierten Testausführung, bei der Erkennung von nicht getestetem Code und beim Debugging von Tests. Zudem bietet NCrunch neben Code Coverage und Performance Metriken verteiltes Testen und einen hoch optimierten Build Process.

Anhand von Beispielen wird uns Yannik aufzeigen wie die Features von NCrunch dich bei der täglichen Arbeit unterstützen können.

Über Yannik

Yannik wurde in Pusan (Süd-Korea) geboren und ist in der Schweiz aufgewachsen. Nach seinem Informatik-Studium legte er seine Spezialinteressen auf Knowhow- und Qualitätsmanagement sowie Team Coaching.

Seit 2007 ist Yannik auch im .NET/C# Umfeld tätig.


Die Anmeldung erfolgt unter Xing Events ohne Xing-Account ist eine Anmeldung über unser Kontaktformular möglich.

Das Hashtag auf Twitter: #dnugbenc

Wir freuen uns auf Deine Teilnahme!

Martin Affolter, Kay Herzam und René Leupold

Von Zeit und Datenmengen
Bei Datenmigrationen und der Batchverarbeitung kommen 2 Bereiche zusammen bei denen viele Entwickler (mich eingeschlossen) schnell an eine mentale Grenze stossen: Zeit Datenmenge Wohl ist jedem bekannt das ein Tag 24 Stunden hat und ein Terabyte aus 1024 Gigabyte besteht. Und doch kommt es immer wieder zu bösen Überraschungen.   Eine Optimierung am Code ist […] mehr
Weekend Reader, Week 29

IMG 0210

On the News:

Translation of the Apple-IBM romance

You heard it, Apple and IBM are best friends now. But what does it mean? This funny post translates the press release into something that we can understand:

 Enterprises love hand holding more than fat kids love candy. Apple is going to offer them hand holding through IBM.


Reflecting on Software Engineering:

Software Environmentalism

My colleague Tudor is musing about how we can deal with the fact that software systems get larger and larger, and they are being created at an ever increasing rate.

We cannot continue to let systems loose in the wild without any concern for how we will deal with them at a later time.

He proposes:

No system should get away without dedicated tools that help us take it apart and recycle it effectively.

For the profession he concludes:

Software engineering is more about dealing with existing systems as it is about building systems.


The Maintenance Developer Myth and The Noble Art of Maintenance Programming

So, software maintenance and dealing with legacy code is only going to increase as software is eating the world. But introducing a chasm between “real” developers and “maintenance” developers is probably not going to help.


What are good developers anyway?

Why are we interviewing developers by asking architect questions? Is it really what we need? When we deal with legacy, architecture gets less and less important. Problem solving skills are what really matters ...


But software eventually collapses under it’s own weight

(the obligate wisdom from Steve Jobs, which seems fitting at that point)


On JavaScript:

Breach: A browser written in JavaScript

Atwood’s law exemplified: "Any application that can be written in JavaScript, will eventually be written in JavaScript." is on sale!

If you want to learn JavaScript seriously, this screencast is a good starting point.


A JavaScript survival guide

If you are afraid of the pain of learning JavaScript, this post gives you some valuable survival tips.


Tech learning  recommendations:

Modern Structured Logging With Serilog and Seq

This is a interesting course on pluralsight. I am wondering what the alternative would be for the Java ecosystem? I guess I will attend the ELK workshop at ch/open Workshoptage in this regard.


Java Script Jabber Episode 106: Protractor with Julie Ralph

A good introduction to end-to-end testing in general and to the Protractor test framework. The episode also contains good discussions about software testing in general and gives insight about testing at Google.


Getting Started With Protractor and An Introduction to AngularJS End to End Testing with Protractor

If you are interested in Protractor, then this is a short tutorial and a longer introductory presentations


Some facts about Stateless EJB beans

It’s always good to repeat that stuff ...

SyncToy: Ein kleiner Backup-Helfer
An Backups denkt man in der Regel erst wenn es zu spät ist. Vorher ist es immer zu aufwändig und man glaubt eh keine wichtigen Dateien zu haben die nicht noch irgendwo anders gespeichert sind. Um nicht eines besseren belehrt zu werden würde es genügen die Daten nur regelmässig auf ein externes Laufwerk zu sichern. […] mehr
Weekend Reader, Week 28

IMG 0207

Developers are taking over the world!


Everyone involved in software development projects should read the book The New Kingmakers.

The book gives the background why traditional tayloristic approaches are not effective in the knowledge work environments of software projects: Plans and roadmaps are not going to work as long as you don’t get developers intrinsically motivated.

For some reason the book is free on the Kindle.


On the same topic:


Planning, planning and more planning!

Speaking of motivating developers. In my experience, one of the most demotivating construct in enterprise development is planning. 


The Agile Manifesto speaks about "Responding to change over following a plan”.

While Scrum is facilitating many Agile principles, the concept of the backlog is often used to re-establish a waterfall-like long-term plan. With the long-term plan comes the justification for controlling and micro-management. Newer methodologies that promise to “scale agile to the enterprise” (like SAFe) even reinforce this tendency for establishing and following a plan (note how the arrows in SAFe all point in one direction?). SAFe is an approach by classical management to re-apply tayloristic approaches that have been questioned by the Agile movement. 

That’s why Water-Scrum-fall is the reality of Agile today.
And that’s why I don’t believe in scaling Agile to the enterprise
That is why we have the Manifesto for Half-Arsed Agile Software Development.

 Ken Schwaber (the inventor of Scrum) puts it like this:

A core premise of agile is that the people doing the work are the people who can best figure out how to do it. The job of management is to do anything to help them do so, not suffocate them with SAFe.


Do we really need strict control (which is basically the reason for all that detailed planning)?

Tom De Marco (a pioneer and author in the area of software project management) has an interesting thesis about this in his paper: Software Engineering: An Idea Whose Time Has Come and Gone?

strict control is something that matters a lot on relatively useless projects and much less on useful projects


What can developers do: They should choose their work!

So for us developers this boils down to making a choice: What kind of projects do we choose to work on?

Mike Monteiro repeats that in his brilliant presentations: How Designers Destroyed the World

The work we choose to take on defines us!

Webstock '13: Mike Monteiro - How Designers Destroyed the World from Webstock on Vimeo.



I want to point to two special upcoming local conferences:

SwissJeese - An indie JavaScript conference in my beautiful hometown of Bern (July 26th 2014). I have never been to that conference and unfortunately my talk-submission was not accepted (probably the topic of Nashorn is too enterprisy for the conference :-)). But the program looks very promising and there are still tickets left.

ch/open Workshop Tage - An excellent event with a marvellous collection of interesting topics (September 9-11, 2014). I am attending and also holding workshops at the Workshop Tage for the last 7 years, and each year I am looking forward to the event again.


Battle Cry

Speaking of conferences: Philip is calling for an epic battle: Web vs Native on mobile devices - let the strongest prevail!
(actually, according to the rules of Philip it would be the quickest, not the strongest ... maybe Philip should look again at what happened to Oberyn Martell?)


On JavaScript

The obligate Gartner prediction:

Through 2014, improved JavaScript performance will begin to push HTML5 and the browser as a mainstream enterprise application development environment.

ThoughtWorks Technology Radar chimes in

The ecosystem around JavaScript as a serious application platform continues to evolve. 

Prezi writes about their experience from migrating from Flash to JavaScript … and why it took so long:

Large JavaScript codebases are hard.

Stackoverflow explains the difference between JavaScript and Java

Java and Javascript are similar like Car and Carpet are similar.

One is essentially a toy, designed for writing small pieces of code, and traditionally used and abused by inexperienced programmers. The other is a scripting language for web browsers.



Für die Forumaktivitäten und Termine werden wir vorläufig die Xing-Plattform nutzen. Nähere Informationen findest Du unter dnug-bern.

Veranstaltungshinweis SQL Performance Tuning