Комментарии:
👏👏👏
ОтветитьThis video is supported by beer reviewed research.
Ответитьjust put your code into packages with well defined purpose and context (no 'adding' package which shares both beer and review for some stupid reason). Have you seen any package in standard library that were grouped by 'adding' or 'listing' function? Why the hell I should even do that? Just code packages, don't try to do any fancy structure, it's all bullshit that based on no foundation at all.
ОтветитьHexagonal hell. 13 folders to keep 17 files. 😅
ОтветитьGreat talk.
ОтветитьVery useful talk! Which approach you use depends entirely on the size and condition of the project but I think that hexagonal architecture can be more better for me. Thank you for everything Kat😊
ОтветитьGood talk, although one small correction DDD = Domain Driven Design (not development), it was proposed by Eric Evans.
Using ports&adapters vs other clean designs and packaging-by-feature vs packaging-by-layered-feature is still a topic that brings controversies within teams, in a way my gut is that programmers embrace them while coders are scared of/confused by them.
How to avoid the init()? Even in testing func, we have to init the server and db to test. How to avoid in this case?
ОтветитьGreat presentation. Thank you.
ОтветитьThe talk was OK. Extreme over complicated and messy project structures. The best thing with Go is that Go is simple, let's keep it simple! There is no point in structuring a Go project as a Java enterprise application or a .NET project. I keep the structure of my services as simple and flat as possible.
ОтветитьAmazing talk !
ОтветитьExcellent...
Ответитьthank. you.
ОтветитьThe moment she couldn’t open the terminal I stopped!!
ОтветитьShe can’t open a terminal in vscode wow
ОтветитьThanks a lot ...
ОтветитьGreat talk! Thank you very much for putting this together. This is quite helpful to this "new gopher".
ОтветитьI'll stick with flat for a while!
ОтветитьGood talk, but DDD is actually Domain Driven Design (not Development) and it was defined, coined and popularized by Eric Evans (not Vaughn Vernon).
ОтветитьExcellent. We could use more talks on how to organise code in larger projects as most examples never get to the kind of complexity where architecture, interface design and import structure actually start to matter.
Ответитьawesome
ОтветитьThank you for putting this talk together!
ОтветитьGetting started with GoLang and this is golden ! thanks much Kat !
ОтветитьOne of the best talk i've ever seen in my life. Very clear explanation, thank you!
Ответитьawesome
Ответитьgreat talk, thanks!
ОтветитьExcellent Talk! Thank you!!
ОтветитьOne of the best talks I've ever seen. Thank you!
Ответитьthank you!
ОтветитьThis was really helpful for me, thanks! Also, it's always great to see another woman developer nailing it! <3
ОтветитьGreat talk!
ОтветитьGreat talk, really helpful to understanding the different approaches. It really does depend on the use-case!
Ответитьwho has the girl's twitter? need more.
ОтветитьI think she didn't help true beginners because she wanted to sound smart.
Ответитьnice talk, thanks
ОтветитьUseful talk. But please, PLEASE stop with those absurd GIFs. They are very distracting and unprofessional.
ОтветитьLinks in the description would be awesome
ОтветитьGreat Talk on Folder Structure! Really helped me. Go Go Golang!!!
ОтветитьGreat talk!
Ответить