i was amused that a dude with a CS masters was of the opinion to make interfaces before you even know you need to have more than one implementation too...

i always know i'm gonna need an interface, because i intend to design a generic type and so i design a common interface for using it in a common way and where the code needs to be specific it can type assert it to the type to access the non-interface methods

fiatjaf is so annoying with how he reaches for generics all the time in go but that's only because they renamed interface{} to 'any' and he type asserts these buggers constantly without using the comma ok syntax, and that's fine if you keep that internal but if you do that shit with other people's shit you are looking for some pain