ALL Software Development Is Incremental

Подписаться 202 тыс.

Просмотров 6 тыс.

50% 1

Kent Beck talks to Dave about incremental software development and how building software this way enables software engineers to receive fast feedback on their work. That fast feedback is one of the keys to building better software faster.
This is a clip taken from Kent's full appearance, which you can see HERE ➡️ • Kent Beck On The FIRST...
___________________________________________
🙏The Engineering Room series is SPONSORED BY EQUAL EXPERTS
Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ bit.ly/3ASy8n0
___________________________________________
#softwareengineer #developerproductivity

Опубликовано:

2 мар 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 31

@trappedcat3615

This only works in a world with no gatekeepers, whether it is the absent reviewers or the awful tests preventing any changes.

@horsethi3f

Could you talk about the recent spike in tech layoffs.

@HemalVarambhia

Hi, Dave. I am sorry I keep asking this: are you closer to interviewing Tim Mackinnon?

@dennistucker1153

I think this video would have benefitted from some context in the beginning.

@esra_erimez

What are you thoughts regarding "squashing" commits?

@chrisdams

Hmmm.... I think there has to be some optimum here. Working in increments that are too big certainly makes things difficult. But I think it is also possible to work in increments that are too small. After reading Kent Becks Test Driven Development I tried to go to the extreme to keep my steps as small as possible in a personal project but I found that it took more time than taking bigger steps would have taken. Say you want to do a refactor that touches some places in the code. I could do it in one step or I could find a way to do it first in one place and then in some other place and run the tests in between. The problem with the latter approach is that you have to find a way to support both approaches in the interim. While that may be possible it may also not be that the cost is higher than the benefit.