7

First, a bit of context.. For me, architecture and design is really important. Architecture is a deeply subjective thing in my opinion, but that doesn't make it less scientific. A good software architecture is one that the team understands, and that the team agrees upon. Therefore, when I am the architect in a software project, my job is to make everyone ...


6

You can't prove that a particular methodology was applied to arrive at a particular result. However, in the specific case of work-for-hire, where the customer owns the resulting IP rights, they could ask for the whole history of development as recorded by your source control tool. If that history shows that you add a test, then add implementation, then ...


3

tl;dr: Some people seem to confuse the trait of a Software System having a good Architecture and a good Design with the activity of performing Architecture and Design explicitly up front and the role of an Architect and a Designer. Most Agile Processes do not have a separate Architecture or Design phase, and they do not have specially designated Architects ...


1

I suppose that using TDD will result in a cleaner code and design. While clean design doesn't automatically mean that TDD was used. I'd analyze such things when assuming TDD was used: A class has more getter functions than is used: to call them from tests to check a state. There's a small amount of High cohesion: such things are difficult to test. Each ...


1

Objectively, there is no way to find out if the tests were written test-first or test-after. But my personal opinion is that someone who is truly experienced with TDD will recognize if code was written test-first or test after. As they produce noticeably different structures and code. Also I have found that writing test-after often causes major edge-cases ...


1

The answer above about finding a common ground would be the best advice, and in keeping with the spirit of devops - but personally, the idea to bring operations and development closer together for me means to stop thinking of personnel as 'dev' or 'ops' in the first place, and to bring everyone's strengths to the fore in terms of improving the overall ...


Only top voted, non community-wiki answers of a minimum length are eligible