Posts

Personal essays and the occasional technical deep dive. Weekly writing on software engineering lives on the newsletter.

2026

  • My father was a mathematician who became a software engineer at Energoinvest in Sarajevo, built the computers I grew up on, and taught at a technical school. His birthday was recently, so let me tell you his story.

  • Nobody starts with credibility. It is an output of writing in public, not a prerequisite for it. Why the question ‘who am I to write?’ is backwards, and why you should publish anyway.

  • AI više nije napredni autocomplete, postao je sposoban član tima koji menja čitav lanac rada. Šta to znači za inženjere, lekare, advokate i sve nas, i kako da iskoristite trenutak.

2022

  • This text present one approach to Software Development called Interface-Driven Development. Its purpose is to make software design better and more efficient.

  • How we can ensure (automatic) high code quality in .NET even before code review? By using static code analyzers and some other tools.

2021

2020

  • Ten books, language-agnostic, from Clean Code and The Pragmatic Programmer to SICP and Patterns of Enterprise Application Architecture, plus honourable mentions - and why the author of a book is usually the next best …

  • What you can actually build with .NET, and with which part of it: .NET Framework, .NET Core, Mono and Xamarin, written in 2020 as .NET 5 was about to fold them into one.

  • From time to time we hear about COBOL, that there is demand for it. What is it and why it is happening now?

  • Sharing knowledge is one of the main pain points in today’s software development. It also promotes innovation and developers productivity within developer teams. So, how we can produce a framework for sharing …

2019

  • A reference list of the things every C# and .NET developer should know: the CLR and garbage collection, async, LINQ and Entity Framework, debugging, profiling, and testing, with the nice-to-know topics separated out.

  • Being a developer these days involves sometimes developing features and fixing bugs at a fast pace, which can result in code that is difficult to maintain in the long-term. In other cases, we want to make the most …

  • My strong opinion is that it is a must. A developer learns plenty from tutorials and examples, but nothing replaces a good book: tools and frameworks come and go, the thinking behind them stays.