Tama66 Some time ago other team was managing the pipeline of my team’s applications, and they were also testing and deploying our applications. This separation of responsibility between creating the software and making it run was leading us to: No ownership of the deployment process: feeling of non responsibility within the team. Errors on environments: No visibility of where our code was being deployed was producing sometimes problems with configuration on environments, and they were tough to fix.
Reading books is one of the activities everyone who is interested in software should do. It’s a great way to learn new things, new points of view, new theories or practices. There are several books that every developer should read. But sometimes it’s difficult to get time to read it, you aren’t motivated enough, or even if you are reading the book, the book is hard to understand. By reading a book in a Book Club, you will discover a new way of learning from a book.
During this year we are experiencing a very huge transformation as a team. We are living an interesting journey to become a more mature team, an autonomous team inside the company. And this transformation includes a lot of practices and activities. With this series of posts, that I’ll call Culture of Learning, I will try to explain in detail each of these activities, how we started them, how we do them and what they give us.