Shows the Silver Award... and that's it.

Thank you stranger. Shows the award.

When you come across a feel-good thing.

  1. I heard about Go, but never played. What do padlocks mean on the knots? They do not present all the time according to the trailer.

  2. Well spotted. The padlocks show when the neuron cluster can no longer be surrounded, and therefore cannot be killed.

  3. This game is basically go but with more variability in node connections. Go is an ancient game with a solid following. I wonder if having two eyes makes a group impossible to take.

  4. Exactly. There is a lot of inspiration from Go, with some changes to make it more fast-paced. The aim is to make it appeal to a slightly different audience.

  5. I'm just seeing this for the first time- is it mandatory again? I can't get past the sign-in page.

  6. Yes, it is mandatory again. So you have to sign in with one of the providers to play.

  7. Sounds fun 😊😊 feel free to share it as a gif or video as well.

  8. You are right, or rather, we had it covered by the wrong type of tests. I also briefly touched upon that in the post.

  9. Thanks for the feedback and for sharing your solution in Go, I'm glad you found it fun!

  10. Glad you enjoyed it 😊 Sounds fun with the Excel and VBA, I would love to see those solutions 😄

  11. Great that you managed to figure out the issue! :)

  12. Thank you for that amazing feedback, Preetham. I’m really glad that you enjoyed the puzzles 😊

  13. Great feedback, thank you for that 😊 I will definitely hold you up on the alpha-tester part 😄

  14. I updated the indexing of all the puzzles now, to be 0-based, as I didn’t see that as part of the puzzle😊 I also added a trailing comma (,) to each line in the list of instructions to help indicate that they are all one big sequence.

  15. Yeah I also think it's fine, just something I noted in the feedback as it's not always clear what is intended or what isn't.

  16. Thank you for the feedback, I am glad you found the mystery fun 😊 I will definitely consider aligning the indexing.

  17. Thank you very much. I appreciate that 👍

  18. I think it's a legitimate question. If an account sign up is necessary for the app, I'd prefer an option to use a throwaway email addr. I don't know what OP's goals are (no offence). I'm just not inclined to attach my personal account to any random site, especially before I even know if there's anything of interest behind the wall.

  19. I will consider moving part of the mystery before the sign-in wall as a small demo before requiring creating an account 😊

  20. Are you honestly suggesting that you'd trust some random dude's potentially shitty (no offence OP) attempt at user management over a known good solution provided by the biggest names in tech?

  21. I really like their overall point, but

  22. While not exactly the same, I definitely believe that the concepts are very related. In both cases, we are treating and interacting with the system as a black box, just like users do, without caring for how it is implemented.

  23. A good behavior-oriented test setup allows for easy debugging and access to logs for understanding what went wrong.

  24. If you change the implementation detail of one class and it breaks their tests, you are not testing it correctly. Unit tests should help you to do any refactoring and they should keep working.

  25. I see class methods and their parameters, as well as how a class is using other classes, as implementation details in the perspective of the system as a whole. They have no significance for the users of the system.

  26. You have it wrong my friend. If you change a public function signature, you are then changing their public interface.

  27. The thing is that we should not care about public interfaces of classes in tests, as users of the system does not care about them either. How the system behaves is what matters.

  28. Any conversation that ignores the nuance in a complex system ("Unit tests are dead!") is usually falling short of the mark.

  29. Seems pretty good for microservices that are sufficiently micro. I found this approach got a little out of hand when we had too many external dependencies, though. Every single test requires you to mock lots of dependencies just to test something simple. But that's only IF you treat the whole thing as a singular black box. In our case, we were able to split the code up to different subsystems that interact with each other in a few predictable, non-interesting ways, then basically apply everything you are talking about to those. Tests are much more readable, and easier to write, so overall it's a pretty good approach.

  30. Thank you very much for the great feedback. We are seeing the same things as you are experiencing. What really helped us make it manageable even for a bit larger micro services is reusable methods for arranging all the test data, which would also take care of mocking anything required for that. This means that each test would only need to concern itself with mocking things that are directly impacted by the “act” part of the test which, in our cases at least, is typically not much 😊

Leave a Reply

Your email address will not be published. Required fields are marked *