Profile_bird

Hey there! mariogleichmann is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving mariogleichmann's tweets.

Already using Twitter
from your phone? Click here.

mariogleichmann

  1. @tiagofernandez ...s/times become aware of 'thinking in Scala' in terms of using some concepts (traits,implcits,...) when in Java land...;o)
  2. Today it happened:Java compiler complains about missing return statement while i'm staring @ expression + puzzled because 2 attuned to Scala
  3. Would you agree Eric Evans (DDD) about Modules / Packages: cognitive overload is the primary motivation for modularity ... ?
  4. If u start 2 play with nested type declarations in #Scala, be sure to understand Path-Dependend Types, otherwise you'll run into trouble...
  5. Agree DDD on Services: operation names should come from the ubiquitous language. Parameters and results should be domain objects
  6. Agree DDD: changing code changes the model, so programmers are modelers, wether anyone likes it or not ...
  7. 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
  8. @stal_m : i'm interested of writing some Scala stuff ... any preferences about a special topic?
  9. Agree Wirfs-Brock about RDD and TDD: 'With a design-test-code-reflect-refactor rhythm, good code emerges alongside well-designed interfaces'
  10. Excellent Article about core of Responsibility-Driven Design (in contrast to structural focussed design strategies) at http://tiny.cc/RgFKK
  11. CleanCodeCampfireRule++:'Our responsibility is to do what we can,learn what we can,improve the solutions and pass them on' Richard P.Feynman
  12. My understanding of TDD: TDD involves short cycles of writing specs that prove the DESIGN, not verifying some code / implementation
  13. 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
  14. Wirfs-Brock on DUF vs. BDUF: Upfront design needn’t be wasteful if you develop a design rhythm that balances thinking, learning and doing
  15. Not only an exhilarant article for those reading Heinlein: '7 Lessons for Software Developers from Heinlein' - http://tiny.cc/JajMd
  16. 2 many times seen: Don’t design every object to behave defensively.Redundant checks are hard to keep consistent and lead to brittle code W.B
  17. You may only develop a design sense by seeing both good AND bad code.
  18. @fbahr , @JBezivin ... thanks for your valuable hint about Rebecca J. Wirfs-Brock ( @rebeccawb )! ... will follow :o)
  19. Software development at its core is most essentially thinking, changing a vague difficulty into a specific, concrete form... would u agree ?
  20. Up-Front design is not Up-front thinking - it's 'rarely wasted effort, especially when tackling complex or novel design problems' (W--Brock)