How to Use Go Interfaces

Re:How to Use Go Interfaces by dnomad on Tuesday March 20, 2018 @03:11AM (#16626516)

Yes I find these sorts of comments as GP to be hopelessly naieve. It speaks to somebody who has never worked on a large project (think 4 teams of 10-20 developers spread across NYC, London, Tokyo, and Hong Kong) or a long-lived project (think 10 years).

That sort of minimial, incremental approach does not scale at all. Software engineering in the large requires, as you say, interfaces at every boundary and a near-religious understanding of how all the different components and boundaries fit together.

[ Parent | on HN ]

Re:How to Use Go Interfaces by adrianN on Tuesday March 20, 2018 @06:25AM (#16627252)

The incremental approach can work for large projects if the teams aren't afraid of large scale refactorings a couple of times a year.

[ Parent | on HN ]

Re:How to Use Go Interfaces by carlmr on Tuesday March 20, 2018 @08:00AM (#16627734)

And large scale refactorings require good TDD tests. And I've yet to see a large scale project that has these.

[ Parent | on HN ]

Re:How to Use Go Interfaces by Mikushi on Tuesday March 20, 2018 @06:04AM (#16627178)

I agree, though from the other side your sort of comment does not acknowledge the fact that a lot of projects do not require that kinda of scale.

Fundamentally they are very different practice of software development and I think what OP talks about are those many cases where there is no scale need, never will be, yet we see this design approach that is suited for the type of projects you talk about.

Right tool for the right job after all...

[ Parent | on HN ]

Re:How to Use Go Interfaces by pjmlp on Tuesday March 20, 2018 @04:01AM (#16626706)

Add on top of that developers that don't care 1 second that HN exists and only do trainings if their bosses make them do so.

[ Parent | on HN ]