2 Matching Annotations
- Jun 2021
-
www.mutuallyhuman.com www.mutuallyhuman.com
-
For me the diagrams make it easier to talk about what the tests do without getting bogged down by how they do it.
Tags
- focus on what it should do, not on how it should do it (implementation details; software design)
- communication: use the right level of detail
- communication: effective communication
- communication: focus on what is important
- describe the what without getting bogged down by how (implementation details; too detailed)
- too detailed
Annotators
URL
-
- Feb 2021
-
github.com github.com
-
While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.
Tags
- focus on what it should do, not on how it should do it (implementation details; software design)
- focus on concepts/design/structure instead of specific/concrete technology/implementation
- allowing developer/user to pick and choose which pieces to use (allowing use with competing libraries; not being too opinionated; not forcing recommended way on you)
- abstractions
- freedom of user to override specific decision of an authority/vendor (software)
- Trailblazer
- leaving the details of implementation/integration up to you
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively
- newer/better ways of doing things
- rails: the Rails way
Annotators
URL
-