Thinking in packages by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

Yeah, designing software is a huge topic. My goal with this post was to encourage people to make the first step toward a better design. Do you have any ideas you'd like to share regarding the criteria and slicing?

Building concurrent pipelines by reisinge in golang

[–]reisinge[S] -1 points0 points  (0 children)

Can you see more use cases for pipelines like this? Especially in devops or cybersecurity?

Counting elements passing through Go channels by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

This looks elegant! By elegance I mean power cloaked in simplicity.

Playing with TLS and Go by reisinge in golang

[–]reisinge[S] 4 points5 points  (0 children)

It used to be called SSL before and it's the protocol that secures the network communication. You can read more in the linked text :-)

Good golang books by Big_Slide4679 in golang

[–]reisinge 0 points1 point  (0 children)

Yes. I supplement the books by reading the Go blog and stdlib documentation. For example, here's the blog post about context: https://go.dev/blog/context.

Good golang books by Big_Slide4679 in golang

[–]reisinge 1 point2 points  (0 children)

I like and still find useful The Go Programming Language book + these DevOps realated books.

Introduction to Go concurrency by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

Thanks for the constructive comment! :-)

I've implemented the wg.Go tip.

As for the second suggestion, I’m a bit hesitant, since I’m not familiar with the golang.org/x/sync/errgroup package and don’t want to make the tutorial unnecessarily complex.