title: What is software development at your company really like (methodologies, tools, ...)?
body: <p>Since I've started my first job as a professional software developer about two years ago, I've read many articles about commonly accepted methodologies (e.g. Scrum, XP), technologies (e.g. EJB, Spring), techniques (e.g. TDD, code reviews), tools (bug tracking, wikis) and so on in software companies. </p>
  
  <p>For many of these I've found that we at our company doesn't use them and I ask myself why. Are we doing it wrong or is it merely that these articles I've read are not really telling what it's like in the real world? Are these articles more academic?</p>
  
  <p>So, please tell me what it's like at your company. Tell about everything regarding software development. Here are some suggestions (in the order as they come from my mind). Tell at least if you do it or not, or give a short comment: </p>
  
  <ul>
  <li>Test-Driven-Development</li>
  <li>Domain-Driven-Design</li>
  <li>Model-Driven-Design/Architecture</li>
  <li>Do you test? </li>
  <li>Unit Testing</li>
  <li>Integration Testing</li>
  <li>Acceptance Testing</li>
  <li>Code Reviews</li>
  <li>Innovative Technologies (Spring, Hibernate, Wicket, JSF, WS, REST, ...)</li>
  <li>Agile</li>
  <li>Pair Programming</li>
  <li>UML</li>
  <li>Domain-specific languages </li>
  <li>Requirement Specification (How?)</li>
  <li>Continous Integration</li>
  <li>Code-Coverage Tools</li>
  <li>Aenemic Domain Model</li>
  <li>Communication (Wiki, Mail, IM, Mailinglists, other documents)</li>
  <li>Effort estimates</li>
  <li>Team size</li>
  <li>Meetings</li>
  <li>Code metrics</li>
  <li>Static code analysis</li>
  <li>Bug tracking</li>
  <li>...</li>
  </ul>
  
  <p>And remember: I want to know what you really do, not what you would like to do or think you should do.</p>