Contents contributed and discussions participated by kuni katsuya

Simple Middle Filter: All | Bookmarks | Topics

Introducing BDD | Dan North & Associates - 1 views

dannorth.net/introducing-bdd

BDD BehaviorDrivenDevelopment introduction

shared by kuni katsuya on 15 Mar 13 - No Cached

Introducing BDD
...

Cancel

Preemptive commit comments | Arialdo Martini - 0 views

arialdomartini.wordpress.com/...pre-emptive-commit-comments

BDD BehaviorDrivenDevelopment CommitComment BestPractices SoftwareEngineering

shared by kuni katsuya on 15 Mar 13 - No Cached

Tell me what the software does
- kuni katsuya on 15 Mar 13
  
  tell me how the software should *behave*, not how the behavior was *implemented* ie. describe the changes in this commit from the behavioral perspective rather than implementation details
  
  <div class="cArrow"> </div><div class="cContentInner">tell me how the software should *behave*, not how the behavior was *implemented* ie. describe the changes in this commit from the behavioral perspective rather than implementation details</div>
  
  ...
  
  Cancel
...

Cancel
What is the project behavior, in this snapshot?
...

Cancel
What did the programmers, in order to produce this snapshot?
...

Cancel
...43 more annotations...
committing comments describing the
...

Cancel
behavior of the software,
...

Cancel
rather than the
...

Cancel
implementation or a description of what we did
...

Cancel
commits’ comments started to look like BDD’s methods name: a description of a behavior.
...

Cancel
principles
...

Cancel
Talk about the feature, not about yourself
...

Cancel
Don’t refer to the past
...

Cancel
I know it’s now
...

Cancel
list of benefits
...

Cancel
More focus while developing
...

Cancel
Commit review is much easier
...

Cancel
Less cognitive load
...

Cancel
You learn commenting much more precisely
...

Cancel
commit comment becomes a
...

Cancel
declaration of intent
...

Cancel
like a BDD method name
...

Cancel
No more “Just a fix“, “Improvements” or “I made this, this, this and also this” comments.
- kuni katsuya on 15 Mar 13
  
  BDD/TDD or any methodology aside, these are the worst commit comments as they are as useless as empty commit comments
  
  <div class="cArrow"> </div><div class="cContentInner">BDD/TDD or any methodology aside, these are the worst commit comments as they are as useless as empty commit comments</div>
  
  ...
  
  Cancel
...

Cancel
Each preemptive comment triggers a micro design session
...

Cancel
A preemptive comment sets a micro goal
- kuni katsuya on 15 Mar 13
  
  which also aligns well with the 'micro goal' or incremental deliverables approaches of most agile methodologies
  
  <div class="cArrow"> </div><div class="cContentInner">which also aligns well with the 'micro goal' or incremental deliverables approaches of most agile methodologies </div>
  
  ...
  
  Cancel
...

Cancel
helps to focus a goal to be reached
...

Cancel
Without preemptive comments, I often went on coding, always asking myself: “Should I commit now? Have I reached a stable state which I could consider a good commit?“
...

Cancel
define micro-goals through preemptive comments
...

Cancel
macro-goal through the feature branch name
...

Cancel
A preemptive comment creates a little timebox
- kuni katsuya on 15 Mar 13
  
  similar to the timeboxing strategy of a short sprints, for instance
  
  <div class="cArrow"> </div><div class="cContentInner">similar to the timeboxing strategy of a short sprints, for instance</div>
  
  ...
  
  Cancel
...

Cancel
Writing comments preemptively puts the agreement between the pair members to a test
- kuni katsuya on 15 Mar 13
  
  more relevant to methodologies using pair programming
  
  <div class="cArrow"> </div><div class="cContentInner">more relevant to methodologies using pair programming</div>
  
  ...
  
  Cancel
...

Cancel
commit history gains a very balanced granularity
...

Cancel
feature branch becomes a collection of evolutionary commits each of which has usually a 1:1 binding with tests
...

Cancel
very easy to find which commit introduced a bug, since each commit is related to a single new goal/feature
...

Cancel
Preemptive commit comments
...

Cancel
Rule #2: write what the software
...

Cancel
I started taking a lot of care of the words I was using in comments, commits, test names and classes/variables/methods’ names
...

Cancel
be supposed to do,
...

Cancel
not what you did
...

Cancel
should
...

Cancel
Introducing BDD
...

Cancel
began with the simple attempt to replace the world
...

Cancel
“should“
...

Cancel
“test”
...

Cancel
with the world
...

Cancel
Rule #1: write commit comments before coding
...

Cancel
use the same criteria for my commits’ comments as well.
...

Cancel
(not what you did)
...

Cancel

The Business Value of Using DDD | Getting Started with Domain-Driven Design | InformIT - 0 views

www.informit.com/...article.aspx

DDD DomainDrivenDesign rationale

shared by kuni katsuya on 15 Mar 13 - No Cached

The Business Value of Using DDD
...

Cancel

ddd-cqrs-base-project - DDD-CQRS Base Project Using Spring and Hibernate (Manage Comple... - 0 views

code.google.com/...ddd-cqrs-base-project

DDD CQRS DomainDrivenDesign CommandQueryResponsibilitySegregation

shared by kuni katsuya on 15 Mar 13 - No Cached

ddd-cqrs-base-project DDD-CQRS Base Project Using Spring and Hibernate (Manage Complexity Simply)
...

Cancel