t3dd16.typo3.org

verraes.net

Domain-Driven Design Courses with Mathias Verraes

http://verraes.net/workshops

One day hands-on discovery, analysis, modelling, and visualization. For Developers, PMs, Product Owners, Domain Experts, Analysts, . Discovering and building the Ubiquitous Language. Extracting and analyzing knowledge from domain experts. Visualization and collaboration techniques. Modelling scenarios, processes, and workflows. Read the full description. Three days hands-on discovery, analysis, modelling, visualization, and theory. Includes everything from the Event Storming Workshop. DDD in PHP Training.

verraes.net

Information Overload

http://verraes.net/2014/06/information-overload

Learn by finding the differences, not the similarities. Published on 27 June 2014 by @mathiasverraes. You are reading this on an Information Overload Device. Probably one that fits in your bag or even your pocket. You also have a large Information Overload Device in your living room, and there’s a bunch of others spread across your home, your office, and your environment. Oh, then it’s a document database, like the document database I already know about. It has small iterations? Share this on Twitter.

verraes.net

Let It Crash

http://verraes.net/2014/12/erlang-let-it-crash

The Erlang view of the world is that everything is a process and that processes can interact only by exchanging messages. Published on 09 December 2014 by @mathiasverraes. Programming Erlang: Software for a Concurrent World, 2nd ed. The Erlang view of the world is that everything is a process and that processes can interact only by exchanging messages. Having such a view of the world imposes conceptual integrity on our designs, making them easier to understand. It’s all about mutable state and concurrenc...

dfau.de

Impressum

http://www.dfau.de/standards/impressum

DFAU Ideen in Entwicklung. Friedrichstr. 4 6. Verantwortlich i. S. d. MDStV: Daniel Fau. In Sachen TYPO3: Die DeveloperDays kommen 2016 noch einmal nach Nürnberg. Anmeldung, Sponsoring und überhaupt alle Informationen gibt es hier t3dd16.typo3.org. Essentielles: At the keys. PHP, XML, JSON, HTML, CSS, JS, SOLR, MySQL, DDD, SOA und S.O.L.I.D. die Bausteine, mit denen wir Ihre Lösung realisieren. Wir sitzen in Fürth bei Nürnberg. Über Werte und Motivation.

dfau.de

Lage

http://www.dfau.de/standards/lage

DFAU Ideen in Entwicklung. Aus Fürth in der Welt zuhause. Fürth in Bayern. Kennen Sie alle zwischen erster und zweiter Liga. Bei Nürnberg beschreibt die Lage dann meist für alle. Im Grunde tiefstes Mittelfranken, sprechen wir Ihre Sprache und sind wie folgt zu finden. Der Flughafen Nürnberg (NUE) ist praktisch um die Ecke. Mit dem Taxi fahren Sie direkt zu uns. Die U-Bahn bringt Sie aber auch bis zum Hauptbahnhof Fürth. Von dort sind es 5 Gehminuten bis zu unserem Büro. Essentielles: At the keys. Lösungs...

verraes.net

Event Storming: on Fake Domains and Happy Paths

http://verraes.net/2014/07/event-storming-fake-domains-happy-paths

Event Storming: on Fake Domains and Happy Paths. More Event Storming insights: picking good domains, modelling branches using duplication, and creative visualisation. Published on 23 July 2014 by @mathiasverraes. Inspired by Tim Schraepen’s experience report. I thought I’d list some recent experiences with facilitating Event Storming sessions. You might want to read my older post with notes on facilitating Event Storming sessions. And the huge amount of content Alberto Brandolini has produced on the topic.

verraes.net

Domain Events

http://verraes.net/2014/11/domain-events

Domain Events allow you to segregate the models of different systems. Published on 11 November 2014 by @mathiasverraes. A system’s design is defined by it’s boundaries, and by the way it communicates with other systems. This outward facing design is, all things considered, more important than the internals. It is important whether we are talking about small systems (such as an object) or large systems. An Event is a type of message that describes something that has happened in the past. This is very ...

verraes.net

How Much Testing is Too Much?

http://verraes.net/2014/12/how-much-testing-is-too-much

How Much Testing is Too Much? Run an experiment to learn how much unit tests you actually need. Published on 29 December 2014 by @mathiasverraes. Because of that, code coverage of your entire code base is a pretty lousy metric. Code coverage has its uses though. When measured ad hoc, in small doses, it is a great tool to validate your assumptions. About how a single unit test executes a complex block of code. For an example of how to use code coverage to your advantage, watch Extract Til You Drop. Timebo...

verraes.net

Economy of Tests

http://verraes.net/2015/01/economy-of-tests

Migrate test levels to improve the long term sustainability of your test suite. Published on 05 January 2015 by @mathiasverraes. Joint post with Konstantin Kudryashov. A common complaint with teams that first try their hand at automated testing, is that it is hard, costly, and not worth the effort. On the other hand, supporters say that it saves them time. Definitions of Test Levels. We will simplify to three levels. The unit must be completely under your control. The test should limit the number of othe...