Well, sure, but Reader and Writer are interfaces existing in java too :)
Anyway I think we agree on the general issue, but actually I suspect go's approach _does_ solve some bad design issues that crop up in common OO, namely the fragile base class one.
I just don't think it impacts the misspecification one.
The Go standard io library has a Reader interface:
a Writer interface: and a ReadWriter interface which uses type embedding to combine both: Idiomatic Go will break interfaces up into pretty discrete bits of functionality and use type embedding to build up more complex interfaces. The article does show this a little bit with its seekable interface but fails in some other areas and I kind of wish it just used the real io package interfaces or else examples of something not covered better by the actual Go standard library.