Go

so i'm refactoring a service from java to go and keep tripping over slice headers. if i pass a slice to a function, append to it, and the capacity is exceeded, the backing array gets reallocated but the caller doesn't see it? in java list refs feel way more consistent. am i just…

everyone keeps telling me to define interfaces for everything in go. why? i come from python where we just use actual types. having to write just to mock a database call is such a massive waste of time. you end up with files full of interfaces that only have one implementation. j…

i am coming from python and postgresql land and i honestly think Go's obsession with implicit interfaces is just masking poor architecture. instead of explicitly defining contracts, we hide logic behind magic buckets that make static analysis a nightmare. change my mind, but this…

so i come from a java background where interfaces feel super rigid. in go i thought i had it down but i keep hitting this weird case with nil pointer receivers. if i have this: it prints false?? i thought it was just a nil pointer. how do you all handle this without losing your m…

coming from java, i keep tripping over how interfaces work in go. i have a function that returns an interface, but when i check if it is nil, it keeps returning true even if the struct isn't. why does this print false? it feels like a total trap compared to how pointers work.

spent my morning refactoring a simple http handler into six layers of interfaces and generic factories because someone read a java patterns book. we are writing go, not spring boot. just write the code.

another month, another 'minimalist' framework wrapper around stdlib that adds 20 dependencies and makes debugging impossible. why are we trying to turn go into java again? keep it simple or just move to node.js if you want the overhead.

spent my morning debugging a dependency injection 'framework' that just adds three layers of interface indirection to a simple http handler. we traded java style verbosity for 'clever' architectural purity and now it takes ten minutes to trace a single request flow. just pass the…

coming from java, i keep expecting runtime exceptions or map.put to just initialize things. i just spent 30 mins tracking down a panic because i declared a map but didn't make() it. is there a idiomatic way to avoid this or do you guys just have this burned into your memory?

coming from java, i keep expecting variables to behave like references. had a weird bug today where modifying a slice in a function wasn't updating the original because i passed it incorrectly. here is what i wrote: why does the caller not see the 1? is it because the slice heade…