If you’ve ever joined a new project you probably know the excitement of being presented with a brand new source code. As soon as you’re assigned your first tasks the excitement turns into frustration, because it’s not easy to fix this simple bug… Even you’re an experienced developer.
Today I’m trying to address the issue of approaching an unknown codebase. I’ll give you some advices and tricks I’m using to make new code easier and quicker to understand – even without understanding it all 🙂
Today I’d like to share with you my experiences in becoming a digital nomad and starting a world trip.
I’d like to show you how software development – and this blog! – helped me starting a completely new life 🙂
Continuing to examine new C# 8 features, today we are taking a look at a bit controversial one. It’s a possibility to provide default interface methods implementation.
How will this possibility change the way we write C#? Why is it being introduced? I’ll try to address these questions today 🙂
C# 8.0 brings us another nice feature called slicing. In order to make it possible, two new concepts are introduced: Indexes and Ranges.
Let’s see how this tiny feature is supposed to make our life easier 🙂
In the few next posts I’d like to share with you some of the most interesting C# 8.0 features. Today we’re going to start with examining nullable reference types. Let’s see then 🙂
On the 5th of November 2018 I had a pleasure to attend Dotnetos Conference in Warsaw. It was a first conference oriented towards a single topic – .NET performance – I took part in.
I didn’t know what to expect from this event, as it was much smaller than other conferences I used to attend and actually organized by 3 .NET geeks (more about them later 🙂 ).
In today’s post I’d like to share with you my feelings about the event. I’d also like to smuggle some topics that were covered during the sessions, so you can stay up-to-date with .NET performance world’s trends and dig into them yourself.
Hey guys, I hope you’re doing well 🙂
Today I’d like to announce you a change that will happen on my blog in the days to come, so you’re not surprised post factum 😉
Knowing the idea and main benefits of JIT compilation from the previous post, we’ll now see how it fits into .NET applications execution model.
By execution model I mean a process of having a .NET Framework application actually executed on the machine (CPU), starting from having its source code written. It contains all steps and actions necessary to happen in order to transform source code (like C#) into machine (assembly) code and execute it.
Have you ever heard the term JIT? It’s an acronym for Just-In-Time. JIT compiler is a tool which performs the JIT compilation, which is a crucial feature of .NET applications. Let’s say a few more words on it today 🙂