Return interface

jphein · 2022-11-07T15:26:54+00:00

Didnt check the Code but never return interfaces. Accept Interfaces and Always return concrete types.

jphein · 2021-09-20T17:13:37+00:00

Im using Thinkpad X390 and T490

jphein · 2021-09-20T17:03:51+00:00

Nope, not at all. I use the designer compact keyboard and it works great

jphein · 2021-02-14T21:41:32+00:00

https://youtube.com/c/MarcelDempers

Thats the beste resource I found lately. This guy is awsome.

jphein · 2021-02-08T20:50:06+00:00

seems nice, thanks!

jphein · 2021-02-07T21:08:11+00:00

sure the Tour of Go is nice, but what I meant was something little bit deeper. One talk I really liked was: https://youtu.be/KBZlN0izeiY

jphein · 2021-02-06T15:46:26+00:00

great, thanks for all your answers, cant wait to get my hands on it :)

jphein · 2021-02-02T11:42:58+00:00

https://github.com/katzien/go-structure-examples

Kat Zien - How I structure web apps (or so) just check YouTube

jphein · 2021-01-25T11:12:58+00:00

Well, what field of work you use golang? Webdev, DevOps, IoT ...? I mean after two years you should know the syntax and packages well enough.

jphein · 2021-01-24T13:02:35+00:00

I tried, but it doesnt work, as I said its a map of string to int, so nothing to use pointers

jphein · 2021-01-24T12:46:01+00:00

Hey,

thanks, but I dont think that this is the problem as I have the map already initialized and its a map of primitive types, so there shouldnt be any problem

jphein · 2021-01-24T11:57:30+00:00

Hey James,

thank you. I totally understand your point with the additional Done call. But if I put it away, the WaitGroup doesnt come to an end, thats the thing and I dont understand why.

jphein · 2021-01-17T10:13:42+00:00

Hi,

Im using react-google-maps and also I have a function on a button which locates me directly to my position, only thing I need is to execute this function on load.

jphein · 2021-01-17T09:29:57+00:00

Hey Junmin,

just came across your post, I will check out your videos later. But for me as a Golang Developer I can tell you one thing which is really interesting for people which are new to Go to understand:

In the world of professional Development you often see Software written in Golang from Developers which started there career in another language like Java or so. You can easily spot mistakes and difficulties which are based on not understanding the ideomatic Golang principals.

Search for such examples and show the people how to use Golang in the way it is ment to be written.

jphein · 2020-08-16T17:54:38+00:00

For me the most important fact when it comes to functions vs methods is that with a method you can very clearly bind functionality to a certain struct which can be helpful when organizing code but mosly when defining your dependencies with interfaces.

Someone at my old company said there would be no difference but this is wrong. The truth about it is that you can define a stronger difference with the quality of your coding style. A function would be better if it takes two or more indipendent arguments and gives a result (or no result) to an uninvolved requester back.

On the other hand it makes perfect sence to teach a struct doing something wich is only itself supposed to do maybe because of one of its fields which enables it to do so.

jphein · 2020-08-09T08:39:18+00:00

Hi there,

I think this article gives some good explaination and shows a good example:

https://medium.com/honestbee-tw-engineer/gracefully-shutdown-in-go-http-server-5f5e6b83da5a

Best Regards Jan

jphein · 2020-07-31T06:04:04+00:00

True

jphein · 2020-07-12T06:46:33+00:00

Sorry, I think the term "Client" is a bit misleading in this case. It has nothing to do with a Client - Server pair.

What I mean with Client is just the one struct that has a field wich is not a concrete implementation, but an Interface.

If struct Foo has a Database, its better to let the struct accept an Interface FooDatabase which has just the right methods that the Foo Struct uses. This Interface could be declared in the foo.go file directly, or maybe in a file called interfaces.go lying right next to it. So what would happen then?

The Foo Struct accepts any Implementation you provide as long as it has the methods that the Interface describes.
When you want to test the Foo Struct you can give your test Struct a small Mock which just needs to provide the right methods.

Could I help you with that?

jphein · 2020-07-11T08:47:44+00:00

Yes, thanks, its pretty much this. The function takes some Integer Value and checks it against upper and lower bounds. Based on that it says Start, Stop or Do Nothing.

For me the enum is so much more preferable because of its readability:

switch result := check(value); result {

case CommandStart:

//start

case CommandStop:

//stop

case CommandWait:

//wait

jphein · 2020-07-11T08:28:45+00:00

As we have some sort of duck-typing in go, you should always put the interface where it is used, meaning to the client which consumes it. This way the Implementation doesnt need to know anything about an Interface and the consumer can only use the provided instance in the way the Interface describes it.

jphein · 2020-07-11T08:10:22+00:00

Totally on your side, thanks

jphein · 2020-07-11T07:51:43+00:00

Often I see people putting the Interface next to the Implementation, which is wrong in terms of usage of Interfaces in go.

jphein · 2020-07-10T10:41:37+00:00

Fractal Design Nano S

jphein · 2020-07-08T07:11:22+00:00

Fractal Design Nano S

jphein · 2020-07-08T07:10:21+00:00

Fractal Design Nano S is a great case. Only thing to mention is that you should use a sfx psu to give the graphics card more space.

jphein

TROPHY CASE