So my co-worker refuses to use Interface in Go because he dislikes php and interface is "the php way to do things". Anyone with experience dealing with this kind of ignorance?

Maybe force coding style and get approval from boss about it? so he can't nag anymore

I wonder what his rationale behind his hate for PHP is huh

@balte because of the interfaces

@david-hil ohh and he dislikes those because it's the PHP way to do it of course.

Not sure about this... does he use structs?
if yes, then he is using interfaces.

@gitpush I already did it, the team will have a discussion next week

@balte he claims that interface "hides" things, and make code harder to understand

Ask that person if pretending to be a software dev/eng. I think that person wants to remain at junior position for INFINITY AND BEYOND.

@Xamenyap perhaps you should educate him on how abstractions and APIs work. Or maybe he expects to see all of Twitter's code base when he makes an API call to search for #headInArse so that he might understand what the code is doing.

Why is the field of software engineering filled with so many bozos? 🤔🤔🤔

Reject his code from repo. With each rejected pull request, answer that it promotes bad coding practices.
This approach works for my son when I ask him to go to bed. After tenth or twentieth time it works.
It should work on your colleague too.

@Xamenyap how does an interface hide anything?

@CodeMonkeyG I already did, I explained to him how interface allows abstraction of low level codes and how it enables polymorphism. I also told him to read some Go standard packages sources to have a better understanding. But I don't think he seems to listen, or his programming mindset is really weak.

He'd rather do
if case 1
Then process case 1
else if case 2
Then process case 2
...

All his arguments are "It looks clearer to me that way", "Doesn't it look better that way?". This has happened for the last 3 days and doesn't seem to have an end. I gave up on this case and told the lead to take care of it

@mt3o The interface design was made by me. Let's say we have to process reports sent by our partners. Different partners use different format, so our task is to validate if the received format is supported, all required data is not missing, date time should be valid date value, etc. Then we need to create message deliveries in our internal format and push them to our message queue system to be consumed by other services
It can easily be abstracted in a few steps so I added the initial interface and a few implementations. The deadline is getting near so my task is shared with 2 other devs to help integrate other partners. Then this guy looked at the code base wondered why interface is used...

@Krokoklemme I don't know, he did not explain. But I guess it's his code comprehension problem