I have to admit the Go base of a stack gets super ...
# golang
m
I have to admit the Go base of a stack gets super dirty and error prone once you start mixing existing resources with resources created by the stack. Is there any best practices here, since the data types for these different scenarios generally are incompatible with each other is feels more like hacking at this point than structurally typed infrastructure.
b
If you use the
get
functions this is pretty standard practice, are you using those?
m
I rewrote some of our code and that made more sense. I’m may simply be expecting it to be too close to rust or ts in terms of asynchronous stuff.
But Lookup makes sense some places, Get other places. I guess that’s my confusion regarding the different types.
b
I always use Lookup, very rarely Get
m
Then I’ll do the same! 😎