Must be a hell of a test suite
https://go.dev/play/p/3UNqnYG3ZiI this is what I came up with now but HasCycles isn't working properly
I thought you didn't want to build graph
I can't believe you call this "most straightforward"
Ise here someone who did microservices with monorepository? Is it a good way to small app with just 5 microservices?
How else would you prevent brute force login attempts?
I see the immediate benefit of error logs. But what about access logs? Would you implement them for your own web project
What is good practice for logging efficiently? Is it something like store 10k logs in memory, then do a batched write to disk?
What do you guys think about https://serviceweaver.dev/ It's maintained by Google but fairly new I wonder if it's worth a risky try? 🤔 It's only relevant if all your service...
What would you use them for? Isn't the DB a log of itself
Anyone volunteering to push for linting in compile time? 🙂
Why not just make the correct way to do things the way that takes the least code?
Guys, should i put go.sum to gitignore?
What about if you have a defer or goroutine that checks it?
Обсуждают сегодня