Coin change - solving dynamic programming in Elixir Dynamic programming is a tough technique to master. You start with the obvious, like Fibonacci's sequence, but suddenly become overwhelmed when trying to sense the pattern and approach in other problems. In its sense it is quite simple, when you know what steps to follow. In this article
Sum of Subarray Minimums problem I've tackled a problem which I found to be very problematic for me, so I've decided to make a detailed analysis of it here. The problem can be found here: https://leetcode.com/problems/sum-of-subarray-minimums Let's describe problem in more detail: Given an array
Software architecture Architecture boundaries Goal of architecture It is often said that software architect is not a programmer per se, and focuses only on high-level issues. Software architects are programmers, but on top of that they guide code to be better designed to maximize productivity. Design focuses on code to be easy to develop,
How to handle money in software (Kotlin) Main role of majority of software is to generate or save money. Good portion of this software also directly work with money. Bad implementations can cause rounding errors which can lead to losing money or worse. There are a lot of things that is to be considered when we want
Software architecture Component principles In this part we'll briefly introduce principles applied on component level. Components are units of deployment, for example .jar files in Java. Well designed components should have an ability to independently deploy and develop. Component cohesion These principles decides which classes should be grouped into components. There are
Software architecture Design principles The purpose of the design principles is same as that of bricks in in the building. That means that as long as quality of bricks is bad, architecture quality won't matter much. Design principles are set of rules applied at the module-level of software. We call them SOLID
Software architecture Programming paradigms The second part of the book dives right in to the heart of the architecture - the code, particularly the programming paradigms. There are three paradigms included, and according to book there is very little possibility that any more does exist. The three are: * Structured programming * Object-oriented programming * Functional programming
Software architecture Behavior and structure There are two values that each system provides: behavior and structure. Programmer's job is to make machines behave in a way that saves or produces money. If the machine violates given requirements, programmer fixes the problem. Many of them believe that it's the entirety of their
Software architecture Intro to the Software Architecture This is the first post in the Software Architecture series. In them, I will write about my personal opinions and understandings of topics covered in the book Clean Architecture by Uncle Bob. For starters, let's define what exactly does it represent. Software architecture are all the low-level details
