modul8com

First open a Administrator Command Promnpt.
In there do a cd \windows\system32\msdtc
then:
msdtcvtr.bat -tracelog dtctrace.log.2013-11-21-18-01-40-0576-00 -o mylog

PS: don't try to browse with the file explorer, you can't get in c:\windows\system32\msdtc

yzorg

echo "START [$($MyInvocation.MyCommand.Name)] $(get-date -f yyyyMMdd.HHmmss.ff)"

try {
    #$env:Path += ";.\node_modules\.bin" # use npmx instead (v8.2+ / npm 5.3+)
    sal code "C:\Program Files\Microsoft VS Code\Code.exe"

    # cd to the first directory in the path that contains a program, script, or file
    filter goWhere { where.exe $args | select -first 1 | Split-Path -Parent | pushd }
    #filter goWhereCD { where.exe $args | select -first 1 | Split-Path -Parent | cd }

jaceklaskowski

Rough Notes about CQRS and ES

Once upon a time…

I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).

I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).

It seems inevitable to throw Domain Driven Design (DDD) in to the mix.

teamaton

Remove-ItemProperty -Path HKLM:\Software\Microsoft\Fusion -Name ForceLog
Remove-ItemProperty -Path HKLM:\Software\Microsoft\Fusion -Name LogFailures
Remove-ItemProperty -Path HKLM:\Software\Microsoft\Fusion -Name LogResourceBinds
Remove-ItemProperty -Path HKLM:\Software\Microsoft\Fusion -Name LogPath

JasonGiedymin

#!/usr/bin/env bash
#
# Author: _j_a_s_o_n_g_at_a_p_a_c_h_e_dot_org
# License: GNU GPLv3
#

set -e

if [ -z "$1" ]; then
  echo "Please supply param 1 as the git hash which to cheery pick. Now exiting..."

ygrenzinger

Summary of book "Clean Architecture" by Robert C. Martin

Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.