The inspiration to write the following little pondering came to me while I was reading the book Teach Tech Together
There was a section about mental models introduced with a pretty neat description:
“It is a simplified representation of the most important parts of some problem domain that is good enough to enable problem solving.”
While reading the section, I happened to realize that a metaphor alone might also be a simple mental model, and it could be a great way to build new or derived software engineering models.
Metaphorical language is a language that consists of a wide range…
As I promised in my last post, I have written this text to show how Azure, GitHub, and NextJS can play nicely together. I wanted to use Github actions to deploy my application to Azure, but I stumbled on a number of issues on my journey. So I hope the following summary of my experience will be helpful to everyone who wants to walk the same path.
Actually, finding a way to deploy my app felt like a detective’s investigation. I needed to search for bits of information in various different GitHub issues and blogs.
So, let’s start with an…
Last month I faced the challenge of running NextJS on Azure web apps.
As I mentioned in one of my previous blogs, Azure is an excellent piece of “software,” but you are likely to experience plenty of bugs while you are on the road to install your “not .NET application.”
I hope the following tutorial will help you avoid some of my mistakes.
Before the start, there are two things to consider:
1) Vercel (the creator of NextJS) strongly recommends using their own hosting. It’s understandable since providing hosting for NextJS is probably their primary model of monetization. …
Have you ever wondered why some technologies are still with us, even after they were proved to be quite bad? Maybe, the Lindy Effect might explain that. Those of you who have read Taleb’s books Antifragile or Skin In The Game are probably familiar with this concept.
Let’s look at the definition:
The Lindy Effect is the idea that the older something is, the longer it is likely to be around in the future.
Or see the more detailed explanation from here :
Take a technology like bitcoin, for example.
According to the Lindy Effect, because bitcoin has been around for…
Today, I would like to write a short text about what I have learned during the super crazy year 2020.
As usual, I had made resolutions on what to learn in the year 2020. And as a rule, it happened that I failed to meet some of them. My plan changed due to new contracts or projects. I had to acquire different skills or knowledge than I had anticipated. Nothing surprising :).
These days, I’m not entirely sure if I am going to make a resolution for the year 2021. I consider omitting it altogether and just putting aside a…
Font with ligatures? Definitely worth a try.
Today, I would like to cast some light on fonts supporting ligatures and how they might help us read our code.
The idea to write this text came to me while I was reading Hillel Wayne’s book — Practical TLA+: Planning Driven Development. The book describes the concept of formal methods to verify our requirements. It seems a pretty interesting topic, so maybe in one of my next posts, I will elaborate on it too.
In Hillel’s book, many rules or intentions are represented by mathematical symbols. There is even a crash course…
My personal history with .NET
I am sorry that I did not publish a new article last month. I spent a lot of time in one company training their developers on C#. We touched upon the future of .NET a bit there, which has inspired me to write a summary of my opinions concerning .NET and its future.
Actually, creating the following post has been incredibly funny because it brings back memories of C#’s ancient times.
Have you ever wondered why working with Typescript gives you sometimes such a headache? I am not referring to the fact that sporadically you need to make an enormous effort to satisfy the TS compiler. No, I mean that occasionally the perfect working code stops working without an easy-to-recognize cause. And your API codes are among the notorious suspects, aren’t they?
I have experienced it many times — as soon as my API changed, I started noticing weird bugs or unusual application behavior. It comes down to the fact there is no guarantee that the TS types are the same…
In my last post, I wrote about getting an overview of what your bundle might contain. You can read it here.
Now that we have gained a deeper insight into your bundle, we can play with it and try to decrease the size of our packaged code. The following text includes my tips and tricks on how to find the culprit and reduce the size of the webpacked bundle.
I consider this a pretty easy rule to follow. Just find a library you do not use. You probably know that a webpack is pretty smart, using a tool…
In one of my single page application projects, I noticed a significant increase in the size of the webpack bundle. I firmly believe that everyone experiences the same situation from time to time. In hectic development conditions, it is just a matter of time until your production code hits the size of 5 megabytes or more.
You started developing a tiny project, yet in just a couple of months, it has grown into super huge bundles. You know, it is always the same story. :)
Whenever I am setting myself up for a new single page application, I regularly reach…
One day I will love C#. I promise. (web, C#, F#, SQL, JS)