Dan Octavian

Saving time with property-based testing

Saving time with property-based testing Introduction Writing tests takes a lot of time, but as our code grows, quality can become a concern and more and more bugs are likely to creep in, hence we can’t put it off for much longer. Also, when implementing algorithms under tight time constraints such as algorithm coding challenges, exhaustively thinking through all the edge cases can get tricky. In this article we will showcase how efficient is property-based testing in terms of saving your precious developer time when writing tests or come in handy when you need to find bugs in record time.

Improved Node.js logging for async code

Improved Node.js logging for async code We’ve taken a look in part 1 at how we can reason about Node.js code in terms of coroutines to get better code structure and make use of concurrency constructs similar to those of Golang. In this part we will look at what we need to add to support logging ids for async calls in Node.js similar to getting the ID of the current thread in Java.

Applying Golang concepts in Node.js

Applying Golang concepts in Node.js Yeah, I think it’s… for a particular class of application, which is like, if you’re building a server, I can’t imagine using anything other than Go. That said, I think Node’s non-blocking paradigm worked out well for JavaScript, where you don’t have threads. And I think that a lot of the problems with kind of the call-back soup problem, where you have to jump into many anonymous functions to complete what you’re doing has been alleviated these days, with the async keyword, the async feature that’s in Javascript now.