justforfunc #15: a code review with logging, errors, and signals 

35:20 in a thread safe way ... with two concurrent inset videos 😁 nice intersting review, that's again. look forward to the next one.

Congrats, awesome as usual! Also, very happy to learn you're increasing the frequency to twice a month and wish you all the best with it, especially that you can sustain it … I can imagine it costs a bit of time to prepare an episode. One suggestion/idea, since you'll have some room to fill: incorporate other Gophers. Something like peer programming or the like. Since we Gophers are gregarious animals, this aspect (how to code in a team, how to work together to achieve something) would be beneficial as well, methinks … KUTGW!

As usual a great learning experience, thanks for the dedication you put on it.

Great video, makes you really notice the subtle differences in code

Awesome video. This video taught me lot of little things which i can use in my day to day code. Thanks!

Good stuff! One tips - you can run "echo $?" to print the last return value. More generic and perhaps easier to follow than the arrow in your custom prompt. :)

That's tech diversity! You write Go (bootstrapped at Google) in an Apple computer, using a Microsoft editor! :D

I love this video format

FWIW, both `killall` and `pkill` allow to send a signal to a process selected by name. Killall wants a name equality and pkill does pattern matching. So here `killall -2 logpipe` (or `killall -INT logpipe`) would do. Both are available on MacOS.

nice editing !! this must take quite a long time

Thank you! Really cool videos. Keep going!

I'm in love with your videos :D

Certified lit

Awesome video! More of this! 👍

Thanks, Can you cover code generating (in deep) too?

is there a way to define logging severity without using stackdriver logging client package. whenever i am using fmt.Println in my service all those statements i can see in stackdriver logs as INFO logs . Is there a way to do it?

Francis, how do you have that different "not equal" sign in your editor? And the channel arrow is quite prettier also, is it an extension? If so, which one? BTW, your videos are amazing. Thanks!

Thank you very much!

Thanks, really love your show. BTW Error numbers are actually standardised en.m.wikipedia.org/wiki/Errno.h Respecting the standard would allow a calling program (such as a shell script) to take a decision based on the error's value. Returning 2 everywhere is probably not a good idea ;)

Awesome video! Any reason to use fmt.Print() and os.Exit() instead of log.fatal? Thanks!

What plugins do you use with VScode for go lang development? I really like how your != symbol looks like, I would like to have that kind of symbols.

Is the "break loop" pattern a good practice to follow? You could achieve the same thing using this pattern, which uses more standard syntax. loop := true for loop { if someErrorCase { loop = false } }

Hi. I would like to see entire series of "Code review in depth for programming beginners" to fill up the gap after learning syntax and before ability to code some simple meaningful programms. I found that almost nobody teach how to solve tasks for beginners. For me it looks like every instructor expect that after learning syntax and basics noobies will be able to write calculators, tic tac toes, to dos and so on. No. As noobie i can tell.. no... i am not able to glue conditions, maps, interfaces, methods, constants together to get something working. I just dont know how to construct it. I dont know the logic. And reading someones code does give me nothing because i do not understand why that code is written exactly like it is. Why this is constant, why this is variable, why this is self invoked function, why there is used this method and why there is 2 functions instead of one and why there is used pointer and there an adress. To build that stupid ToDo ap i need to understand why this and that must be done before something else and why it must be done exacly by using these techiques. So... i think some kind of noobie friendly code review could help. Lets say... code review of registration and login system. Or code review of some CRUD system. From frontpage to backend and sql.

Hello Francisc. How to overcome fear, that I'll never be hired as go-developer?

Couldn't you just call log.Fatal?

I don't know about go-flags, but the standard flag package will happily parse an empty string flag, e.g. logpipe --project= This would make ProjectID an empty string. Maybe this is why the check you remove at 11:54 was there?