mariogleichmann
-
In light of actual events: seek loow coupling in the sense of concepts that
can be understood and reasoned about independently of each other
about 8 hours ago
from TwitterMail
-
Agree DDD: choose Modules that tell the story of the system and contain a cohesive set of concepts
about 17 hours ago
from web
-
Agree DDD: Modules in domain layer should emerge as meaninful part of the model,telling the story of the domain on a larger scale
5:12 PM Nov 20th
from web
-
FP+1: If a function is pure it's guaranteed isolated from other parts, hence
easier 2 change code in 1 place w/o breaking anything unrelated
7:41 AM Nov 19th
from TwitterMail
-
:_* in Scala: 'treat this sequence as a sequence' o/wise your n items seq
will be treated as seq of 1 item (which will be your n item seq)
12:25 AM Nov 17th
from TwitterMail
-
If u understand Liskov Subst.principle and Design By Contract esp.under
inheritance, you'll also understand contra- and covariance in
1:59 AM Nov 16th
from TwitterMail
-
@ ...s/times become aware of 'thinking in Scala' in terms of
using some concepts (traits,implcits,...) when in Java land...;o)
2:14 AM Nov 10th
from TwitterMail
-
Today it happened:Java compiler complains about missing return statement
while i'm staring @ expression + puzzled because 2 attuned to Scala
1:23 AM Nov 10th
from TwitterMail
-
Would you agree Eric Evans (DDD) about Modules / Packages: cognitive overload is the primary motivation for modularity ... ?
1:20 PM Nov 9th
from web
-
If u start 2 play with nested type declarations in , be sure to
understand Path-Dependend Types, otherwise you'll run into trouble...
1:18 AM Nov 9th
from TwitterMail
-
Agree DDD on Services: operation names should come from the ubiquitous language. Parameters and results should be domain objects
2:31 PM Nov 5th
from web
-
Agree DDD: changing code changes the model, so programmers are modelers, wether anyone likes it or not ...
10:13 AM Nov 3rd
from web
-
Agree DDD: effects of a model can be very sensitive to details which don't always come across UML diagrams - so programming is all design
9:03 AM Nov 3rd
from web
-
@ : i'm interested of writing some Scala stuff ... any
preferences about a special topic?
4:11 AM Nov 3rd
from TwitterMail
-
Agree Wirfs-Brock about RDD and TDD: 'With a design-test-code-reflect-refactor rhythm, good code emerges alongside well-designed interfaces'
3:06 PM Oct 28th
from web
-
Excellent Article about core of Responsibility-Driven Design (in contrast to structural focussed design strategies) at
3:00 PM Oct 28th
from web
-
CleanCodeCampfireRule++:'Our responsibility is to do what we can,learn what we can,improve the solutions and pass them on' Richard P.Feynman
2:19 PM Oct 28th
from web
-
My understanding of TDD: TDD involves short cycles of writing specs that prove the DESIGN, not verifying some code / implementation
2:02 PM Oct 26th
from web
-
Clean code roots:our main task isn't 2 instruct a computer what to do,but rather on explaining to human beings what we want it to do.D.Knuth
1:37 PM Oct 26th
from web
-
Wirfs-Brock on DUF vs. BDUF: Upfront design needn’t be wasteful if you develop a design rhythm that balances thinking, learning and doing
1:20 PM Oct 26th
from web
|
- Name Mario Gleichmann
- Location Frankfurt / Germany
- Web http://gleichmann...
- Bio Dad, Husband and strong believer in Brain Driven Development
|
