Кент Бек цитаты

Кент Бек фото

2   0

Кент Бек

Дата рождения: 31. Март 1961

Кент Бек — разработчик программного обеспечения, создатель таких методологий разработки ПО как экстремальное программирование и разработка через тестирование . Бек был одним из 17 специалистов, подписавших Agile Manifesto в 2001 году.

Кент Бек учился в Орегонском университете с 1979 по 1987 год, получил степени бакалавра и магистра по информатике. Был одним из пионеров в введении в практику шаблонов проектирования ПО, создании методологии разработки через тестирование, а также коммерческого использования языка Smalltalk. Бек популяризовал CRC-карты вместе с Уордом Каннингемом, совместно с Эрихом Гамма является создателем фреймворка для тестирования JUnit.

Кент Бек живёт в городе Медфорд штат Орегон, работает на Facebook.

„Smalltalk, с его акцентом на человеческом аспекте программирования, был той питательной средой, на которой выросло Экстремальное Программирование. Smalltalk всё еще не имеет себе равных по уменьшению стоимости изменений в течении всего времени жизни проекта. А это то, без чего существование XP не возможно.“

„Оптимизм — это профессиональный источник опасности для программиста: обратная связь клиента может его сгладить.“

„I'm not a great programmer; I'm just a good programmer with great habits.“

„Do The Simplest Thing That Could Possibly Work“

„Responsibility cannot be assigned; it can only be accepted. If someone tries to give you responsibility, only you can decide if you are responsible or if you aren't.“ Extreme Programming Explained: Embrace Change

„The XP philosophy is to start where you are now and move towards the ideal. From where you are now, could you improve a little bit?“ Extreme Programming Explained: Embrace Change

„Without planning, we are individuals with haphazard connections and effectiveness. We are a team when we plan and work in harmony.“ Extreme Programming Explained: Embrace Change

„McConnell writes, "In ten years the pendulum has swung from 'design everything' to 'design nothing.' But the alternative to BDUF [Big Design Up Front] isn't no design up front, it's a Little Design Up Front (LDUF) or Enough Design Up Front (ENUF)." This is a strawman argument. The alternative to designing before implementing is designing after implementing.“ Extreme Programming Explained: Embrace Change

„Beta testing is a symptom of weak testing practices and poor communication with customers.“ Extreme Programming Explained: Embrace Change

„the XP strategy is "design always.“ Extreme Programming Explained: Embrace Change

„Saying that programmers should just accomplish twice as much doesn't work. They can gain skills and effectiveness, but they cannot get more done on demand. More time at the desk does not equal increased productivity for creative work.“ Extreme Programming Explained: Embrace Change

„However, most defects end up costing more than it would have cost to prevent them. Defects are expensive when they occur, both the direct costs of fixing the defects and the indirect costs because of damaged relationships, lost business, and lost development time.“ Extreme Programming Explained: Embrace Change

„There is only one code stream. You can develop in a temporary branch, but never let it live longer than a few hours. Multiple code streams are an enormous source of waste in software development. I fix a defect in the currently deployed software. Then I have to retrofit the fix to all the other deployed versions and the active development branch. Then you find that my fix broke something you were working on and you interrupt me to fix my fix. And on and on. There are legitimate reasons for having multiple versions of the source code active at one time. Sometimes, though, all that is at work is simple expedience, a micro-optimization taken without a view to the macro-consequences. If you have multiple code bases, put a plan in place for reducing them gradually. You can improve the build system to create several products from a single code base. You can move the variation into configuration files. Whatever you have to do, improve your process until you no longer need multiple versions of the code.“ Extreme Programming Explained: Embrace Change

„Used Pluggable Adaptor, which we promise not to use again for four months, minimum, because it makes code hard to statically analyze.“ Test Driven Development: By Example

„If there are forms of testing, like stress and load testing, that find defects after development is "complete," bring them into the development cycle. Run load and stress tests continuously and automatically.“ Extreme Programming Explained: Embrace Change

„Change is not necessarily slow. A team eager or desperate for improvement can progress quickly. It doesn't need to wait long to assimilate one change before moving on to the next practice. If you change too fast, though, you risk slipping back into old practices and values. When this happens, take time to regroup. Remind yourself of the values you want to hold. Review your practices and remind yourself why you chose them. New habits take time to solidify.“ Extreme Programming Explained: Embrace Change

Подобные авторы