It's just a one-page note where you can write something down. It's super useful for me because sometimes I really need a place to make some notes briefly.

Because the question isn’t whether you’ll pay down the debt —
the question is when:

📍 now, while the product is growing
…or later, when the market has already moved on.

You don’t stop technical degradation with heroics from engineers. You fix it by changing priorities:
— refactor regularly, not “when there's time”
— measure system quality, not only delivery speed
— invest in tests, docs, onboarding automation
— evolve architecture as systematically as product

How to recognize tech degradation
— Small tasks take disproportionate time. Architecture becomes fragile: change one module → break three others. It’s accumulated architectural debt.
— More incidents. More repeat bugs. Longer time to fix.
— Engineers spend 70–80% of time just keeping things working.

It’s not an engineering problem — it shows up first in business outcomes, not metrics. If growth slows while team costs rise, you might be dealing with tech degradation—whether you call it that or not.

Actually, there's one interesting aspect to this process — I enjoy answering behavioral questions because I genuinely have a lot of very diverse stories.

I may be mistaken, but this visa cannot be extended for a year. For those who want to live in Slovenia for just one year, it is undoubtedly attractive. But what about those who fall in love with the country and decide to stay for another 3-5 years?

Simple colored pencils. It turned out to be super simple and actually works perfectly. Sometimes the best answers are the most obvious ones.

I made this photo in Echka — it is a small village in Serbia maps.app.goo.gl/XVW4t2UtoGvH...