This week was Basta week again. As usual, many thanks to all those who attended my workshop and my presentations! If you saw my Microservices talk, you may remember that two technical issues occurred during the talk. I was going to follow up here with explanations, but unfortunately it turned out that there is nothing more to say! I had trouble, in one of my demos, to talk to a service through a message queue, but that was only because I stupidly forgot to pass that service the configuration parameter to actually set it up correctly for the message queue (so it was talking to nothing at all!).
The other problem was that my demo app didn’t correctly update multiple concurrent windows when running on AWS, but I can’t reproduce that issue now and so it seems that the network connection was to blame after all. Here are the links where you can access my slides and samples:
Sometimes I don’t fancy debugging a piece of code in the browser. I mean that as in “use the debugger” - I’d much rather see some log output. This can be more useful than step-by-step debugging because the program flow is not interrupted, which can cause strange behavior in its own right, and because log output makes it easier to see how values go in and out of functions as the program runs through its flow.
Since I prefer writing code in a functional style, I often have the problem that it’s not easy to quickly insert
console.log calls. For instance I was just looking at this piece of code: