Objects in a program should be replaceable with instances of their sub-types without altering the correctness of that program Robert C. Martin “At the beginning, keep things simple and concrete – stick to that as long as possible/necessary.” “Correct abstractions usually come after careful thinking and initial minimal, concrete implementation” “Incorrect abstractions usually come from […]
SOLID – Open/Closed
Def. Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification Robert C. Martin In object-oriented programming, the open/closed principle states that “software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification” Usually, the first impression that comes out about this principle is confusion: it […]
C# and Roslyn – Immutable types
Child upbringing – by Pajsije
Recently I have read the article about the monk Pajsije from Mount Athos Greece. The article is about his notes for parents related to child upbringing. His pieces of advice I consider as evergreen – a perfect blend of old times wisdom and newest standpoints on how to raise your child. Here is they are, […]
Pipeline Pattern in C#
WCF to gRPC – in .NET Core
JS – event loop
Psychology of code readability
https://medium.com/@egonelbre/psychology-of-code-readability-d23b1ff1258a – we remember 4+/-1 item in our short memory, then they fade away. – in our brain facts/knowledge pieces are grouped, chunked and CHUNKS are linked. – we process input with our focus/locus of attention (one thing at the same time in the same space) – focus/locus is called CONTEXT – MENTAL MODEL is […]
ReactiveUI – state lifting & event streams binding
https://reactiveui.net/ https://github.com/reactivex http://introtorx.com https://channel9.msdn.com/Shows/XamarinShow/Lifting-App-State-with-Geoffrey-Huntley ReactiveUI – world where Observable is the king
Design Patterns – how to use them?
Design pattern – how to use them? 1. Remember the pattern category (creational, behavioral, structural) 1. Create simple, single sentence pattern explanation 2. Associate simple use case with previous explanation Whoila! You have a design patterns toolbox!