Software Engineering

Let's address the existence of so called Ghost Engineers

About 15 years ago, I got my first software engineering job, and the way things were done back then--was different.

For the past few weeks I've been thinking about how hard it is to develop software.

Recently, I've seen a lot people online asking for CV improvement tips. I decided to share my knowledge in this article.

A tale on why software engineering might not be a team sports after all, despite what eveyrone wants us to believe

While looking for a job recently, I stumbled upon an interesting phenomen that I consider to be a curse for senior software engineers.

A step by step guide for staying junior forever

An evening rant about the unnecessary bloat in Software Engineering

In the past six months, I wrote and self-published two books related to Software Engineering. Let me share with you the workflow and tools I used to do so.

Since the dawn of the web, humans created CRUD APIs. And we were instructed that modification verbs should return the modified resource in response. But, should they?

All engineers are good writers... of code. But I believe that in order to a become better engineer–you should improve your writing skills.

There are many concepts in the OOP paradigm. Inheritance is the most known, and it allows us to model software as relations between objects.

New year is a good time to create a resolution. What if your resolution is a career change to software engineering?

There is one thing engineers hate the most—waking up at night and troubleshooting production incidents. What if I told you I know how to make it less painful?

Traditional pagination existed for many years. But it’s not useful for platforms with huge amount of user generated content. Luckily, there is an alternative solution for such systems.

GNU Make. A software that is, most likely, older than you. It’s so simple, so standard, and so ignored. I’m here to provide a case in favor of make and Makefiles.

Legacy. The one word engineers cringe when they hear. Nobody wants to work with legacy code or legacy systems. And yet someone has to. Can we do something about it?

Take a good look at the following function and try to understand what it's doing. function do_magic(a, b) { return a + b; }

The dire state of the software industry, leaves us with hopes for a better future. Why we ended up like this?

The path to becoming a great technical interviewer is full of doubts, tough decisions, and self-discovery. But I believe every engineer should try to walk it.

We’ve all been there. Its time to introduce a new package / dependency to our code base, be it a HTTP request library, a logger or something else, and the question we ask ourselves “Should I wrap it?”