The document discusses various topics related to software development including agile methodologies, traditional vs agile approaches, productivity of different developer types (cowboy vs professional), and challenges with traditional approaches. Specific points covered include the agile manifesto principles, benefits of agile such as improved productivity over time, and how agile values individuals, collaboration, and responding to change over rigid processes.
95. // create some properties and get the default Session
Properties props = new Properties();
props.put("mail.smtp.host", _smtpHost);
Session session = Session.getDefaultInstance(props, null);
// create a message
Address replyToList[] = { new InternetAddress(replyTo) };
Message newMessage = new MimeMessage(session);
if (_fromName != null)
newMessage.setFrom(new InternetAddress(from,
_fromName + " on behalf of " + replyTo));
else
newMessage.setFrom(new InternetAddress(from));
newMessage.setReplyTo(replyToList);
newMessage.setRecipients(Message.RecipientType.BCC,
_toList);
newMessage.setSubject(subject);
newMessage.setSentDate(sentDate);
// send newMessage
Transport transport = session.getTransport(SMTP_MAIL);
transport.connect(_smtpHost, _user, _password);
transport.sendMessage(newMessage, _toList);
Tuesday, December 15, 2009
96. new EmailMessage()
.from("demo@guilhermechapiewski.com")
.to("destination@address.com")
.withSubject("Fluent Mail API")
.withBody("Demo message")
.send();
(thanks to Guilherme Chapiewski)
Tuesday, December 15, 2009
117. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
Tuesday, December 15, 2009
124. Manifesto for Agile Software Development
Kent Beck Mike Beedle, Arie van Bennekum, Alistair Cockburn,
Beck,
Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith,
Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin,
Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
Tuesday, December 15, 2009
142. Manifesto for Agile Software Development
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn,
Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith,
Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin,
Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
Tuesday, December 15, 2009
214. Trabalho 1 hora 3 semanas < 1 hora 8 semanas 1 semana 6 semanas 2 semanas 2 semanas
Juntar
Enviar Aprovação Aprovação Codifica-
Requeri- Análise Design Testes Deploy
Requisição do Projeto do Cliente ção
mentos
Espera 6 semanas 2 semanas 8 semanas 1 semanas 2 semanas 3 semanas 3 semanas 3 semanas
Tuesday, December 15, 2009
215. Trabalho 1 dia 1 hora 2 semanas 4 semanas 4 semanas 4 semanas
Enviar Aprovação Arquitetura Sprint Sprint Sprint
Requisição do Projeto Preliminar
#1 #2 #3
Espera
2 dias 1 semana 1 semana 1 dia 1 dia
Tuesday, December 15, 2009
228. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
Tuesday, December 15, 2009
229. Manifesto for Agile Software Development
Estamos are uncovering better maneiras melhores de
We “descobrindo” ways of developing
desenvolver software naand helping ajudando outros
software by doing it prática e others do it.
Through this a desenvolver.
work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
Tuesday, December 15, 2009