what program growth during your association unequivocally (methodologies, tools, ...)?
since i've started initial office conductor program developer twin years ago, i've review articles ordinarily supposed methodologies (e.g. scrum, xp), technologies (e.g. ejb, spring), techniques (e.g. tdd, formula reviews), collection (bug tracking, wikis) program companies.
for i've found during the association doesn't i ask myself why. doing wrong merely articles i've review unequivocally explanation it's genuine world? articles some-more academic?
so, greatfully tell me it's during your company. tell all per program development. here suggestions (in method mind). tell during slightest not, give brief comment:
- test-driven-development
- domain-driven-design
- model-driven-design/architecture
- do test?
- unit testing
- integration testing
- acceptance testing
- code reviews
- innovative technologies (spring, hibernate, wicket, jsf, ws, rest, ...)
- agile
- pair programming
- uml
- domain-specific languages
- requirement preference (how?)
- continous integration
- code-coverage tools
- aenemic domain model
- communication (wiki, mail, im, mailinglists, documents)
- effort estimates
- team size
- meetings
- code metrics
- static formula analysis
- bug tracking
- ...
and remember: i wish know unequivocally do, cruise should do.
Comments
Post a Comment