Skip to main content

Home/ Groups/ SoftwareEngineering
Rss Feed
Sort By: Most Recent | Popular Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

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)
kuni katsuya

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
      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
  • What is the project behavior, in this snapshot?
  • What did the programmers, in order to produce this snapshot?
  • ...43 more annotations...
  • committing comments describing the
  • behavior of the software,
  • rather than the
  • implementation or a description of what we did
  • commits’ comments started to look like BDD’s methods name: a description of a behavior.
  • principles
  • Talk about the feature, not about yourself
  • Don’t refer to the past
  • I know it’s now
  • list of benefits
  • More focus while developing
  • Commit review is much easier
  • Less cognitive load
  • You learn commenting much more precisely
  • commit comment becomes a
  • declaration of intent
  • like a BDD method name
  • No more “Just a fix“, “Improvements” or “I made this, this, this and also this” comments.
    • kuni katsuya
      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
  • Each preemptive comment triggers a micro design session
  • A preemptive comment sets a micro goal
    • kuni katsuya
      kuni katsuya on 15 Mar 13
       
      which also aligns well with the 'micro goal' or incremental deliverables approaches of most agile methodologies 
  • helps to focus a goal to be reached
  • 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?“
  • define micro-goals through preemptive comments
  • macro-goal through the feature branch name
  • A preemptive comment creates a little timebox
    • kuni katsuya
      kuni katsuya on 15 Mar 13
       
      similar to the timeboxing strategy of a short sprints, for instance
  • Writing comments preemptively puts the agreement between the pair members to a test
    • kuni katsuya
      kuni katsuya on 15 Mar 13
       
      more relevant to methodologies using pair programming
  • commit history gains a very balanced granularity
  • feature branch becomes a collection of evolutionary commits each of which has usually a 1:1 binding with tests
  • very easy to find which commit introduced a bug, since each commit is related to a single new goal/feature
  • Preemptive commit comments
  • Rule #2: write what the software
  • I started taking a lot of care of the words I was using in comments, commits, test names and classes/variables/methods’ names
  • be supposed to do,
  • not what you did
  • should
  • Introducing BDD
  • began with the simple attempt to replace the world
  • “should“
  • “test”
  • with the world
  • Rule #1: write commit comments before coding
  • use the same criteria for my commits’ comments as well.
  • (not what you did)
kuni katsuya

GraniteDS: Gas3 template for complex enums | Javalobby - 0 views

java.dzone.com/...graniteds-gas3-template

GraniteDS3 gas3 ComplexEnums Flex ActionScript3 AS3 CodeGeneration

shared by kuni katsuya on 16 Mar 13 - No Cached
  • GraniteDS: Gas3 template for complex enums
  • changed enum.gsp from class:org/granite/generator/template/enum.gsp
  • I posted  a new version on github (master-branch) that
  • ...3 more annotations...
  • works with GraniteDS 3.0.0. 
  • https://github.com/graniteds/graniteds_builder 
  • fixed and committed to github
kuni katsuya

The WebSocket API - 0 views

dev.w3.org/websockets

HTML5 WebSockets WebSocketsAPI specification

shared by kuni katsuya on 16 Mar 13 - No Cached
  • two-way communication with a remote host.
kuni katsuya

Download Update for Windows 7 for x64-based Systems (KB976422) from Official Microsoft ... - 0 views

www.microsoft.com/...details.aspx

SD SDCard Windows7 Windows7x64 driver >32GB

shared by kuni katsuya on 16 Mar 13 - No Cached
  • Update for Windows 7 for x64-based Systems (KB976422)
  • Install this update to support Secure Digital (SD) cards that are larger than 32 GB
kuni katsuya

Internet media type - Wikipedia, the free encyclopedia - 0 views

en.wikipedia.org/...Internet_media_type

MediaType MimeType

shared by kuni katsuya on 17 Mar 13 - Cached
  • Internet media type
  • two-part identifier for file formats on the Internet
  • called MIME types
  • ...16 more annotations...
  • sometimes referred to as Content-types
  • two or more parts:
  • media type
  • A type,
  • optional charset parameter
  • is composed of
  • a subtype
  • optional parameters.
  • and zero or more
  • indicate the character encoding (e.g. text/html; charset=UTF-8)
  • experimental or non-standard[3] media types were prefixed with x-
  • this practice was deprecated due to incompatibility problems when the experimental types were standardized
  • subtypes that begin with prs. are in the personal or vanity tree
  • Subtypes that begin with vnd. are vendor-specific
  • Limitations
  • may incorrectly classify a content's media type:
kuni katsuya

Agile/Evolutionary Data Modeling: From Domain Modeling to Physical Modeling - 0 views

www.agiledata.org/...agileDataModeling.html

shared by kuni katsuya on 17 Mar 13 - Cached
  • serial approach which risks communication errors
    • kuni katsuya
      kuni katsuya on 17 Mar 13
       
      serial approach, aka 'throw it over the wall' approach
  • parallel approach which risks double work (both of us would have explored the same schema issues, her from an object point of view and me from the data point of view) and incompatible work (we could have easily made different schema design decisions)
kuni katsuya

jsonschema2pojo - 0 views

www.jsonschema2pojo.org

JSON JSONSchema Java CodeGeneration

shared by kuni katsuya on 20 Mar 13 - No Cached
  • Generate Plain Old Java Objects from JSON or JSON-Schema.
« First ‹ Previous 1161 - 1180 Next › Last »
Showing 20▼ items per page