@decanibass@tottinge DHH took a similar stance awhile back. You may find these conversations between him, Kent Beck, and Martin Fowler interesting. TLDR; the original proponents of TDD and unit testing are against using mocks when possible https://t.co/8kHj38OhPE
@tottinge Ha definitely not a good thing. I’ve been burned by that more than once. Not sure I see a way around it I suppose other than something along the lines of standardization or convention which is till problematic when it’s not followed or a new standard comes along
@housecor It’s a great workflow because you get more visibility into progress (more, smaller tickets getting done more quickly) and the process of breaking the tickets down into single acceptance criteria user stories gives the team more context and helps scope the work
@MasroorEjaz@ikoichi Clean code can only be written under the assumption that you don’t know the future. It’s optimized for change, not a predicted future state.
@allenholub I’ve seen a number of big rewrites fail. Do you have any tips on how to successfully execute rewrites? It seems like it’s a different development process than adding features to an existing system.