Array destructuring – revisited
Do we know everything about array destructuring?
Functional Programming in JS, part II – Immutability (Vanilla JS, Immutable.js and Immer)
A sequel to an article about composability. In this article, we will focus on immutability.
Functional Programming in JS, part I – Composition (Currying, Lodash and Ramda)
In this series of articles we will go through a soft introduction to functional programming in JavaScript.
(Un)remote Retreat 2020: Exploring Brodnica Lakeland
Getting together with the whole team on the first (un)remote event!
Top Locations For Remote Work: 4 Engineers Share Personal Experience
We share our thoughts on working remotely and what to consider when choosing the best location.
How to build GraphQL APIs with ASP.NET Core & HotChocolate – Part 1 – Setup
GraphQL with ASP.NET Core is much less intimidating than it seems. Let me show you how straightforward it can be.
Lightweight QA Strategies For Startups That Care About Quality
Define the QA values, find the balance between manual and automated testing, and discover what does Dumbledore has to do with automation.
Setting a QA Process In a Startup From Scratch
Is there a room for QA at startups? Where do you start building a process? What questions can help you identify problems you will need to solve?
Core Cypress Lessons We Learned That 10x-ed Our E2E Automation
We moved our e2e suite from CodeceptJS to Cypress to reduce the E2E flakiness and speed up test development. Here is what we learned over the first month.
Mocking Callbacks with OpenAPI and Prism
Callbacks are outgoing, asynchronous requests that service will make to some other service in response to an action. They are very similar to callback functions in popular programming languages like JavaScript. However, they are executed at the API abstraction level.
1on1 with Design-First Contract Testing Your OpenAPIs
A quick introduction to validating your APIs with Prism
How to Mock HTTP Servers With Stoplight Prism & OpenAPI
I’d like you to reach back in your memory to the last time you built a web application. Remember when you (the front-end person) and “The API Team” had to sync over an API to build a feature together?