SMoni

var BlackBox = function() {
    var self = this;

    self._events = [];


    self.Record = function(event) {
        self._events.push(event);
        self.Recorded(event);
    };

SMoni

An abstract interface should not require any configuration to use

Configuration should be done behind the scenes using an external resource like a property file, and should be done internally before anyone uses the interface.

---

An user of an abstract interface should not have to go through more than one function call in a chain to “find” any component they need

Remember that indirection is evil and only ends up adding to the cognitive complexity necessary to use something. You can find examples of this in normal GUIs when you are forced to go through a huge list of complicated steps across multiple interface to complete one task. A wizard is an example of an abstraction over these complicated steps, and it basically provides one access point to your task. The same idea applies to abstract interfaces: If the user has to call more than one function just to access a component or complete a task then you haven’t helped them at all.

SMoni

Jedes Problem wird solange mit MSExcel bearbeitet, bis bemerkt wird, dass es nicht verstanden wurde.

When there’s no more room in your Repo. Then dead code will be in the deployment 
  and coders won’t have a commit. Cause it’s the dawn of the dead code 

Wenn die Schnittstelle schwer zu verstehen ist und eine Dokumentation braucht,
  dann ist die Schnittstelle unter Umständen nicht wirklich gut.
  Eine schlechte Schnittstelle wird durch eine Dokumentation nicht besser.

Es geht nicht darum, es richtig zu machen, sondern nicht falsch!

SMoni

var getWeek = function() { 

    var a = Math.floor((14 - (this.getMonth())) / 12);
    var y = this.getYear() + 4800 - a;
    var m = (this.getMonth()) + (12 * a) - 3;

    var jd = this.getDate() - 2 + Math.floor(((153 * m) + 2) / 5) + (365 * y) + Math.floor(y / 4) - Math.floor(y / 100) + Math.floor(y / 400) - 32045;
                              ^ Offset auf Montag

    var d4 = (jd + 31741 - (jd % 7)) % 146097 % 36524 % 1461;

SMoni

• Qualität von Anfang an (Build Quality In)
• Verschwendung vermeiden (Eliminate Waste)
• Wissen erzeugen (Create Knowledge)
• Entscheidungen so spät wie möglich (Defer Commitment)
• Schnelles Liefern (Deliver Fast)
• Respekt (Respect People)
• Das Ganze optimieren (Optimize The Whole)

SMoni

• Sortiere aus Obsolete Dateien, Software usw. auf Arbeitsplatzrechnern und Server finden und entfernen oder archivieren.
• Sauberkeit Den virtuellen und realen Arbeitsplatz säubern.
• Systematisierung Ordner-Strukturen auf Arbeitsplatzrechnern und Servern vereinheitlichen.
• Standardisierung Strukturen automatisiert anlegen, Coding-Richtlinien festlegen.
• Selbstdisziplin Die Vorgehensweise leben.

SMoni

Unterteilung

What the system is (User thinking)

• Classes & Objects
• Domain Experts
• Architects
• Database Schemata
• Long-term stable structure
• Form

SMoni

• The pitfalls of Test-Driven Development
• Power your projects with Telerik - Now with the Convenience of NuGet
• What is Software Architecture?
• Servers Microsoft Message Analyzer 1.1
• Paket
• Coupling and Cohesion
• TypeConverters: There's not enough TypeDescripter.GetConverter in the world
• PostSharp
• Neo4j
• http://design-types.net

SMoni

Software architecture encompasses the set of significant decisions about the organization of a software system including the selection of the structural elements and their interfaces by which the system is composed; behavior as specified in collaboration among those elements; composition of these structural and behavioral elements into larger subsystems; and an architectural style that guides this organization. Software architecture also involves functionality, usability, resilience, performance, reuse, comprehensibility, economic and technology constraints, tradeoffs and aesthetic concerns.

Philippe Kruchten, Grady Booch, Kurt Bittner, and Rich Reitman

The highest-level breakdown of a system into its parts; the decisions that are hard to change; there are multiple architectures in a system; what is architecturally significant can change over a system's lifetime; and, in the end, architecture boils down to whatever the important stuff is.

Patterns of Enterprise Application Architecture, Martin Fowler

SMoni

require "test/unit"
require "./IntegerArrayToString.rb"

class Suite < Test::Unit::TestCase

    Array.include IntegerArrayToString

    def test_GetArrayAsString
    
        randomNumber = Random.new.rand(1..100)