go
Recently, I reviewed some coding interview questions. There was a problem with which solution used DFS over a graph with recursive calls. My solution was in Go and has a recursive function: func dfsVisit(curr int, graph map[int][]int, currPath *[]int, visited map[int]struct{}) { ... } * curr represents the current
go
I worked as a front-end engineer in the early days of the current company. We had used Angular [https://angular.io] for the time being and moved to React [https://reactjs.org]. React was a framework that actively used higher-order functions. I always have thought Javascript is the most "
go
A few days ago, a friend of mine posted a question about the Go concurrency control. The question was, "Can we assure that doSomething(0) always runs before doSomething(2)?" The answer would be, "No." We cannot determine the order in which goroutine can run at
go
Two years ago, some engineers in my company had a study on the book "Hands-on Dependency Injection in Go." [https://www.amazon.com/Hands-Dependency-Injection-Go-maintain-ebook/dp/B07FSKBWVR/ref=sr_1_2?dchild=1&keywords=dependency+injection+in+go&qid=1606703396&sr=8-2] Overall, the book was
