VimleshS

Patterns of Enterprise Application Architecture

By Martin Fowler (2002)

Chapter 1: Layering

A basic example of layering: FTP < TCP < IP < Ethernet

Benefis of layering:

• You can understand a layer without knowing much about the others.
• Minimize dependencies.

maykonmeier

using System;
using System.ComponentModel;
using System.Runtime.InteropServices;
using System.Net;

    public class NetworkConnection : IDisposable
    {
        readonly string _networkName;

        public NetworkConnection(string networkName, NetworkCredential credentials)

CodeHeight

@Html.DropDownListFor(Function(Model) Model.ProgramTypeId, New SelectList(Model.allPrograms, 
      "ProgramTypeId", "ProgramName"), "Select Program....", 
    New With {Key .class = "form-control", Key .required = "Required"})

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

paulstatezny

Patterns of Enterprise Application Architecture

By Martin Fowler (2002)

Chapter 1: Layering

A basic example of layering: FTP < TCP < IP < Ethernet

Benefis of layering:

• You can understand a layer without knowing much about the others.
• Minimize dependencies.

brazilnut2000

## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.

###################
# compiled source #
###################
*.com
*.class
*.dll
*.exe