Not just for yourself, but for developers on-boarded onto the project in the future. This was when I was finally struck by the importance of writing readable code. It was only after a couple of years that I worked on my first project that involved an inherited legacy code base. These projects generally involved writing new code that only I was responsible for. ![]() Since the beginning of my career I have mostly been working in consulting roles for ‘greenfield’ projects. This tends to result in project code bases with inconsistent code formatting and less focus on readability and maintainability by others. It will usually just be one person responsible for maintaining a code section, rather than the collective responsibility from multiple team members. ![]() Yes, we work in teams but it is unusual for you to be working on the same code file as someone else and normally you will have individual responsibility and ownership over a particular part of the project. In contrast to Software engineering, as Data Scientists we tend to work quite independently on code. ![]() “Of course, I know what type of data that variable holds and what type of transformation that function is responsible for – it’s obvious, right!?" But I never gave too much consideration to whether I would still be able to read it in 6 months time or if it was easily understandable for a colleague with no prior knowledge of the code base. Obviously, I cared that I could read it during development. I never used to worry too much about readability of my code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |