This is a group for anyone interested in new technologies, cloud computing, e-commerce, networking, etc. We invite developers, devops, architects, revolutionaries, and visionaries to join our free sessions to learn and discuss. Hosted in Berlin, Germany by NewStore, you can expect interesting speakers, great crowd, food & drinks. For more details of upcoming events, please visit www.newstore.com/digital-retail-events.
ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-yszygk1cpEc.html it's better to use subtest for running table tests. Example for _, tc:= range tt { t.Run(tc.name, func (t *testing.T) { // smth } } in this case you see clear name for every subtest. and you can run test and filter by name for subtest
the problems with microserices are no different than the problems with microkernels. go back and read the books on the failure of the MACH kernel at IBM planned to be used on OS/2 and AIX.
At 28:10 we can see two complete similar dom items have different class names .. does this mean you are generating copies of each style class to apply for different instances of an item using them? How is this with performance?
TDD, Fixtures, Golden Files, Test Helpers returning cleanup func for defer statement, custom go test flags, TestServer() as part of pkg's public API etc. This was really good and rich talk, thank you!
