The following paragraph kind of sums it up when people ask what trust means for teams?
I believe you are competent to do the work
I believe that if you have an issue with me, you’ll bring it up directly
with me, not talk behind my back.
I believe will follow through on commitments—or let me know when you need
to renegotiate.
I believe you have good intentions towards me and the team.
Stuff about software development, agile and testing
Thursday, October 9, 2008
Labels
- agile (4)
- agile testing (1)
- build tool (1)
- design (1)
- DSL (1)
- duck typing (1)
- eclipse (1)
- ejb3 (1)
- Fluent Interface (1)
- grails groovy (1)
- groovy (1)
- gwt (1)
- hacking (1)
- haskell (1)
- java (1)
- javascript (1)
- jvm (1)
- languages (1)
- mac (1)
- pipes (1)
- programming (1)
- qa (1)
- rant (2)
- ruby (6)
- sas (1)
- scala (3)
- scripting (2)
- software rewrite (1)
- statically typed (1)
- testing (4)
- two phase commit (1)