Martin Fowler Quotes

• If you're afraid to change something it is clearly poorly designed.

  Martin Fowler

  Si

  "Evolutionary Design: A Conversation with Martin Fowler, Part III". Interview with Bill Venners, www.artima.com. November 18, 2002.

  35 Copiar cita

• Cualquier tonto puede escribir código que un ordenador pueda entender. Los buenos programadores escriben código que los humanos pueden entender.

  Martin Fowler

  Inspirador, Divertido, Humorístico

  Jay Fields, Shane Harvie, Martin Fowler, Kent Beck (2009). “Refactoring: Ruby Edition”, p.36, Pearson Education

  84 Copiar cita

• The biggest issue on software teams is making sure everyone understands what everyone else is doing.

  Martin Fowler

  Team, Issues, Software

  20 Copiar cita

• Comprehensiveness is the enemy of comprehensibility.

  Martin Fowler

  Enemigo

  Twitter post from Mar 30, 2016

  26 Copiar cita

• Now I'm a pretty lazy person and am prepared to work quite hard in order to avoid work.

  Martin Fowler

  Order, Lazy, Prepared

  Martin Fowler, Kent Beck (1999). “Refactoring: Improving the Design of Existing Code”, p.90, Addison-Wesley Professional

  30 Copiar cita

• If you're a technical lead, you need to be coding.

  Martin Fowler

  Needs, Ifs

  47 Copiar cita

• When to use iterative development? You should use iterative development only on projects that you want to succeed.

  Martin Fowler

  Use, Development, Want

  21 Copiar cita

• So I hope I’ve made clear that imposing agile methods is a very red flag.

  Martin Fowler

  Red Flags, Made, Method

  19 Copiar cita

• I find that writing unit tests actually increases my programming speed

  Martin Fowler

  Writing, Tests, Bugs

  19 Copiar cita

• In almost all cases, I’m opposed to setting aside time for refactoring. In my view refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts.

  Martin Fowler

  Views, Littles, Cases

  Jay Fields, Shane Harvie, Martin Fowler, Kent Beck (2009). “Refactoring: Ruby Edition”, p.75, Pearson Education

  23 Copiar cita

• A pattern is an idea that has been useful in one practical context and will probably be useful in others.

  Martin Fowler

  Ideas, Patterns, Practicals

  Martin Fowler (1997). “Analysis Patterns: Reusable Object Models”, p.8, Addison-Wesley Professional

  18 Copiar cita

• Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.

  Martin Fowler

  Team, Errors, Practice

  "Continuous Integration". www.martinfowler.com. May 01, 2006.

  44 Copiar cita

• One of the big dangers is to pretend that you can follow a predictable process when you can't.

  Martin Fowler

  Danger, Process, Bigs

  20 Copiar cita

• Never in the annals of software engineering was so much owed by so many to so few lines of code

  Martin Fowler

  Engineering, Lines, Software

  27 Copiar cita

• When you actually sit down to write some code, you learn things that you didn't get from thinking about them in modeling terms...there is a feedback process there that you can only really get at from executing some things and seeing what works

  Martin Fowler

  Writing, Thinking, Feedback

  19 Copiar cita

• I can't choose whether someone is offended by my actions. I can choose whether I care.

  Martin Fowler

  Care, Action, I Can

  16 Copiar cita

• I can only think of so many good ideas in a week. Having other people contribute makes my life easier.

  Martin Fowler

  Pensamiento, Ideas, Personas

  Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts (2012). “Refactoring: Improving the Design of Existing Code”, p.59, Addison-Wesley

  12 Copiar cita

• He aprendido a evitar siempre decir "siempre"

  Martin Fowler

  He aprendido

  12 Copiar cita

• One of the things I've been trying to do is look for simpler or rules underpinning good or bad design. I think one of the most valuable rules is avoid duplication. "Once and only once" is the Extreme Programming phrase.

  Martin Fowler

  Thinking, Design, Trying

  "Design Principles and Code Ownership". Interview with Bill Venners, www.artima.com. November 11, 2002.

  11 Copiar cita

• Comparing to another activity is useful if it helps you formulate questions, it's dangerous when you use it to justify answers.

  Martin Fowler

  Use, Answers, Helping

  10 Copiar cita

• Why is composing symphonies tough? I don't know. It's just very few people in the world can do it well. And I think that's the case with upfront design. It is very hard to do well.

  Martin Fowler

  Thinking, Symphony, People

  "Evolutionary Design". Interview with Bill Venners, www.artima.com. November 18, 2002.

  10 Copiar cita

• Es imposible no fijarse en Ruby on Rails. Ha tenido un enorme efecto tanto dentro
  como fuera de la comunidad Ruby... Rails se ha convertido en un estándar
  herramientas bien establecidas.

  Martin Fowler

  Community, Tools, Rubies

  7 Copiar cita

También te puede gustar:

Kent Beck

Robert Cecil Martin

Alistair Cockburn

Grady Booch

Erich Gamma

Fred Brooks

David Heinemeier Hansson

Steve McConnell