My last three years of Ruby development in a pie
30 Mar 2018After working for almost 3.5 years for the company, I am leaving in a few weeks. This made me look back and think how I spent the time here. And I mean how my time was distributed among all kinds of work that I needed to do.
So I made this meme looking pie chart:
This is only my guess. And of course, each project that had a different profile, some required a little more coding while others more investigation, and others involved a lot of discution with the team.
-
talking to POs about features, UX, screens, business rules: This is my favorite. I love talking about what we want to acomplish, and exchanging experiences with the other team members about the problem we are solving.
-
manipulation the git tree of the project: Because we had some code bases with a lot of people working on them at the same time, I had the feeling I spent a good chunk of time rebasing, rewriting commits, solving conflicts, etc… or helping other coleagues to do so. (I actualy enjoy untangling git work trees, seriously!)
-
reading and investigating: Some of the legacy code had more than a decade of existence. Then some times the work felt more like an archeological task that involved interviewing people from remote areas of the giant open floor office and deciphering ancient writing on the walls (well, there were some ASP on windows servers…).
-
code reviews, architectural and technical discussions: We had a very nice code review flow even with all the bumps and bruises that only made the process mature, and there were a lot of knowlogde sharing.
-
coding (programming): Thanks to Ruby (and Rails, git and unix), the easiest part :)
After looking at it again, it seems we too often take for granted all the time and skills necessary for proper software development that don’t directly involve coding.