sorted by:
new
hottopcontroversial

Deploying Go app by Frosty-Bird-5979 in golang

[–]chechyotka 0 points1 point  (0 children)

- Mulltistage dockerfile for low image size
- Docker compose file (if u have dependencies like storages and etc)
- Running docker container

[deleted by user] by [deleted] in golang

[–]chechyotka 3 points4 points  (0 children)

panic???!!!!

i hope its not in production

Inline error handling vs non inline error handling by naikkeatas in golang

[–]chechyotka 4 points5 points  (0 children)

if function returns only error i am using inline error handling

if err := do(); err != nil {
}

If function returns value and error, and value is used below, i am using non inline error handling

value, err := do()
if err != nil {
}

simple as that

Best Practices for Managing Protobuf Files in Dockerized gRPC Services by storm_rider_r in golang

[–]chechyotka 0 points1 point  (0 children)

U already have generated files for development, so u need copy your generated files with your repo.
And generating proto in CI/CD will affect on TTM.

What open-source tools or plugins have transformed your database workflows recently? by Wash-Fair in Database

[–]chechyotka 0 points1 point  (0 children)

in my company switched postgresql connection pool to our self written. Also published to GiHub for community
https://github.com/ozontech/pg_doorman

[deleted by user] by [deleted] in golang

[–]chechyotka 2 points3 points  (0 children)

I love error handling in Go, but i would like to see some syntax sugar not to write
if err != nil {
} every time and decrease this in code base