Let’s be honest, we do not treat frontend code the same way we treat backend code. And it shows. We talk about applying rules of clean code, about keeping it simple, about writing unit tests. Yet, when it comes to writing frontend code, we skip all those rules that we usually self impose. We convinced […]
The sorry state of frontend code Read More »
One way of learning new things about your coding style and about yourself is by doing a daily code kata. It can be like a simulation of a year-long software development project, with all the ups and downs happening in a much shorter time scale (a few iterations). More on that below. I encourage you
Lessons learned while doing daily kata Read More »
One of the dangers of writing user stories is that they can get pretty big if there’s no one on the team to point it out. The scope of a user story becomes broader than it should be. In the following article, I’m going to walk you through the reasons why you should aim for
Splitting user stories – Why, When, How Read More »
You and your team are preparing to deploy in production a set of features. Unfortunately, some of these have the status”almost done” and it’s not clear how much longer will take until done. Straight to the point – this shouldn’t happen. To avoid the failure of the deployment, one way is to reconsider how your team
How to manage “almost done” status of features Read More »
Doing your job as a software developer is not limited to writing code and attending meetings. It should also include keeping in sync with your company’s technical strategy. It may not be that obvious, but a developer should know what the technical strategy of the product is, why it needs a plan at all and
Technical strategy in practice: a developer’s view Read More »
Throughout my software-development years, giving and receiving feedback has proven to be an important tool. It helped me drive the projects forward and improved my skills as a developer. In this article, you can find out why it’s important to give feedback to your colleagues, and, more importantly, what are the proper means to provide
Feedback and happy teams Read More »
Making a new developer productive as quickly as possible is most of the times challenging for the product team. I’ve heard stories about new on-boarding team members needing up to several weeks, or even months, until they feel comfortable or knowledgeable enough about the project and the code. This shouldn’t be the norm. Situations like these are
Joining a team? 5 techniques to start & a developer story Read More »
