Michal Kosyk

We have all been there. We got a task to introduce totally new functionality. New database relations, controllers, services, models, views. We all said: this time it will be different. But it’s not.

Engineers, developers, business stakeholders – they all communicate somewhat differently, having various professional backgrounds. The very interpretation of the context will be different, then, and it will also affect the cooperation on the project. To be sure everyone is on the same page, you can try event storming – a flexible method to create models understandable by everyone.

In a world of distraction and endless procrastination, we are witnessing the birth of a whole-new currency, scarce but incredibly coveted: focus and efficiency. Being effective, especially when you work remotely, isn’t really that easy. We hope, however, that with this set of recommended productivity tools for developers you’ll be more satisfied with your professional performance.

The perspective of legacy code refactoring can bring you a headache, or even worse. In the darkest corners of every app development process dwell lines of code that make even the bravest of developers wake up at night drenched with sweat. “It’s only about adding one functionality, what’s the deal?”, the client added, so it’s gonna be an interesting day. But should you do it or not? If yes, what approach should you take? We’ll try to help. Read on!