Execution flowcharts can be a useful tool for visualising and understanding how our code behaves at runtime.
Using a simple combinator, you can make your data-driven tests cover a wider range of scenarios while keeping test code neat and readable
Is there a simpler way to write acceptance tests?
How might we tweak the familiar UML "class diagrams" to instead model Typescript code?
Recent experiments with mock data reveal a surprisingly versatile tool that can boost developer productivity and enjoyment.
How to run multiple requests in parallel and combine the results.
Using wireframes to depict elements and interactions together
I am on a personal and professional mission to write bug-free code.
It can be tempting to think that we are the reason we got hired (or rejected). But I think there are many other dynamics at play.