@aditiitwt If nobody sees or care about your backend work. You're doing it right. I shouldn't be made aware that there's a possiblity my system crashes at 3AM
Designers share visuals.
Frontend developers share deployed links..
Backend developers ship systems nobody sees...
So how does a backend dev show their work?
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
STOP ASKING CHATGPT THINGS YOU CAN GOOGLE
@VladimirAtHQ@bidhanxcode Lol.
You return the error as value like you would return a string or an int from a function
So
func someShit() returns (err)
When calling someShit(), if it spawns a critically error, you gotta check it
err := someShit()
if err != nil {
// handle the error
}
Everytime btw
@sukasvn@bidhanxcode Forgive my curiosity (and laziness), how do you normally handle errors in Go?
I heard something about
try{
} catch(err){
} finally {}
not being part of the specs. But is it really that bad?
Google uses Go
Meta uses Go
Microsoft uses Go
Amazon uses Go
Uber uses Go
Dropbox uses Go
Cloudflare uses Go
Twitch uses Go
Docker uses Go
Kubernetes uses Go
PayPal uses Go
Shopify uses Go
What’s stopping you from learning Go?