go-structure-examples VS svc-fizzbuzz

I have a question, I am trying out hexagonal architecture for one of my projects trying to follow this repository example and I ran into a slight problem.

Just fyi, that repo is NOT considered standard, and in fact, is often advised against. The structure of your code should depend on its complexity and how interoperable with other projects you need/would like it to be. I suggest watching this talk on structuring your code and taking a look at this companion repo to decide which will be the best way to structure your code, depending on your needs

Kat Zien's excellent talk, presentation and code samples can be found here.

Thanks for the video, I'll take a look at it. And I checked the repo, I liked how the new is structured: https://github.com/katzien/go-structure-examples/tree/master/new

So here’s where I normally tell people to start off: check out this video and this repo in regards to the main 6 ways of architecting your Go applications.

Watch this and give this repo a look.

Am I completely fumbling it by approaching this the wrong way & if so what should I do differently? I have searched a few repos like this which redefines the same entity in multiple places which I feel is a violation of some sort, and this which the author had to resort to moving some files outside to overcome a circular dependency (see comments inside their handling.go file).

Really surprised I haven’t seen katzien/go-structure-example and her GopherCon 2018 talk about structuring your Go projects mentioned yet

Let's agree to leave the MVC model for OO languages. A better architecture would be something like katzien/go-structure-examples

For my projects I use this code organization (https://github.com/hugdubois/svc-fizzbuzz). I don't necessarily use dependency injection because I consider go packages to be a singleton (with a setup function).