This article presents a model for describing the architecture of software-intensive systems, based on the useof multiple, concurrent views. This use of multiple views allows to address separately the concerns of thevarious ‘stakeholders’ of the architecture: end-user, developers, systems engineers, project managers, etc.,and to handle separately the functional and non functional requirements. Each of the five views is described,together with a notation to capture it. The views are designed using an architecture-centered, scenario-driven, iterative development process.
This is part of a three part examining the underling mathematics and mechanics of Asynchronous programming with javascript When i wanted to make sense of the continuations , i started from the basics…
GitHub flow is a lightweight, branch-based workflow that supports teams and projects where deployments are made regularly. This guide explains how and why GitHub flow works.
I’ve written this article series, to help you get a good sense of how production Haskell is written at a company like Klarna and what to avoid along the road.
Since the React hooks API was introduced, a lot of questions have risen about whether or not React hooks will replace Redux. In my view, there is little overlap between hooks and Redux. Hooks didn’t…
Next js is a fast upcoming frameworking being used in some huge companies, but what is it? Let me tell you what Next js is and why you should be using it!