Career
In this article I want to give a brief overview of what I think is expected of a Professional Software Engineer, what you should aim for to be good and how you can learn and progress.
Career
In this article I want to give a brief overview of what I think is expected of a Junior Software Engineer, what you should aim for to be good and how you can learn and progress.
Career
In this article I share the things that changed in my work life after becoming a Tech Lead. Especially I will cover how my contribution to the team changed and how my view changed in general.
Career
I share my experiences of working in a Tech Lead role for the past two and a half years. I write about the fuzziness of the role and what my expectations and those of others have been at the beginning. Finally, no one can tell you what this role is about because every team is different.
Agile
When I write non-agile environment I do not necessarily mean an environment that does not use an agile methodologies like scrum or kanban. What I mean is an environment that is not agile. I made the following observations when I worked in such an environment. * there are a lot of
Focus
The problems of an inbox are widely discussed. Switching attention because of your unread count leads to a context switch and loss of focus. One solution is to check your inbox only a few times a day or week (this is crazy dude, he!?). Cal Newport brought up the idea
Agile
I wrote about our retrospectives already in an earlier article. In this one, I would like to write about my personal experiences of changes that your partner suggests to the meetings. I started using the way of holding retrospectives mentioned in the referenced article. I chose the structure as a
Agile
I experienced the pretty fast growth of a company I worked for, in which scrum is used as the development process. When companies grow, teams get bigger or new teams form. In my particular case the company used to have one scrum master - let's call him Jim
Agile
In one of my past articles I briefly mentioned the roles in a scrum team. One of them is the scrum master who guides the team to be successful applying scrum. But why do you need this role? Asking from a different perspective: what happens if you remove the scrum
Agile
A key point in scrum is transparency. To create transparency of the work of a team the board plays an integral part. A discussion point in multiple scrum teams I worked in was if the board should be digital or analog. I asked myself the same question when we started
Agile
When I started introducing agile methodologies in private life and in my family I thought I have to do it the right way. For me this included story estimation. It turned out that for me this is not the right way of organizing my free-time and projects in our family.
Agile
“Fail fast, fail often”. You read and hear this sentence a lot in the agile world. It is supposed to be a good practice. But why exactly is this a good practice - not only in agile? First of all, failing feels bad, right? You usually invest time and energy.
